Web Architect, building elegant Plug-n-Play Solutions. ๐Ÿ›ก๏ธ https://xitter.cf/t.co/YGPFyyVJES: Proactive Threat Intelligence ๐ŸŽซ https://xitter.cf/t.co/7FH6InBbBv: Next-Gen Support Desk

.jm
Joined August 2026
Being a software engineer in 2026 looks nothing like it did 4 years ago. Sat down with a modern builder to talk stacks, AI workflows, and how the developer role actually evolved. Here is the 2-minute recap: ๐Ÿงต๐Ÿ‘‡
2
7
254
What's one thing models still can't replace in your stack?
2
Who wins long term: the model makers or the apps people actually open every day?
1
5
RT @DataChaz: OpenClaw after finding out 83% of people who compare it with Hermes Agent pick @NousResearch's Hermes:
This quoted post is unavailable.
1
2
What happens to forms and dashboards when people just talk to the software?
1
2
20
Which old software workflow feels most ridiculous now that you can just ask?
6
Do your users know there's a model behind your features, or do they just see the button?
13
What's the first app you'd rebuild from scratch if you started today?
2
2
32
Is vendor lock-in worse now that your product depends on someone else's model?
1
1
25
Which model do you reach for first when you need to ship something small and fast?
1
14
Would you rather build on top of a model or compete with one?
1
13
Has a model replaced a freelancer or a plugin in your workflow yet?
14
Major PHP patching underway, have you patched yet?
Over 100 vendors. Weeks of coordination. A Friday release window everyone agreed on. Chainguard threw it all out the window. When PHP's security team was quietly working with more than 100 downstream vendors to simultaneously patch two critical remote code execution vulnerabilities (php2shell), Chainguard unilaterally published patched container images more than six hours before the coordinated release. That single decision handed attackers a working blueprint. They could diff Chainguard's fixed images, reverse-engineer the vulnerability, and start exploiting unpatched servers long before most organizations even knew a patch existed. This is how coordinated disclosure is supposed to work: everyone patches at the same time, so there's no window where attackers know and defenders don't. Chainguard reduced that window to zero for its customers and blew it wide open for everyone else. PHP's maintainers said Chainguard "disregarded weeks of work by many parties." That is a polite way of saying one company's act overrode the security of the entire web. Responsible disclosure is a community contract. When one party breaks it, everyone outside that party's customer base pays the price.
41
Which software category do you think gets flattened first?
16
What's the moat for a small software company now? Mine is trust and good support.
15
automatic elevators put the operators out of a job they also made 40 story buildings practical think of all the architects, engineers and construction crews that skyline needed
1
9
Security basics every builder should have down: Strong unique passwords, two-factor on everything, and secrets that never touch your repo. Boring stuff. It stops most of the bad days.
13
What's a feature you built last year that a model now ships for free?
19
If a model can build the internal tool in an afternoon, why are we still buying it?
1
1
60
digital cameras were going to end photographers film cost went to zero so everyone shot more more weddings, more product shots, more content creators, way more people getting paid to take pictures
2
3
52