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.
The callout about Uber is weird as it also fails to mention their autonomous vehicle was the first of its kind to provably kill a pedestrian, with full video of the accident available online.
Arduino and, specifically, the ESP8226 (basically an Arduino+Wifi) and ESP32 (Arduino+Wifi+BT) development boards are a fantastic place to start!
For most hobbyist-level electronics, it’s just a matter of becoming familiar enough with using the Arduino IDE to flash your C(-like) code to your board, or using something like MicroPython, then following the wiring instructions freely available online for common parts like servos, LEDs, displays, etc. Every once in a while you may have to reach for something like a transistor, capacitor, or resistor, but those can also be learned in an afternoon.
Google really is your friend! I taught myself hobby electronics over 15 years ago using the same, and they still hold up!
Surprised I seem to be the only one willing to ask; _why in the world would you wall the implementation behind a Google Form?_
Edit: Implementation details are actually readily accessible in the DOM. Here's a gist that extracts the relevant details (for those who, understandably, don't want to give out their email in exchange):