Scaling Go Testing with Contract and Scenario Mocks
https://funnelstory.ai/blog/engineering/scaling-go-testing-with-contract-and-scenario-mocks
#HackerNews #ScalingGoTesting #ContractMocks #ScenarioMocks #SoftwareEngineering #TestingBestPractices
Military Standard on Software Control Levels
https://entropicthoughts.com/mil-std-882e-software-control
#HackerNews #MilitaryStandard #SoftwareControl #SoftwareEngineering #TechNews #Cybersecurity
What is a build system, anyway?
https://jyn.dev/what-is-a-build-system-anyway/
#HackerNews #buildsystem #programming #devtools #softwareengineering #techarticles
‘But [Vogel] wants developers shaped like the letter T – deep expertise in one domain, broad knowledge spanning many.
“Great developers are T-shaped,” he says. “They’re experts in their field who understand how their work fits into a larger system. You must broaden your T.”
What the hell shape I am goodness knows https://mastodon.social/@RuthMalan/115667191845472692
"Vibe coding is fine, but only if you pay close attention to what is being built. We can't just pull a lever on your IDE and hope that something good comes out."
That's not software engineering. That's gambling."
#WernerVogels, 2025
But ... when we say "vibe coding" we're specifically talking about *not* paying attention to what's being built. Usually because of lacking the base knowledge to understand it.
(1/3)
Has the cost of building software just dropped 90%?
https://martinalderson.com/posts/has-the-cost-of-software-just-dropped-90-percent/
#HackerNews #costofsoftware #softwaredevelopment #technews #startupinnovation #softwareengineering
Why Fighter Jets Ban 90% of C++ Features [video]
https://www.youtube.com/watch?v=Gv4sDL9Ljww
#HackerNews #FighterJets #C++Features #SoftwareEngineering #VideoAnalysis #AviationTech
CartyBoston
boosted
This video from a team lead at Google is fascinating.
Here's someone who has clearly seen the negative consequences of LLM adoption in software teams. He seems like a conscientious manager, talking about how it makes some people struggle, or resistant, and damages the social fabric of a team.
Yet, he's stuck in a frame that "AI is the future of work" and "AI makes better decisions," so everything he has to say about it is in terms of how to drive adoption, even when, he admits, it may have serious negative consequences.
The cognitive dissonance is striking, and familiar. He's working very hard to justify this policy of LLM use. He wants to "put his people first." The paradox comes from trying to force both of these views at the same time.
What if we just didn't force LLMs on people? What if it's not a net benefit? What if overcoming people's resistance means getting worse results? It feels like he won't let himself consider that possibility.
I ignore the spotlight as a staff engineer
https://lalitm.com/software-engineering-outside-the-spotlight/
#HackerNews #staffengineer #spotlight #softwareengineering #careerdevelopment #professionalgrowth
This video from a team lead at Google is fascinating.
Here's someone who has clearly seen the negative consequences of LLM adoption in software teams. He seems like a conscientious manager, talking about how it makes some people struggle, or resistant, and damages the social fabric of a team.
Yet, he's stuck in a frame that "AI is the future of work" and "AI makes better decisions," so everything he has to say about it is in terms of how to drive adoption, even when, he admits, it may have serious negative consequences.
The cognitive dissonance is striking, and familiar. He's working very hard to justify this policy of LLM use. He wants to "put his people first." The paradox comes from trying to force both of these views at the same time.
What if we just didn't force LLMs on people? What if it's not a net benefit? What if overcoming people's resistance means getting worse results? It feels like he won't let himself consider that possibility.
You Can't Fool the Optimizer
https://xania.org/202512/03-more-adding-integers
#HackerNews #You #Fool #the #Optimizer #optimization #programming #technews #softwareengineering
You Want Microservices, but Do You Need Them?
https://www.docker.com/blog/do-you-really-need-microservices/
#HackerNews #Microservices #Development #Architecture #SoftwareEngineering #TechTrends
Good engineers write bad code at big companies
https://www.seangoedecke.com/bad-code-at-big-companies/
#HackerNews #Good #engineers #write #bad #code #at #big #companies #badcode #softwareengineering #bigtech #programming #HackerNews
Andreas Wagner
boosted
2/n
* Context compaction: documentation vs. code.
* AI rift: part of the team doesn’t believe in AI, and the other part uses a lot. The two sides hate each other more and more.
* PR is for mental alignment (among humans).
* And Memento is the best movie for context engineering!
Human Layer CEO Dexter Horthy on Advanced Context Engineering and avoiding the “dumb zone”
Andreas Wagner
boosted
1/
Highly recommending this talk from AIE/CODE 2025 on how to code effectively as a team with AI:
* With coding agent, 40% of your context window is “smart zone”. Once it’s passed, expect more slop.
* How do you know you should start a new context (task): when your coding agent says “You’re absolutely correct!”
* Research, Plan, Implementation (RPI).
* Leverage-wise: R >> P >> I. Screwing up upstream costs big time.
1/
Highly recommending this talk from AIE/CODE 2025 on how to code effectively as a team with AI:
* With coding agent, 40% of your context window is “smart zone”. Once it’s passed, expect more slop.
* How do you know you should start a new context (task): when your coding agent says “You’re absolutely correct!”
* Research, Plan, Implementation (RPI).
* Leverage-wise: R >> P >> I. Screwing up upstream costs big time.
2/n
* Context compaction: documentation vs. code.
* AI rift: part of the team doesn’t believe in AI, and the other part uses a lot. The two sides hate each other more and more.
* PR is for mental alignment (among humans).
* And Memento is the best movie for context engineering!
Human Layer CEO Dexter Horthy on Advanced Context Engineering and avoiding the “dumb zone”
1/
Highly recommending this talk from AIE/CODE 2025 on how to code effectively as a team with AI:
* With coding agent, 40% of your context window is “smart zone”. Once it’s passed, expect more slop.
* How do you know you should start a new context (task): when your coding agent says “You’re absolutely correct!”
* Research, Plan, Implementation (RPI).
* Leverage-wise: R >> P >> I. Screwing up upstream costs big time.