yep https://github.com/leo-aa88/HelloWorldEnterpriseEdition

From my experience of boss looking at people working. Working hard is by a huge margin a lot better than working smart. Trust me I know my shit. Once I even wrote a formula in Excel! /s

That being said with experience you stop using anecdotes, easy pre-made sentences like “premature abstraction/optimisation is the root of all evil!” and you understand that there are no generic solutions and you need, every time, to think hard about the best way to produce something relatively to the context and constraints which, most of them, aren’t technical but organizational and human related.

And also, if you intend to work on a project more than 6 months. Quality is really worth it. The lack of quality works like accumulating mud. After a while, you are stuck, and the next step will require a huge amount of energy.

I didn’t see Claude 4 Sonnet in the tests and this is the one I use. And it looks like about the same category as o4 mini from my experience.

It is a nice tool to have in my belt. But these LLM based agents are still very far from being able to do advanced and hard tasks. But to me it is probably more important to communicate and learn about the limitations about these tools to not lose tile instead of gaining it.

In fact, I am not even sure they are good enough to be used to really generate production-ready code. But they are nice for pre-reviewing, building simple scripts that don’t need to be highly reliable, analyse a project, ask specific questions etc… The game changer for me was to use Clojure-MCP. Having a REPL at disposal really enhance the quality of most answers.

Obligatory link to wat? video

https://www.destroyallsoftware.com/talks/wat

Obligatory XKCD https://xkcd.com/378/

Moreover, codebase in pure funcional languages is hard to understand and maintain, that’s why they are rarely used in production.

hahahah how to trigger a lot of people working with these pure functional languages (like me).

I’ve worked with both “normal languages” like C++, java, Perl, javascript (node + UI), etc… and then I switched to Haskell and Clojure. And our current production code is a LOT better than in traditional languages. In particular, maintenance is a lot cheaper that what I was used to when working with more traditional languages.

Regarding the community impact I would advise to use Clojure instead of Haskell (or Purescript, or Elm). Clojure is a nice middleground that has a huge advantage of being very stable (by that I mean, the code you write today will probably be very easy to deploy in 10, or 20 years from now).

Note however, the language alone is not sufficient to write good code, but it helps you choose better abstractions that will be easier to maintain. If you dive into the spirit of the language, you will have a better intuition and understanding about state management of big applications and will probably make more visible some design issues.

cp $fic $fic.$(date -Iseconds)
git commit -a -m "save at $(date -Iseconds)"
# edit $fic
git commit -a -m "save at $(date -Iseconds)"
git push -f

Fresh from university I found a job with terrible keyboards. After about 4 months I started to feel constant pain in my wrists. I then switched to vim.

And it solved my wrists issue. But also, I discovered a way to edit text that was so much optimized fat beyond my expectations.

I wrote this article for people that would like to familiarize with vi keybindings.

https://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/