Nicolas Dular

Nicolas Dular

@nicolasdular.com

Staff Engineer @gitlab.com Web: https://nicolasdular.com/ Podcast https://walkingdevs.com/

101 followers119 following143 posts

Nicolas Dular reposted

"If these tools are so good, where's all the magic software?" I see more bugs now, in software that was rock solid before. The uncomfortable question: when does that hit something load-bearing? Has it already?

Nicolas Dular reposted

📭 New Blog Post 📬 I wrote a tiny piece about how to store your SSH keys more securely. In times of distribution attacks like Shai-Hulud, it's easy to install malware on your computer that extracts your private SSH keys. Don't let them. peterullrich.com/store-ssh-ke...

peterullrich.comStore your SSH keys in a Password ManagerYour SSH keys are sitting in ~/.ssh as plain text exactly where malware looks first. Move them to a password manager instead.

I like how @mariozechner.at and @mitsuhiko.at are at the forefront of using AI & at the same time not bullshitting 🙌 Worth listening.

Gergely Orosz@gergely.pragmaticengineer.com

OpenClaw was built on top of Pi, a minimalist, self-modifying agent. I sat down with Pi's creator, Mario Zechner, and longtime Pi user Armin Ronacher to talk on the "why" of Pi, their grounded takes on building with AI, why we should probably slow down, as an industry, and more. (cont'd)

btw: mostly RSS memory that doesn't get free'd up. So outside of the Beam. It gets free'd eventually, multiple short bursts of concurrent tasks can increase it unsustainably.

While we like to complain about the Frontend ecosystem constantly changing. At least they have one language. Backend has the problem of language diversity.

Frontend: If you know TS + React/Vue - you cover most job requirements. Backend? Completely other story. Add Databases, scaling problems and a few other expertises (KVS, Event systems, ...) and your options are limited.

Nicolas Dular reposted

The job of a programmer is to manage exactly two things: uncertainty and complexity. Code is sometimes an asset and sometimes a liability, but itself has no meaning outside the context of those two factors.

Querying tree hierarchies can be tricky, especially when the `IN (...)` query gets large. There are some optimisations, but you can only go that far. We decided to denormalise the hierarchy data into the issues table. Lots of research and testing went into this. Especially for the new indexes.

I am building a small application with #ElixirLang and Codex. Process is pretty much: - Let Codex run with my prompt - Look at generated code - Delete 50% of the code It's okay-ish at writing tests, which is nice. Especially since IMO Elixir tests are too verbose compared to RSpec.

View full thread

ash_typescript/rpc is THE reason to use Ash right now. I ran into an edge case (still need to write a bug report) but 0.x version is already more stable than most "stable" NodeJS libraries I've seen recently.

It feels like I can escape the declaration style, but I am not 100% sure if that's true in the end. Not a fan of the APIs with `for_read`, `for_create` but I understand why it's needed. Also weird that some data is wrapped in Ash Structs (Like a string value from an changeset attribute)

I am unsure about potential compatibility issues with all the different ash packages in the future? Policy integration is nice. But hard to wrap my head around policies for reads. I prefer more control over the query

I looked into Node/Typescript ecosystem for a Fullstack framework last week. Quality on the backend is just too far off from what I see in Rails/Phoenix. My biggest requirement is: full typing between backend to frontend. Now looking into @ash-hq.org 👀

"What do you hate about ActiveRecord?" That interview would definitely go over time.

nateberkopec.bsky.social@nateberkopec.bsky.social

With LLMs making leetcode and other whiteboard problems trivial, software hiring IMO should shift towards establishing taste, which LLMs absolutely do not have. "What do you hate about ActiveRecord? What would you change about Rails if you could?" Review this PR, etc.

So far I've not seen any good fullstack framework. JS does well on client/server communication, but is years behind backend frameworks. Backend languages try to abstract all client-side communication and end up with weird patterns.

I really tried to give NextJS a chance in the past few days. Documentation is sparse, basic things are unstable, server/client communication is nice. Too much magic, but neat DX (if it works)

Nicolas Dular reposted

I am getting SO tired of these posts from influencers: “We literally cloned an N billion-dollar company in 20 minutes with {vibe coding tool}. This changes the game forever.” No, you didn’t “clone” a billion-dollar business. You created a landing page similar to it. That’s all.

Most SaaS products are just fancier Excel sheets. Dedicated software is still nicer to use though. But with AI, I expect more companies starting to build tailored tools themselves.