EzProgramming's profile picture. I help organizations overcome the challenges of software development. DM is always open.

Steve (Big Red) Bishop 👨‍💻

@EzProgramming

I help organizations overcome the challenges of software development. DM is always open.

固定されたツイート

Bishop's Law revised Parallel Systems: R = O(α log C + β) Concurrent Systems: R = O(α C + β) The addition of O() uses Big O notation for asymptotic upper bounds, while "log" reflects logarithmic scaling in optimized parallel implementations, versus linear in naive ones. These…

Bishop's Law: Work done in async requires a resync. As the work complexity increases, so does the resync complexity. Resync complexity: R = αC + β (for independent streams/parallelism) R = αC² + β (for conflicting streams/concurrency), Where C is total async work complexity,…



Are you writing user stories or are you writing role stories? If you're writing role stories then you are already on the path toward process over people.


God I hope so.

90% of all new .NET projects in 2026 will use Vertical Slice Architecture Are you still using Clean Architecture or N-Layered? In modern software development, there are 4 popular approaches to structuring your projects: • N-Layered Architecture (Controller-Service-Repository)…

AntonMartyniuk's tweet image. 90% of all new .NET projects in 2026 will use Vertical Slice Architecture

Are you still using Clean Architecture or N-Layered?

In modern software development, there are 4 popular approaches to structuring your projects:

• N-Layered Architecture (Controller-Service-Repository)…


Dave: So you took my picture. Me: Yes Dave. Dave: Then ran it through AI. Me: Yes. Dave: Just to make this meme? Me: Correct!


Easy, MAG.

If they took baldurs gate 1 & 2 and icewind dale info the baldurs gate 3 engine that would be freakin sweet

memeslich's tweet image. If they took baldurs gate 1 & 2 and icewind dale info the baldurs gate 3 engine that would be freakin sweet


I really don't understand businesses obsession with thick chucky projects. They are the least valuable and highest risk type of work that can be done. Every day you don't have a product in your customers hand is a day of lost revenue and feedback. So why do everything in your…


98c/gal

I remember .99 cents. What is the lowest you remember?

Sadie_NC's tweet image. I remember .99 cents. 
What is the lowest you remember?


If you aren't fixing the biggest bottleneck, you're rearranging deck chairs on the Titanic.


It's basically Parkinson's law at the CPU cycle level.

Software engineers have negated every advancement in transistor density, computer architecture, compilers, and computer networking over the past 30 years.

bubblebabyboi's tweet image. Software engineers have negated every advancement in transistor density, computer architecture, compilers, and computer networking over the past 30 years.


The garbage collection process is quite fail proof.

An old-school memory management technique.

davidcrawshaw's tweet image. An old-school memory management technique.


😅

Zuckerberg employees inventing React.js



Steve (Big Red) Bishop 👨‍💻 さんがリポスト

What they imagine is "programming under surveillance," which I tried to explain: industriallogic.com/blog/programmi… It is a horrible thing to imagine, but imagination always warns us of possible trauma first. You have to get past that to see opportunity. Actual co-creation is great & fun!

Why is it that the people who seem to have the strongest negative opinions about Mob/Ensemble programming are usually the people who have never experienced it? The thing they imagine has nothing to do with the real thing, but that doesn't stop them from having opinions. Welcome…



I'm sounding like a broken record these days. The problem is not indirection (too many little modules) the problem is DISPERSION. It's that you have too many tiny little modules scattered all around in different folders/packages/projects/libraries. If you had a bunch of little…

Code quality involves making code easier to read and change. Some of the worst code quality comes from getting "easier to change" wrong. We have this curious idea that somehow lots and lots of so-called abstractions will make future changes easier. That is the highway to hell.…



If your team does not have consistent hours each day for uninterrupted "heads down" time, you cannot possibly expect consistent throughput.


Want to know how much value something has for you or your business? Ask how much pain you would be in without it.


I think opinionated Agile gets a bad rap.


LLM's are all too easy to anthropomorphize. Our lizard brains see faces in toast. Is it any wonder it sees thinking in extremely good predictive text algorithms?


"So your teams aren't delivering software on schedule." "That's correct, Dave" "So you're implementing Scrum." "Correct" "To add meetings to their schedule for talking about how they can get more stuff done." "Correct!"

EzProgramming's tweet image. "So your teams aren't delivering software on schedule."

"That's correct, Dave"

"So you're implementing Scrum."

"Correct"

"To add meetings to their schedule for talking about how they can get more stuff done."

"Correct!"

Steve (Big Red) Bishop 👨‍💻 さんがリポスト

I’m not anti-AI. I am, however, anti the rapacious tech bros who selfishly hype AI for the purpose of increasing their wealth and power at the expense of our humanity.


Vibe coders remind me of the people who build applications in MS Access for their department using macros. At some point when they need to scale, or tweak existing logic, they require someone who actually knows what they're doing to take over.


Loading...

Something went wrong.


Something went wrong.