"The fix is not to lock the code away. The fix is to separate participation from final control. Give the entire team access to the code so people (with or without agents) can work on it. Keep merges limited to engineers."
Oh great. The engineers now have to review 100x more code AND still be the ones responsible when something goes wrong. How convenient!
What you’re describing is actually the flaw of the traditional model. Engineers end up accountable for everything, including decisions they didn’t make, because they are the final gate. In my proposal, responsibility follows decision power and is explicitly shared. Whoever proposes a change owns its behaviour, which is why sufficient product context is essential. This only works if everyone in the team operates as a product person, understanding the impact of their proposals beyond just implementation. The product manager owns product direction, engineering owns system integrity, and ownership is distributed rather than concentrated.
The final engineering review is not full ownership of every diff, but a focused technical judgment about whether the change preserves core invariants and integrates coherently within the system. If engineers still have to review exponentially more code while remaining responsible for everything, then the model has failed. The goal is to distribute accountability together with autonomy, so engineering safeguards systemic coherence while the entire team shares responsibility for product outcomes.
Why? You can use rechargeable AA batteries and if you want you can swap them out and basically never have downtime for charging. Also all embedded batteries degrade over time which is a non issue here
Some of you have never been laid off and it shows.
Intrinsic value is great, where achievable. Companies do not care at all about intrinsic value. I take pride in my work and my craft to the extent I am allowed to, but the reality is that those of us who can’t adapt to the businesses desires will be made obsolete and cut loose, regardless of whatever values we hold.
I felt the exact same way until I tried Hazelight's AngelScript UE fork. It is amazing, it brings the developer experience and iteration speed to Unity levels. They even made a VSCode plugin for it. Cannot recommend enough
I'll heartily second this. After years of Unity, I just couldn't stand the developer experience any more. Waiting for iterative compiles that took an ice age each time I changed a line of code killed me. Angelscript UE is as close to engine perfection as I can imagine
Any thoughts on Verse? I’m not experienced with Unreal or in the ecosystem, but it looked like it might be too foreign to me. But Tim Sweeney is no dummy, so it’s probably good and just requires some effort if you’re not already a functional programming nerd?
Yes, I tried it recently for easy cross-compilation. You can use basically any C/C++ compiler, even TinyCC works (in most scenarios) if you want an extremely fast edit/compile/test cycle.
Macos window/desktop management is also stuck in 2001 with "magic gestures" tacked on. For someone who hates using these gestures especially when connected to an actually good kb/m, the base desktop experience is horrible. The dock is completely useless, the various cmd+tab or cmd+` shortcuts are unwieldy, Spotlight is growing increasingly worse year after year.
Rectangle/tiling window managers on top is the only way to make it workable.
Apart from wm, the existence of application notarization is a downright insult (though Windows is also guilty of this with smartscreen but to a much lesser extent).
Apple's "pay us 100 bucks a year or we'll tell your users that your program is malware" is just another step in the inevitable game of locking down macos and turning it into a mobile-like hellscape
What gestures are you talking about? I think you can turn those off, and I’d be surprised if there isn’t a way to turn off the rest with a 3rd party or custom tool.
Application notarization isn’t a problem anymore- you just have a single accept dialog. That problem that made you do a trick to get past it was only a problem years ago, due to whomever the moron was that thought that was a good idea. The current way is acceptable.
I install homebrew and random apps with no problems.
I was thinking that too. There are many cases where you do want to manage memory yourself, and in that case you should likely use Rust or maybe Zig if you can choose your own tool. But if you don't want to manage your own memory Nim works nicely, though IMO it requires adherence to a style guide more than most languages.
Depends what you do but most of the time you do not need to do anything special about memory management in Rust. That is why people try to use it for other things then just system programming.
Oh great. The engineers now have to review 100x more code AND still be the ones responsible when something goes wrong. How convenient!
reply