It's buzzword bingo, which has been the trend for decades.
I joked thirty years ago that everything was Object-Oriented, even when it wasn't.
06.03.2026 12:51
👍 0
🔁 0
💬 0
📌 0
It's buzzword bingo, which has been the trend for decades.
I joked thirty years ago that everything was Object-Oriented, even when it wasn't.
My most recent blog entry - Steps to Obtain a Software Engineering Internship - Getting an Internship is a Lot Like Dating
jhumelsine.github.io/2026/03/03/i...
I still recall these days from college:
As the entries accumulated, I realized I needed to provide some organization to it as well. So I created a Table of Contents page too: jhumelsine.github.io/table-of-con...
I feel the same. I'm a bit ahead of you. I retired almost 3 years ago after a 38 year career in software.
I created a blog as my retirement project: jhumelsine.github.io
Also consider mini versions of other companies that people already understand, such as eBay, Twitter or Amazon.
There are lots of relatively simple Actors and Boundaries in each of these in mini form.
Interesting scenarios ...
* What happens to other Applications when all Job slots are filled?
* What happens when a Candidate withdraws?
* Can AI find good Candidates for Jobs without human intervention? What about bias?
An ATS has:
* Candidates, with name, contact info, resume(s).
* Jobs, with attributes
* Applications, i,e., Candidate applies for a Job. Each Application has an interview process workflow.
* Notifications when things happen, such as offer/reject.
...
My last employer's product was an Application Tracking Software (ATS) product.
I used a simplified version for some Event Storming training sessions.
...
My most recent blog entry - You Studied Computer Science. Your Career Will Be Software Engineering - An Introduction to a Software Engineering Career Path
jhumelsine.github.io/2026/02/11/c...
The pendulum continues to swing.
Time to think has been squeezed out of the schedule.
I like slow processes, because they give me time to think.
This was a major theme in my blog where I described my design process: jhumelsine.github.io/2024/05/28/d...
I have also overhauled the Table of Contents with more structure including a more complete True Stories section, new Cautionary Tales section and new index of Complete Code Examples.
Blog Update. I have spent the past month reviewing my blog entries, fixing broken links, minor phrasing updates, etc.
...
jhumelsine.github.io/table-of-con...
"The strength of JavaScript is that you can do anything. The weakness is that you will." — Reg Braithwaite
ToS Tip
Most ToS agreements are online. Copy and paste them into ChatGPT, or equivalent, and ask for an easy to read summary. Ask for the pros and cons. Ask about your rights and responsibilities. Etc.
This isn't perfect, but it's better than nothing. It can be enlightening to see what it reveals.
Agreed. AI is a force multiplier. It will make good developers better and bad developers worse.
Like any tool, it's power lies in the hands of the craftsperson. One can use a circular power saw to build a cabinet or cut off one's thumb.
I'm retired now, so only speaking from past experience.
The biggest problem I faced was the lack of coherent software architecture.
"We build our computer (systems) the way we build our cities: over time, without a plan, on top of ruins." — Ellen Ullman
After I solved an Advent of Code problem this past year on my own, I would ask ChatGPT to solve it.
I copied the problem as described without any modification. Then I asked it to create a Java implementation.
In most cases, it generated the correct answer on the first try.
I prefer the term "Monkey Paw Coding."
It gives you what you asked for but not necessarily what you wanted.
I prefer "Test Double".
We use them to emulate dependencies without depending upon the dependencies.
I've seen some tests that only seemed to test the mock!?
jhumelsine.github.io/2024/07/02/t...
Logging and Observability are on my blog backlog, and this blog will definitely be included as a reference.
However, my blog backlog is so long that it will probably be years before I get to it.
I learned some of SumoLogic's log searching tools in the last year of my career. It was like moving from mining for gold with pick and shovel to industrial grade mining tools. I found all sorts of things once I knew how to reveal them.
Thanks for the referral. Very interesting.
I don't think I ever saw good logging in my career. Too many useless things were logged. Never enough useful things were. And important info (context) was often omitted. It was always looking for the needle in the haystack.
I referenced the Unix Philosophy briefly in my Domain-Specific Language blog when describing the Interpreter Design Pattern.
jhumelsine.github.io/2024/03/18/i...
What you describe sounds very much like the Unix Philosophy. en.wikipedia.org/wiki/Unix_ph...
Each Unix operation did one thing with ASCII Standard In/Out. Pipes were the glue. You could build new operations from others.
It was a great shell environment.
