Always surprises me how people feel identified with progress they didn’t participate with. These satellites have nothing to do with you. You didn’t build them nor researched about them. These are the toys of a far-right asshole. It sucks
I was waiting for GTA 6… but if it’s not released in disk, then I will simply pass. If new games start to be non-physical, then I will simply stop playing new games
From my naive pov: Related to computation is the concept of state (I know, functional languages can get away without it, sort of). I always wondered how the universe “knows” the mass of the sun. If there are some underlying functions/computations “running” in the background to keep planets moving and so on, and if the mass of planets is a key element in such computations… then either: the mass is calculated “on the fly” every time (seems expensive) or it’s a variable (how is it updated? Where is it “stored”?)
What is normal? You know how girls dress, let’s say in the Andes? Is that normal? Or by normal you mean what’s fashion in NY? Or perhaps what the majority of people wears today? Or what the majority of people have worn in the past?
Very little of what the west does can be considered normal.
We should rephrase the multipliers. We are not 10x whatever, we are x/10 cheaper now to the companies that hire us. That’s the correct frame. AI is not here to make the life of engineers better; AI is here for the delight of companies
But there are two types of “programming”: 1) programming per se (just you writing code for fun and perhaps building your own tools) and 2) a team of people with real-world constraints writing software for others for revenue
It’s clear why it feels so good to use something like Lisp for personal projects. It’s also clear why the vast majority of companies don’t use it
The companies I have worked for before all have used open source software like postgres, mysql, go, python, k8s, etc. 99% of the time we relied on free work; never contributed to these projects nor forked them for our own needs. I don’t think this behaviour is the unusual path tbh
- typically they are behind a single person. That’s usually bad because of spf
- typically they are achieved in a very short amount of time, so the author hasn’t acquired any discipline in creating the project. That means it’s unlikely the author is going to stick to the project in the mid and long term
- anyone that wants to contribute to the project needs to pay. Needs to pay tokens because it’s increasingly difficult to maintain these projects without AI
So, who wants to put something like this in production? Doesn’t make much sense
I find it painful as well. I actually find agentic coding counterproductive. I typically use LLMs the “old way”: web chat interface, asking questions and searching. I write the code by hand. This makes me 2-3x more productive than before (I guess with agents I could be 5-10x more productive but the price to pay is not worth it)
> Good specs should be grounded (complete and not ambiguous), they don't need to be formal
IMHO, this is a mistake. I guess we play with it because there’s isn’t anything better nowadays. Writing and maintaining “specs” in plain english is painful.
Certainly I have never been in such a situation, but just for me to understand: if the sender has enough decision power to move forward with a default action without confirmation, then the email is simply a polite notice to someone above in the command chain, isn’t it?
Why the email then? Wouldn’t a record of the decision (not via email , but in some confluence-like space) be enough? If the confirmation is really needed then a default action wouldn’t be possible, ofc
I started with js and php. Moved to Java. Then node. Then php again. Then Go. Then Kotlin. Then TS. Then Python. Then Go again. In between a bunch of sql, html, css, and many different tools, libraries and frameworks. The most important things Ive learned are around architecture/databases/distributed-systems, tho.
I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.
> Our hypothesis is simple: session logs are now the most important artifact in software development, and should be stored alongside the code itself in the repository.
I don’t think this scales. We recently have been doing “spec driven development” and we are committing the specs and prompts to our repo, alongside the generated code. At the beginning it seems fine: you wanna change something, you update the spec and ask the machine to regenerate the code. Easy. Over time, though, you have hundreds if not thousands if spec files in MD. It’s all English prose. There is duplication and subtle inconsistencies. It’s difficult to search for sections of a spec. Do you create a new file for this new requirement or update an existing one? What level of detail is enough here? Should I hint the machine about using the “saga” pattern or just let it know that we are dealing with non atomic transactions distributed across services? Etc. When a colleague opens a PR updating a spec, it’s hard to suggest objective changes (at least with code, you can demonstrate the presence of bugs… not so much with English prose. Sometimes I feel like a lawyer)
All in all, it seems as if maintenance of english prose is way worse than maintenance of actual code in big enough systems. You not only need to review the spec but also review the generated code. It’s painful