Location: Paris, FR
    Remote: full remote
    Willing to relocate: no
    Technologies: Python, Typescript, Lisps, React, Django, FastAPI, Postgresql, Gitlab/ci, Docker
    Résumé/CV: https://registry.jsonresume.org/jnpn?theme=elegant (github https://github.com/jnpn)
    Email: johan.ponin.pro@gmail.com
    Schedule: Part-time (10/20h per week)

Senior Fullstack Developer | 12+ Years | Seeking Long-Term Collaboration as Freelance

Currently employed but looking to build relationships with teams that value craftsmanship and velocity. I'm offering competitive rates ($70-90/hr) prioritizing team culture and interesting problems over maximizing income. I also enjoy procedural repetitive testing, so QA could do too (lower rates apply)

Summary:

- 12+ years shipping production code

- Dev tooling expertise (recently: custom Babel AST analyzers for faster debugging)

- Proactive problem-solver who likes to improve processes

Ideal projects:

- Teams with strong engineering culture who build ambitious things cleanly and fast

- Greenfield development or systematic refactoring

- Bonus: Highly formal/industrial model-driven environments and FP/Logic Programming environments (Clojure, Haskell, Prolog)

Isn't that why we created models and graphs before ? Maybe now the uml to source roundtrip can be solved with LLMs. Back in 2010s that's where it was stuck.

Note: I wonder how many people reified their codebase as logical facts to query or investigate it more deterministically. I've been trying for a while, still not far but getting there.

I'm a keyboard based UI lover, but I wonder if the supportive crowd is, and will ever, be too small.

Even crude AS400 days keyboard UIs were beyond nice. But then if people want to try and replicate emacs keymaps or vi command composition, better for the dozens of us. ^^

once again, I get to cite the IBM AS/400 CallPath system demonstrated here https://youtu.be/5pY6Xxptp9A?t=2083 which almost brought a tear to at least one viewer's eye

Pretty cool video. I would love to know more about the internal design of the as400 platform and how people thought and designed user interfaces. I can't shake the feeling that these interfaces are so lean they're satisfying. Also, I feel that a lot of interfaces today are wasting resources.

watch the whole video from the beginning! :-)

oh i will, i let the second half run, but i'll make sure to see the first part too

Even as a naive teen, I always found the mechanical forces required to clamp cpu heatsinks and fans brutally high considering the small ceramic package underneath.

so the final challenge is to try to print a string ? ;)

last year i mis-bought a ssd on amazon (wrong size or model i can't recall) so I asked for a return, surprisingly amazon wanted to save on transport that they offered to pay me to keep it (i don't want to spread stupid claim but maybe the full item price), i was confused and worried it would create issues down the road so i sent it back thinking i'd buy the proper item the month after.. and now i'm running duplicate search programs to save space on drives.

It would strange if just when a lot of articles mention computing / social networks are detrimental, governments start passing laws to forbid platforms and/or phones for kids, and now price gouging flares up everywhere, this would entice people to just stop using these devices and maybe enjoy natural taper-off.

I like this idea! Perhaps folks will game less on PCs and consoles. But would they shift to playing on their phones? Or play less video games overall?

Also, when OpenAI's new device comes out, would people shift to talking to these small devices?

People do not want to talk to their devices because they are in the room with other people and they dont want to disturb them. I think their device is going to be a flop.

It's going to flop because everyone is already able to talk to Google Assistant to manage things, and outside of very specific circumstances (e.g. driving) everyone is still tapping screens instead

The "language model" aspect shows IMO, at least for someone who grew up with the material of 90s and 2000s where we describe things more in mechanical, engineering terms. When gpt4 landed it was somehow amazing to see the output, but yeah nowadays I keep skimming through the explanation. It's like an intermediate dev who has nothing else to do but create long sentences to describe what could be simpler.

I'd extend the advice with "put yourself into a reading friendly context" so you wonder less and dive in more easily.

I've seen a subtler variant of that. Since 2025 winter model improvements, low quality developers can now commit somehow decent stuff more regularly, but as before, they still don't own the solution space independently. LLM output is now larger than what they can envision and cracks will simply happen further away, only to be discovered by someone else later. It's strange everything changes so nothing changes phenomenon.

Most vibeslop these days is superficially good in that it has unit tests, compiles, passes the style guide, but it's bad on a macro level in that it makes the system more complicated, ignores the wider design of the app, implements what the prompter asked for and not what the app actually needed, etc.

I'm seeing a bad pattern of vibeslop being used to solve the immediate complaint of the user without stepping back and reconsidering things from a product perspective. Just add another conditional statement to make this very specific scenario the user complained about work the way they want.