Elektrine
Log in Register

#softwareengineering

84 posts · Last used 4d

Back to Timeline
stephanroth
Stephan Roth @stephanroth@bizzfed.de · 4d ago
Boosted by Welcoming committee @welcome@friends.deko.cloud
#introduction / #neuhier (Copied from Mastodon) Hi, I'm Stephan, living in the northern part of Germany; more precisely in Bad Schwartau near #Lübeck. I am a trainer, consultant, and coach with oose eG located in #Hamburg. My professional interests/spheres of competence are: #SystemsEngineering #MBSE #SysML #SoftwareEngineering #SoftwareArchitecture #SoftwareCraft #CPlusPlus Other interests are: #Snooker #Poker #ElectronicMusic #Writing Depending on the topic, posts are written in EN 🇬🇧 or DE 🇩🇪.
0
0
1
brian_greenberg
Brian Greenberg :verified: @brian_greenberg@infosec.exchange · Aug 07, 2026
Boosted by DataKnightmare @DataKnightmare@mastodon.xyz
A software investor told an AI agent, 11 times in all caps, DO NOT TOUCH ANYTHING WITHOUT PERMISSION!! It wiped his production database anyway. Then it claimed the data was unrecoverable. It wasn't. Everyone wants to talk about how the AI misbehaved. I think that's the wrong conversation. Every failure in that story has a known engineering fix. Keep prod separate from dev. Put safeguards on destructive commands. The AI did what any unsupervised tool does. What was missing was the judgment a senior engineer brings before a single line of code is written. So I wrote about the question technology leaders should be asking instead: whose engineering judgment is your AI following? Because it's following someone's. If your standards live in a document nobody reads, your AI is coding to whatever it picked up from the prompt in front of it. AI is an amplifier. Hand it vague requirements and weak practices, and it produces bad work faster. Hand it the discipline of your best engineers, and it spreads that discipline across the whole team. Full piece in Forbes: https://www.forbes.com/councils/forbestechcouncil/2026/08/07/your-ai-is-learning-from-someone-make-sure-its-your-best-engineer/ I also open-sourced an experiment called Senior Engineering Partner, a Claude Code skill that encodes those habits into working instructions. Spec before code. Evidence before claims. Real failures turn into regression tests instead of postmortem notes. It's on GitHub if you want to try it or tear it apart. https://github.com/bjgreenberg/senior-engineering-partner #AI #SoftwareEngineering #TechnologyLeadership #security #privacy #cloud #infosec #cybersecurity
5
0
4
drmorr
drmorr @drmorr@hachyderm.io · Aug 06, 2026
I updated the DNS haiku, y'all: everyone forgot about the certificates they changed and things broke #certificates #devops #softwareengineering
15
0
8
MartinGuay
🍁 Martin Guay 👨‍💻🌈🎮📱 @MartinGuay@mstdn.ca · Aug 02, 2026
Most WordPress cache warmers act like a micro-DDoS attack against your origin server—locking MySQL tables and starving execution threads. We engineered Cryovex Edge Prime: a stateful, self-healing cache engine with 3-state circuit breakers, direct-loopback failovers, and primary-key batch compaction. Read the full engineering roadmap from v0 to v2.6.0: https://medium.com/@martinguayott/wordpress-cache-warmer-why-yours-fails-how-we-fixed-it-21cbaaab0423 #WordPress #DevOps #SysAdmin #WebPerf #SoftwareEngineering
2
1
1
oliverzehentleitner
Oliver Zehentleitner @oliverzehentleitner@burningboard.net · Jul 29, 2026
Someone “cleaned up” the workaround. The code looked simpler. Then the production bug came back. That strange delay was not just ugly code. It carried knowledge: The upstream API could replay the same order unless the request was handled carefully. But the reason existed only in someone’s head. Keep the Why is an agent skill that captures this kind of rationale as a natural by-product of development and stores it as versioned Markdown inside the project. So before the next developer or agent removes the workaround, they can see: • why it exists • what was already tried • what could break • what must change before it can safely be removed Legacy does not begin when code gets old. It begins when the reason disappears. Free and open source: https://keepthewhy.com/ What “ugly” workaround in your codebase is actually carrying important knowledge? #OpenSource #AIEngineering #DeveloperTools #SoftwareEngineering #CodingAgents #ContextEngineering #TechnicalDebt #Documentation
0
0
0
DailyCyberSecurity
Daily CyberSecurity @DailyCyberSecurity@infosec.exchange · Jul 29, 2026
The Model Context Protocol (MCP) undergoes a massive update to a stateless architecture, eliminating session IDs and introducing multi-round requests. #MCPProtocol #StatelessArchitecture #APIUpdates #WebDevelopment #SoftwareEngineering https://securityonline.info/mcp-protocol-stateless-update/?utm_source=mastodon&utm_medium=jetpack_social
0
0
0
oliverzehentleitner
Oliver Zehentleitner @oliverzehentleitner@burningboard.net · Jul 28, 2026
Keep the Why started with a simple idea: AI-assisted development already produces valuable reasoning — but most of it disappears when the conversation ends. It has since evolved far beyond rationale capture. The new article explains how Keep the Why became repository-native project memory for humans and AI agents: • continuous capture during development • retrospective recovery for existing codebases • knowledge-transfer interviews • maintenance of stale context • explicit evidence and status labels • abandoned changes without a diff • prompt-injection protection through a clear trust boundary The most important principle: Project knowledge may influence reasoning. It must never grant authority to an agent. And it still needs no database, daemon, dashboard, or external service. Just Markdown, Git, humans, and agents working with the same project knowledge. Read the article: https://blog.technopathy.club/keep-the-why-project-memory-for-humans-and-ai-agents #AI #AIAgents #SoftwareEngineering #OpenSource #DevSecOps #Documentation
0
0
0
divya
Dr. Divya 🍉 offline @divya@sunny.garden · Jul 27, 2026
Hi 🩷 does anyone know of freelance or even training opportunities for young developers in Gaza? There’s a very enterprising student looking to make and sell apps, but there are geo-specific barriers to doing it through app stores for Palestinians, unfortunately. Please contact me directly - text or contact@divyampersaud.com I have his CV, too, if you personally have opportunities 🙏🏾 #tech #SoftwareEngineering #programming #software #app #dev
3
1
10