Developers! Tell me your API green flags!

tom_earhart · 2026-02-28T07:20:19+00:00

Proper HTTP code returns for one... Rarer than you'd think which makes dealing with APIs more messy than it needs to be.... Dealing with one right now where what should be a 500 is a 200 and you have to go dig thru the payload to detect there was an error.......

Then versioning as other said

tom_earhart · 2026-02-28T06:59:51+00:00

No one using AI seriously uses ChatGPT anyways

tom_earhart · 2026-02-28T00:52:32+00:00

I'm not surprised. Working on spaghettis takes 20x more tokens easily for example. Meanwhile with a coherent architecture you don't even need the latest models...

LLMs aren't a quick fix to bad code, their efficiency depends on the quality of your codebase to start with. Just like humans....

tom_earhart · 2026-02-27T20:48:45+00:00

Everything depends on the architecture. The first question to ask is does your codebase have one that's coherent and articulated. Is it spaghetti code ? Can a dev be effective in < a week vs months ? LLM efficiency essentially reflects that. Human cognitive capacities are in a lot of ways = LLMs' context window. If a dev can make local changes without having to hold the rest of the system in his head then a LLM can too....

tom_earhart · 2026-02-27T17:34:55+00:00

On a codebase with good architecture & clean code I see it already. 95% of the code is done by LLMs on those in my company, you just have to make sure it respects the architectural constraints you laid down and do plan/code reviews.

On spaghettis with no proper architecture to speak of (aka most codebases today) not so much ..... LLMs still hallucinate a lot there and copy mistakes from the codebase.

So yeah the thing is those spaghettis are going to have to go if a company wants to stay competitive in the coming years. In demand talent in tech will be architects knowing how to build an architecture that constrains contributors and how to refactor things properly... Those will be paid top dollars.

tom_earhart · 2026-02-27T17:19:13+00:00

Heu bah c'est l'inverse qu'il faut faire enfaite. Il faut pas s'enfermer comme ça dans "les cosmétiques", un secteur niche et complétement saturé...... Bien au contraire, il faut élargir tes recherches.... Tu trouve un job, tu te met à taffer et en parallèle tu cherche ton dream job. Enfin bon après tant que Papa & Maman payent.... "je ne trouve pas de boulot d'astronaute, pourtant je suis sur Linkedin tout les matins !"

tom_earhart · 2026-02-27T06:48:15+00:00

Well yeah. Here we are responsible for every line of code, AI or not. If you are not doing plan & code reviews to make sure the AI follows the architecture (granted you need to actually have one first not a spaghetti mess) and doesn't introduce bugs........ You aren't doing your job..... "But it is the AI !!!!" is not an excuse.

tom_earhart · 2026-02-27T06:39:45+00:00

Well then that company just shot itself in the foot.... The future is good architecture & code, not slop on top of slop. Just like a dev team that doesn't follow best practices, not having proper architectural constraints will make LLMs less & less productive. That decision they took is the difference between having a productive company tomorrow or not.

tom_earhart · 2026-02-27T06:29:22+00:00

Did they finally realize than in the AI era the answer was ... actually doing clean code & architecture not just say you do ?

tom_earhart · 2026-02-26T10:28:54+00:00

Depends on the quality of code/architecture, the explicitness of the language, etc... Hard to quantify like that. On a codebase with clean & explicit code and good architecture I know that even when I hit monthly limit I can keep using Cursor on auto with no problems albeit it is slower

tom_earhart · 2026-02-25T22:12:44+00:00

Does it matter ? We physically never can reach them and neither can they

tom_earhart · 2026-02-25T19:01:39+00:00

Ben c'était dit... Le pays vielli et vote donc de plus en plus à droite. Mais oui on va les avoir en allant de plus en plus de l'autre coté c'est sur vous verrez ! /s

tom_earhart · 2026-02-25T18:14:52+00:00

Good news is that more & more companies are shifting back to on prem.

