I used to complain about all the levels of indirection of modern software, running in a javascript jit, in a browser container, in a vm, on an os, etc.
I eventually just accepted it, but this new agent layer really takes things to a new level.
You can see how I did mine here if you're interested:
https://github.com/bruse/dotfiles/tree/main/macOS (I suspect com.local.KeyRemapping.plist is most interesting, but the key layout file is there too, with some comments on how it was generated).
Sure, but it's probably unwise to have your production credentials on your development machine at all. It's far more likely to be compromised than your locked down production environment.
I must have missed some trends changing in the last decade or so. People have production secrets in the open on their development machines?
Or what type of secrets are stored in the local .env files that the LLM should not see?
I try to run environments where developers don't get to see production secrets at all. Of course this doesn't work for small teams or solo developers, but even then the secrets are very separated from development work.
It's interesting, because a few years ago I would have put this strictly under the "not invented here" fallacy, where we'd now be stuck maintaining another project for the foreseeable future. I used to press pretty hard to avoid it.
Now I wonder if the maintenance cost for this type of internal system has gone down to a level where that is no longer an issue.
Of course, majority is not very cleanly applicable yous politics. Less than half (which according to Mirriam Webster is the definition) of the votes cast in the last election went to Trump/Vance, and with such a poor voter turnout it was even further from a majority. Meanwhile the electoral college is working against the idea.
I wonder why Andreessen needs to use disinformation to shape opinion if the actual problem is so bad? I find it very unlikely that he does not know how PEP actually works.
It is so demonstrably false. Anyone who has worked in an finance adjacent industry likely knows the definition of a PEP.
Does anyone know if Embark are still using a lot of rust in their production games? They seem to be a very well funded studio (lots of employees, big fancy office, competes with other AAA FPS-games). I wonder if these experimental-sounding projects have given way to more classic tech in the churn of building games that are profitable.
This is my experience in very small companies (think a <10 person startup). The value of everyone knowing a lot of what's going on from immersion is immense. You can have very little processes around information sharing (which takes time to set up and fine tune!), very little time to convince people what needs to be done (it's obvious from the conversation the other side of the room is having), and all the nuance of in-person communication is kept.
Once a company gets a little bit bigger, the processes around information sharing, planning and other communication has to be in place anyway. Teams need to collaborate, work needs to be tracked, there has to be meetings for planning. Once you're already doing that you might not lose anything by going remote.
I worked in the robotics lab at my university for a few months. That was a really nice way of making software more tangible. Seeing things move through physical space made it more real.