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/

Design by Decision Fatigue | QuestDB
https://questdb.com/blog/design-by-decision-fatigue/

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.

Solving a software problem, on the #vibeCoding scale:

↓ no vibes ↓

• Writing from internalized knowledge
• Reading documentation
• Reading a blog post on the topic
• Lifting from sample code
• Copy/pasting from StackOvervflow
• Adding yet another library dependency
• Using AI to write implementation

↑ nothing but vibes ↑

Hot take:

Human-written tests > No tests > AI-generated tests.

I think I prefer no tests to extremely complex, verbose and unmaintainable test code that just perfectly contorts around a code base and its defects.

The 13 software engineering laws - by Anton Zaides
https://newsletter.manager.dev/p/the-13-software-engineering-laws

"Would you happily go on-call for a system of fully AI-generated services?"

#softwareengineering #developerexperience #vibecoding

https://serce.me/posts/2025-31-03-there-is-no-vibe-engineering

Listen at: https://anonradio.net:8443/anonradio

This week we will talk about the Unix Philosophy and how it compares and contrasts with whatever one might call the “Emacs Philosophy.”

The impetus for the discussion is a series of blog posts by @ramin_hal9001 called “Emacs fulfills the UNIX Philosophy”:

• [The original introductory blog post](

  https://tilde.town/~ramin_hal9001/articles/emacs-fulfills-the-unix-philosophy.html

  )
• [The show notes](

  https://codeberg.org/ramin_hal9001/lisp-gopher-climate_chat-about-emacs/src/branch/main/show-outline.org

  )

…as well as a fascinating discussion that took place over this past week on ActivityPub on the topic of the Unix philosophy and history of Lisp on Unix in which some very knowledgeable people have contributed anecdotes and facts.

#technology #programming #SoftwareEngineering #RetroComputing #lisp #r7rs #SchemeLang #UnixPhilosophy

within each of us
our loved ones, in tiny form,
caring's innate yield
    company at a distance
    legacy in case of loss

Joined a new customer project today. The project started recently. Customer provides project director and business analysts. We provide architects/devs.
Watched a recap of a recent kickoff meeting to get familiar with the business domain and the project setup.
In this meeting I noticed that they presented a rough and very (very very) optimistic timeline.

Me: Were any technical people involved back then when you were setting the timeline?
Project Director: No. The dates are fixed. Why?
Me:

I would like to introduce you to "Vibe Management". Give in to the vibes, and embrace exponentials. It's like management, but not really. You just see stuff, copy stuff, and paste stuff, and it mostly works!

https://yieldcode.blog/post/vibe-management/

New intro now I am retired...

Looking to get into some #Indie #GameDev now I have time. Want to write the games I wanted to write all along: #Roguelike #Roguelite #ProceduralContent...

Also available to help other people with projects/personal development... Commercial or unpaid, drop me a message, the worst can happen is I don't know or am too busy.

Skills: #SoftwareEngineering #SoftwareDesign
#C++ #Teamwork, #C++, #Online

Development cycle time decays just like anything else in software. If not actively maintained, it gets worse over time.

I've worked on Clojure development cycles with tools.namespace and Component, but it's still hard: You have to intentionally design your code for interactive development and be careful not to break the feedback cycle.

https://github.com/stuartsierra/component.repl

One of my favorite memories from working in AAA video games:

I was at work late one night, like 11PM, during crunch. The lights were out at the office. I was sitting in my cubicle, with my headphones on, watching a Monty Python's Quest for the Holy Grail DVD on the TV hooked up to my Xbox devkit.

Suddenly, I hear a voice behind me. I turn to find my boss's boss's boss, a key producer on the project, behind me.

1/3

I am tested repeatedly every single day.

But, I have done something that is super cool and I have nobody to share it with, and nothing to show for it besides some passing tests.

https://github.com/zeyus/liblsl.dart/blob/main/packages/liblsl/ (readme is outdated, see tests)

HMU if you're a #softwareengineering , #networkengineering , #systemsarchitecture or #designpattern nerd, I'd love feedback and suggestions for improvement (or just question my sanity)

Happy Friday folks! Humble Bundle is . Just £25 for one of the best collections of O'Reilly books I've ever seen. If you're a Software Engineer or Architect, don't miss out!

https://www.humblebundle.com/books/head-first-programming-and-patterns-oreilly-books

Vibe coding is a prime example of the sheep mentality we have in tech.

Some out of touch tech bro says something stupid, and a new industry / profession is born out of it.

Want to use AI coding tools right? @BirgittaB shares real tips on Copilot, TDD, code review, and pair programming. #AIinDev #coding #SoftwareEngineering https://martinfowler.com/articles/exploring-gen-ai.html#memo-13