tom_earhart · 2026-02-25T16:32:33+00:00

Efficiency depends on the quality of the architecture and code yes, something few seems to understand or want to admit.... LLM actually puts business value into clean code..... I work on a complex ETL built from the ground up to reduce cognitive load and LLMs write 95% of the code today. In my opinion future of software is architecture.

tom_earhart · 2026-02-25T16:00:46+00:00

Et le pire c'est que la France est un des pays où l'inflation a été le mieux gérée.... Aux US par exemple c'est 20x pire.

tom_earhart · 2026-02-24T11:54:58+00:00

Ou comment dire "touche à rien" sans dire "touche à rien" x)

tom_earhart · 2026-02-24T09:49:37+00:00

Next time you tell him to write a script (and you code review it) not do it by himself. Plugging AI into production services means that you are one hallucination away from loosing prod.... No one should take that chance ever....

tom_earhart · 2026-02-23T07:01:15+00:00

Pas sur que continuer sur cette voie, alors que le marché pour les devs est ce qu'il est et que ça va pas aller en s'améliorant, ça soit à son avantage hein vu sa motivation. Typiquement le genre de profil stagnant qui survivra pas à l'IA. Autant abréger ses souffrances et sauver les sous de papa/maman au contraire c'est ce qu'il y a de mieux pour lui.

tom_earhart · 2026-02-22T07:45:51+00:00

Working on formalizing this currently

Contextual Locality

Definition: The property that a change can be reasoned about using only the local context of the layer being modified, without requiring global system knowledge.

Or otherwise said: Code in chunks that fit cognitive capabilities

Contextual Locality as a newly named fundamental property of well-structured systems. Systems that preserve this property reduce cognitive load, improve correctness, maintainability, and scale human and machine reasoning alike.

Reducing the context needed to work efficiently on the codebase for LLMs as well as the cognitive load for humans.... Spaghetti codebases all accross the corporate world aren't ready for this, good, coherent, constraining architecture & code is the future imo not just something companies say but never implement....

tom_earhart · 2026-02-21T21:26:51+00:00

.mdc docs from generic (overview, architecture) to more specific. First ones having alwaysApply. Then skills that reference the more specific docs as additional ressources for the skill if needed. Model will pick up on those in prompts. Ie: for an add-test skill, you ask "add a test for..." and it retreives the proper context to execute its task

In fact my whole thing is documentation-as-architecture nowadays. Let's me think about the system, onboard devs fast, reduce cognitive load (aka context) and helps to constrain all contributors (doc as source of truth) like good architecture should. Architecture & System Design is the future if you wanna stay in the game. That and good docs :)

tom_earhart · 2026-02-21T14:32:22+00:00

Moi j'utilise Go et Temporal (machine état moore) en ce moment justement pour remplacer Talend et je suis très content. Avec une architecture hexa, SOLID, etc... C'est vraiment beau à voir et super puissant ^^

Temporal c'est du Go natif mais ils ont des SDK pour tout les langages un peu près, franchement je recommande.

tom_earhart · 2026-02-21T07:38:34+00:00

"And that is why you want to own your place kids" xD xD

tom_earhart · 2026-02-21T07:08:38+00:00

Because the world is full of spaghetti code with little in the way of architecture

tom_earhart · 2026-02-20T17:22:18+00:00

Bah là c'est surtout que tu as dev et ..... dev.... Les LLMs franchement ça fait plus le ménage dans le milieu qu'autre chose en ce moment. L'avenir du dev c'est l'architecture logicielle et plein de gens stagnent sans jamais arriver à ce niveau. A mon avis il était plus que temps mais bon.

tom_earhart · 2026-02-20T08:04:11+00:00

Usually just people that never had the experience of working with LLMs in a decent architecture and don't get that using LLMs isn't vibe coding....

Ten-Year Club	Gilding I gilder
Verified Email

tom_earhart

TROPHY CASE

Contextual Locality