> This is a great insight. For software engineers coding is the way to fully grasp the business context.
> By programming, they learn how the system fits together, where the limits are, and what is possible. From there they can discover new possibilities, but also assess whether new ideas are feasible.
Maybe I have a different understanding of "business context", but I would argue the opposite. AI tools allow me to spend much more time on the business impact of features, think of edge cases, talk with stakeholders, talk with the project/product owners. Often there are features that stakeholders dismiss that seemed complex and difficult in the past, but are much easier now with faster coding.
Code was almost never the limiting factor before. It's the business that is the limit.
It’s perplexing; like the majority of people who insist using AI coding assistance is guaranteed going to rob you of application understanding and business context aren’t considering that not every prompt has to be an instruction to write code. You can, like, ask the agent questions. “What auth stack is in use? Where does the event bus live? Does the project follow SoC or are we dealing with pasta here? Can you trace these call chains and let me know where they’re initiated?”
If anything, I know more about the code I work on than ever before, and at a fraction of the effort, lol.
The project managers and CEOs who are vibe-coding apps on the weekend don't know what an "auth stack" is, much less that they should consider which auth stack is in use. Then when it breaks, they hand their vibe-coded black box to their engineers and say "fix this, no mistakes"
I think that for the average developer this might be true. I think that for excellent developers, they spend a lot of time thinking about the edge cases and ensuring that the system/code is supportable. i.e. it explains what the problems are so that issue can be resolved quickly; the code is written in a style that provides protection from other parts of the system failing; and so on. This isn't done on average code and I don't see AI doing this at all.
Can complain to your local MEP about that. They updated the passenger rights regulation recently, but still kept this/
Regulation (EU) 2021/782
> Railway undertakings may introduce a minimum threshold under which payments for compensation will not be paid. This threshold shall not exceed EUR 4 per ticket.
Sadly the MEPs cared more about railway companies than passengers.
Parship used to do this (not sure about their current practices, this was years ago): I once had a six-month subscription that would automatically extend by a year if you didn't cancel at least three months in advance (by letter or fax!). Especially dodgy in that line of business, because if you get lucky shortly before subscription runs out, you're literally giving away a year's worth of subscription that you're not going to use at all.
Many commercial leases run in 5-year increments with 2 5 year auto-renewals and a 90-180 day window in which to exercise the opt-out of auto-renewal. That window is often not set to end coincident with the end of the lease term for obvious reasons.
The discussion concluded with it being codified into law.
How it's gonna work apparently is that the image will be stored E2E-encrypted in the cloud and at the photographer you'll get a barcode that contains the URL to the image and the key to decrypt it. To upload the image into the cloud, the photographer will need to use a secure ID card to sign in.
> HaystackDB is accessed through a RESTful HTTPS API. No client library necessary.
That's cool, but but I would prefer to not reinvent the wheel. If you have a simple library, that would already be useful.
Some simple code or request examples would be convenient as well. I really don't know how easy or difficult your interface design is. It would be cool to see the API docs.
Yeah, it’s a bit of a chicken and egg problem. Since I don’t have a way to find potential customers I feel it’s too risky investing in stuff like client libraries and good API docs. But I can definitely understand you’d like to see more.
> By programming, they learn how the system fits together, where the limits are, and what is possible. From there they can discover new possibilities, but also assess whether new ideas are feasible.
Maybe I have a different understanding of "business context", but I would argue the opposite. AI tools allow me to spend much more time on the business impact of features, think of edge cases, talk with stakeholders, talk with the project/product owners. Often there are features that stakeholders dismiss that seemed complex and difficult in the past, but are much easier now with faster coding.
Code was almost never the limiting factor before. It's the business that is the limit.
reply