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,โฆ
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.
The garbage collection process is quite fail proof.
๐
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โฆ
Easy. Mosquitos.
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!"
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.
Front-end framework wars are yesterday's news. LLM model wars are the new hotness.
The behavior is static. Yes the services it calls are inverted dependencies, but the steps it goes through are static. What happens if they decide to add push notifications, or stop sending emails? The developer would have to either modify this method, thus violating OCP, orโฆ
I haven't seen this video before but it is absolutely ๐ฏ youtu.be/L2Wnq0ChAIA?siโฆ
youtube.com
YouTube
Vertical Slice Architecture, not Layers!
Me: Our team will be deploying at least once if not several times a day. SH: How often will you have to take the system offline for that? Me: Never. SH: *stunned silence* I relayed this story to my team, everyone laughed when I told them the stakeholders question. Not becauseโฆ
I am of the opinion that a Scenario is the smallest unit of work which the business should be observing and monitoring. A user story can be of a wide variety of sizes that simply describe what the user wants. It can be written as small as a single scenario, or as large as a fullโฆ
I often wonder why event driven architecture is primarily done for communication between systems, but not within a system. It seems like a perfectly good way to decouple and invert dependencies. Why do we stop once we reach inside the system boundary?
United States ํธ๋ ๋
- 1. #DWTS 35.2K posts
- 2. #DWCS 6,537 posts
- 3. #WWENXT 16.4K posts
- 4. Ohtani 12.6K posts
- 5. Yamamoto 10.6K posts
- 6. Robert 105K posts
- 7. Carrie Ann 4,192 posts
- 8. Haji Wright N/A
- 9. #RHOSLC 3,799 posts
- 10. Roldan 2,242 posts
- 11. #USMNT 1,303 posts
- 12. Elaine 58.7K posts
- 13. Whitney 15K posts
- 14. Young Republicans 54K posts
- 15. Max Muncy 3,703 posts
- 16. Dylan 32.6K posts
- 17. Yelich 1,583 posts
- 18. Politico 272K posts
- 19. Mr. Feeny 1,352 posts
- 20. Danielle 10.2K posts
๋ด๊ฐ ์ข์ํ ๋งํ ์ฝํ ์ธ
Something went wrong.
Something went wrong.