If anything, Laravel has been what has kept PHP relevant. The community (both PHP and Laravel) has continually grown year over year after the sharp decline of everyone’s poor experience with PHP < v5.0, and Laravel has clearly been responsible for that more than anything.
If you work to inflict violence on others, you shouldn’t be surprised when it’s attempted to be inflicted back on you. I’m not saying it’s a just worldview, but it is pragmatic.
FWIW I mainly use Opus 4.6 on the $100/mo Max plan, and rarely run into these issues. They certainly occur with lower-tier models, with increased frequency the cheaper the model is - as for someone using it for a significant portion of their professional and personal work, I don’t really understand why this continues to be a widespread issue. Thoroughly vetting Plan Mode output also seems like an easy resolution to this issue, which most devs should be doing anyways IMO (e.g. `npm install random-auth-package`).
I really don’t understand the widespread adoption of OpenClaw when a simple prompt injection in an email, chat message, or calendar event has the potential to leak the credentials/keys for every attached service.
The golden age is over. It’s a saddening experience watching something you care about, and your opportunities to build a career and life around it, fade away. The reasons for this are numerous, (like you mentioned; ZIRP, COVID, etc) but the ultimate irony IMO was the layoffs/AI push being an industry-driven nail in the industry’s own coffin.
There’s also something to be said about the industry’s faltering after the social era, a period which largely began the degradation of Big Tech’s public image, which was worsened even more by the overcorrection into Crypto/Web3, and finally through AI - which feels just as forced as the previous era was.
You can clearly run the provided gist. Calling “You are OpenCode” in the system prompt fails, but not if you replace the name with another tool name (e.g. “You are Cursor”, “You are Devin”). Pretty blatant difference in behavior based on a blacklisted value.
I feel like it’s not talked about enough that the ultimate irony of software engineering is that, as an industry, it’s aiming to make itself obsolete as much as possible. I struggle to think of any other industry that, completely on their own accord, has actively pushed to put themselves out of work to such a degree.
FWIW the “location based charge limits” are entirely up to the user; for example, I may want a full-charge at home but a limited charge at the office (where it might be paid).
A couple of recent software additions to my ‘23 MY:
* Dynamic speed profiles for Autopilot/FSD
* The ability to specify individual drop-off locations for FSD arrivals (curbside, parking lot, driveway, etc)
* Grok as a voice assistant for the infotainment system
* iOS live activity viewer for the Dog Mode camera feed
* Speed/steering/control statuses being overlaid on dashcam footage
* “Santa Mode” which revamps the UI with Christmas theming for the holiday season
* Automatic HOV lane routing based on vehicle occupancy status
* Vehicle alerts/chimes when exiting, if leaving your phone within the vehicle
* Location-based individual charge limits
* 3D visualizations of supercharger locations, synced with active availability/occupancy per stall
* The SpaceX docking simulator ported as an in-vehicle game, playable on the infotainment screen
These are all additions from just the most recent update, and I can confidently say this is the only vehicle I’ve had that consistently gets better and better in terms of its software features over the course of ownership. Each update takes anywhere from 20-45 minutes during which, unfortunately, you’re not able to utilize the vehicle at all.
It's worth noting that LLMs have been part of the tech zeitgeist for over two years and have had a pretty limited impact on hireability for roles, despite what people like the Klarna CEO are saying. Personally, I'm betting on two things:
* The upward bound of compute/performance gains as we continue to iterate on LLMs. It simply isn't going to be feasible for a lot of engineers and businesses to run/train their own LLMs. This means an inherent reliance on cloud services to bridge the gap (something MS is clearly betting on), and engineers to build/maintain the integration from these services to whatever business logic their customers are buying.
* Skilled knowledge workers continuing to be in-demand, even factoring in automation and new-grad numbers. Collectively, we've built a better hammer; it still takes someone experienced enough to know where to drive the nail. These tools WILL empower the top N% of engineers to be more productive, which is why it will be more important than ever to know _how_ to build things that drive business value, rather than just how to churn through JIRA tickets or turn a pretty Figma design into React.