Readit News> IV.1.8) Information about the Government Procurement Agreement (GPA) The procurement is covered by the Government Procurement Agreement: Yes
Googling the UK Government Procurement Agreement got me to:
> https://www.gov.uk/government/collections/government-standar...
which was when I realised this was a rabbit hole and while I am positive that somewhere deep in that rabbit hole would be a requirement for all procurement suppliers to meet ISO9000 or similar, I was going to have to spend hours finding it. Hours I don't have.
You can cheerfully dismiss this opinion if you like, I don't have the data to provide you evidence.
But I also think this proves my point; if you have to spend hours just finding out what the requirements are, you probably don't meet them.
> Quality Plans
> 6.1 The Supplier shall develop, within [insert number] Working Days of the Effective Date, quality plans that ensure that all aspects of the Services are the subject of quality management systems and are consistent with BS EN ISO 9001 or any equivalent standard which is generally recognised as having replaced it ("Quality Plans").
The Short Form Contract also have optional ISO 27001 or Cyber Essentials (which is, uh, an adventure on its own). But there's also an option for no certification required. It depends on the contract.
But yes, you're right. Dealing with requirements takes time and experience and you likely need a dedicated person (or team) to deal with it.
A prompt to generate similar output would be a good start.
At a base level, people are “upgrading” their Claude Code with custom skills and subagents - all text files saved in .claude/agents|skills.
You can also use their new tasks primitive to basically run a Ralph-like loop
But at the edges, people are using multiple instances, each handling different aspects in parallel - stuff like Gas Town
Tbf you can still get a lot of mileage out of vanilla Claude Code. But I’ve found that even adding a simple frontend design skill improves the output substantially
Nobody said do everything from scratch. The point is: basic networking (port forwarding, WireGuard) should not be beyond someone's capability as a software engineer.
"I use apt instead of compiling" is a time tradeoff. "I can't configure a VPN" is a skill gap. These are not equivalent.
If you choose convenience for whatever reasons, that is completely fine.
I could, I just choose not to and direct my interests elsewhere. Those interests can change over time too. One day someone with Tailscale can decide to explore Wireguard. Similarly, someone who runs their own mail server might decide to move to a hosted solution and do something else. That's perfectly fine.
To me, this freedom of choice in software engineering is not disheartening. It's liberating and exciting.
n.b.: the above quote is from The Matrix.
The chances of colliding with anything else would be tiny. In case of other commercial jets zero, thanks to TCAS at the least.
TCAS = traffic alert and collision avoidance system
How is grep a bad thing? I find myself using it all the time.
I’m not into graphical user interfaces. They overwhelm me. By the time I’ve clicked myself through the GUI or written some horrible proprietary $COMPANY Query Language string, I might have already figured out the bug using tried and tested CLI tools.
grep is all right, but sometimes I need to tease out a complex data relationship.