“More than 95% of your organization’s problems derive from your systems, processes, and methods, not from your individual workforce. Your people are doing their best, but their best efforts cannot compensate for your inadequate and dysfunctional systems.” – Peter Scholtes
- User Research Will Destroy Your Product
- R rises to #12 in Redmonk language rankings
- Upstart - The Engineer's Path: 2 Decisions That Define a Career
- The hidden costs of serverless - Evaluating the real costs of serverless architecture is tricky
- On the criteria to be used in decomposing systems into modules – a review of the legendary Parnas paper from 1971.
- ”In conclusion, while much attention is given to the need to divide a system into modules (microservices), much less attention has been given to the criteria by which we decide on module boundaries”
- “We have tried to demonstrate by these examples that it is almost always incorrect to begin the decomposition of a system into modules on the basis of a flowchart. We propose instead that one begins with a list of difficult design decisions or design decisions which are likely to change. Each module is then designed to hide such a decision from the others. Since, in most cases, design decisions transcend time of execution, modules will not correspond to steps in the processing…”
- The emperor has no clothes - why do we estimate?
- How to break a Monolith into Microservices
- Bitcoin is the greatest scam in history - It’s a colossal pump-and-dump scheme, the likes of which the world has never seen.
- The Wrong Questions about Agile -One of the more common "wrong" questions I get is "what's the role of the Project Manger in an agile shop?"
No comments:
Post a Comment