jnpnj

Fair point, I wasn't thinking about making everybody a civil engineer but you can clean some walkway, fix a simple bolt, a bench. that sort of thing.

jnpnj

4일 전discuss

ah yeah pretty common and pretty annoying.. either they had to avoid false issues or maybe there was a regulation forcing the use of a more beefy system (or maybe someone thought it's "better" to use the latest shiny thing)

jnpnj

4일 전discuss

That is true, that said reporting is not the same (imo) as having a global map of problems and proposals to fix some of them. To me it's a lot more engaging (again, imo) as you see the distance to a goal.

jnpnj

4일 전discuss

Are there other similar apps to stimulate soft "crowdfixing" ? I'm sure there are plenty of other aspect of society that would benefit from a light way to know where someone can contribute or notify so other can fix things (forest dumps, random trash). Homeostatic apps to ensure our surroundings are close to a good state :]

jnpnj

5일 전discuss

What was your reading list ? I plan to add more medical / genomic knowledge to my skillset.

jnpnj

5일 전discuss

    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: [email protected]
    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)

jnpnj

2개월 전discuss

Corporate emails asking why are you not using the <insert-llm> paid plan ??? came very very rapidly. So naturally, everybody started to use it blindly so that the dashboard metrics are all high.

It's astonishing how society forgets.

jnpnj

2개월 전discuss

I ask myself the same questions. And I see other people discussing this on HN or other websites (old video games culture for instance).

I too feel that the computing aesthetic has vanished, somehow on purpose, a lot of efforts were aimed at making gpus and browser able to emulate anything (magazine, movies), so that's what apps do.

And I also agree about the balance between the tool and user. Limitations forced UIs to be organized, structured in some simple ways, they would do enough work to do some of the work, but the rest was on you to grasp the abstractions and ideas around. The software became something to immerse yourself in to gain more. That was part of the magic.

jnpnj

2개월 전discuss

Hehe yeah we all have our own tastes based on time. But I'm also interested about the perception of computers. I too was enamoured with the creative possibilities of it. But nowadays I see a detrimental trend in how aesthetics are born on computers. The cleanliness, the recurrent patterns. A lot of pre-computing visuals were really different, none of it would qualify as nice today, but it was seen a cute before, and I kind of miss the less structured, less obvious, less shiny approach. It was also material, a different game, with constraints about possible colours, shape and precision you know. It also distracts us too much and creates real mind issues (I struggle with strange behaviors when browsing, near no attention-span etc)

So now I rebalance things and put computers in a smaller niche, not the centre of gravity.

jnpnj

2개월 전discuss

Could you tell us more about your grandma point of view (if she ever told you more of course).

With age I'm becoming jaded with computing, not personal computers per se, but the overwhelming space taken by them now (especially due to cheap networking I guess).

jnpnj

2개월 전discuss

Not really, I knew it was radically strange in its philosophy.

jnpnj

2개월 전discuss

I find admirable how every era was filled with fights on just about every detail. Keys included, layout, shape, meaning. And now nobody pays attention that any of this at all. Very strange and funny at the same time.

jnpnj

2개월 전discuss

it's strange to see software engineers using skills aka human description of small scripts instead of scripting things directly. often there were cli / tools / libraries to do what a skill does for many years. maybe it's culture issue, people who enjoy automation / devops / predictability will naturally help themselves, but other people just want to "delegate" and be done without trying.

jnpnj

2개월 전discuss

looks like an informal DSL for specs that brings back some quantifiable structure, how many people follow the same ?

also, i wonder if people who did MDD (model driven development) have embedded AI in their methodology

jnpnj

2개월 전discuss

hehe. alternatively dotnil would have sounded closer to dotnet while hinting at lisp terminology and history

jnpnj

2개월 전discuss

    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: [email protected]
    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 to grow my skills faster. I'm offering competitive rates ($60-90/hr) prioritizing team culture and interesting problems over maximizing income.

What I bring:

- Taste for type safety

- Pragmatic mindset (planning my solutions for regular delivery and avoid delay or drift)

- 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)

jnpnj

2개월 전discuss

Well, Moggi's paper on monads is from 91 and wadler first tutorial from 92. Am I missing something ?

jnpnj

2개월 전discuss

Very very nice timeline ! some interesting papers from the 90s section.

Maybe they could add https://github.com/VincentToups/emacs-utils/blob/master/mona... . I found J.V. Toups writing very nice, and useful to see how monadic composition could exist without type support.

jnpnj

2개월 전discuss

I was wondering how people feel about this trend. LLM allow you to free yourself from foundations (frameworks, programmable programs) to just generate any support layer you want from old or new libs. This is all very understandable.. yet I find it a loss, in the lisp world, having a core model and semantics shared by all the upper layers means ease of reuse (for instance people leverage emacs calc classes in other places), llm allows for easier fragmentation..

jnpnj

3개월 전discuss

But is the debate about "fleshing out a system spec" or "ability to come up, plan and explore various ideas to solve problems elegantly on a budget" ? I think there's always these two sides conflated as one when discussing LLM impact on users.

Submissions

. GotHub All the Things

comments