Recent searches
Search options
#softwareengineering
52 posts49 participants4 posts today
I have been having some fun in my #SoftwareEngineering class using ideas from Gordon Ramsay to help students see commonalities as well as bad and good behaviors. I have always found distance helpful for learners since, too often, when we think of ourselves doing the good/bad, we can't hear and think clearly.
Anyway, I decided to make some imagery for another time, and lookie #AI can be useful, though I probably killed three sea otters to make it.
"AI does not eliminate the need for structured thinking about how to solve problems, which is the core of programming. It presents a new layer of abstraction."
seldo.comAI's effects on programming jobs | Seldo.comThere's been a whole lot of discussion recently about the impact of AI on the market for web developers, for programmers in general, and even more generally the entire labor market. I find myself making the same points over and over, and whenever I do that it's time to write a blog post about it, so this is that.
Doom and utopia are not our only options
There are two extreme takes on the impact of AI on programmer jobs:
Cyberattacks are inevitable. Your response decides the damage. Learn what to do right after a breach.
Read the full blog: https://www.openexploit.in/incident-response-101-what-to-do-following-a-security-breach/
Senior Developer Skills in the #AI Age: Leveraging Experience for Better Results • Manuel Kießling
https://manuel.kiessling.net/2025/03/31/how-seasoned-developers-can-achieve-great-results-with-ai-coding-agents/
The Log Book of Manuel Kießling · Senior Developer Skills in the AI Age: Leveraging Experience for Better Results • Manuel KießlingHow time-tested software engineering practices amplify the effectiveness of AI coding assistants.
One thing I've seen demonstrated over and over in 30+ years of maintenance programming is that most organizations have no fucking clue on how their code works. This leads to an irrational fear of change, and illogical decisions on implementing changes.
Don't you love when software displays a message that something "completed successfully" when it actually wasn't successful?
Guys, you either handle errors or you don't. Both is fine with me. But don't lie to me.
Had a great time chatting with Sam and Richard on the Moonpig Tech Podcast about our journey into event-driven architecture (#EDA)!
We dig into the why, the how, and the real-world intricacies of building #EDA at #Moonpig
Listen now:
Apple Podcasts: https://podcasts.apple.com/us/podcast/episode-29-event-driven-architecture/id1469387549?i=1000702164445
Spotify: https://open.spotify.com/episode/4gb6Biivs8zIvyNL8UOGLy?si=82f47ef1860243d1
Apple PodcastsEpisode 29 - Event Driven ArchitecturePodcast Episode · Moonpig Technology Podcast · 04/04/2025 · 15m
"My current conclusion, though preliminary in this rapidly evolving field, is that not only can seasoned developers benefit from this technology — they are actually in the optimal position to harness its power.
Here’s the fascinating part: The very experience and accumulated know-how in software engineering and project management — which might seem obsolete in the age of AI — are precisely what enable the most effective use of these tools.
While I haven’t found the perfect metaphor for these LLM-based programming agents in an AI-assisted coding setup, I currently think of them as “an absolute senior when it comes to programming knowledge, but an absolute junior when it comes to architectural oversight in your specific context.”
This means that it takes some strategic effort to make them save you a tremendous amount of work.
And who better to invest that effort in the right way than a senior software engineer?
As we’ll see, while we’re dealing with cutting-edge technology, it’s the time-tested, traditional practices and tools that enable us to wield this new capability most effectively."
The Log Book of Manuel Kießling · Senior Developer Skills in the AI Age: Leveraging Experience for Better Results • Manuel KießlingHow time-tested software engineering practices amplify the effectiveness of AI coding assistants.
The best way to build confidence in your solution…
…Is to get early feedback.
Discuss your ideas before implementing them. Get someone to eyeball your solution as early as possible. Deploy something and let people have a play as soon as you can.
Too often, I've found myself tucked away working on a feature, going deeper and deeper down that rabbit hole...
"Kill one mainframe. Successfully replace the software running in one mainframe. Let us know how you achieve that — and then update your timeline. That would be orders of magnitude easier than what is being claimed here."
Think your website is safe? Think again. These are the Top 10 web vulnerabilities you MUST know in 2025!
Read the full blog: https://www.openexploit.in/understanding-the-owasp-top-10-key-web-vulnerabilities-explained/
What's wrong with AI-generated docs - passo.uno https://passo.uno/whats-wrong-ai-generated-docs/
passo.uno · What's wrong with AI-generated documentationIn what is tantamount to a vulgar display of power, social media has been flooded with AI-generated images that mimic the style of Hayao Miyazaki’s anime. Something similar happens daily with tech writing, folks happily throwing context at LLMs and thinking they can vibe write outstanding docs out of them, perhaps even surpassing human writers. Well, it’s time to draw a line. Don’t let AI influencers studioghiblify your work as if it were a matter of processing text. It’s way more than that.
I built a blog to teach cybersecurity from scratch—here’s everything I’ve learned so far!”
Read the full blog: https://www.openexploit.in/i-built-a-blog-to-teach-cybersecurity-heres-what-ive-learned-so-far/
I have now encountered several cases of unintelligible documentation - functional requirements, security measures, technical how-tos - where I had to ask the author for clarification, and getting as a reply "oh I don't know; I just asked #ChatGPT".
Now I can bash #ai tools, but people who produce documentation that they themselves don't understand have always been a blight on #IT. It's irresponsible, unprofessional, and makes work harder for everyone.
Found my flowchart stencil / ruler! Bought this from the University of Oulu bookstore in the early 2000s. Because it was kinda quaint. We have diagram software these days and this thing doesn't have UML obviously.
Now, where the heck did I put my typographical ruler that came with that old art software...?
#programming #softwareengineering #softwaredesign #flowchart
Now, where the heck did I put my typographical ruler that came with that old art software...?
#programming #softwareengineering #softwaredesign #flowchart
"The real innovation, the sustainable progress, comes from maintaining deep understanding while embracing AI's capabilities."
N’s Blog · Karpathy’s ‘Vibe Coding’ Movement Considered HarmfulLast Tuesday at 1 AM, I was debugging a critical production issue in my AI dev tool. As I dug through layers of functions, I suddenly realized — unlike the new generation of developers, I was grateful that I could actually understand my codebase. That’s when I started thinking more about Karpathy’s recent statements on vibe coding. For those who missed it, Andrej Karpathy recently shared his thoughts on what he calls “vibe coding” — essentially surrendering code comprehension to AI tools and hoping for the best. His exact words? “I ‘Accept All’ always, I don’t read the diffs anymore.” I have learnt a lot from Karpathy and use AI tools daily, but there’s a world of difference between augmenting your capabilities and completely surrendering your understanding.
️