Markus Harrer

@markusharrer.de

325 Followers 264 Following

Software Development Analyst @innoq, Trainer @socreatory. I like fixing things. Legacy systems, Wardley Maps, DDD and Software Analytics fanboy. https://markusharrer.de/

The first lines of a Python script where the first line is "# vibe coded"
Developers before the MCP hype: Ugh, not another API from someone else I have to deal with... Developers during the MCP hype: Awesome! Another API from others I get to deal with!
Quality is all about the How, not the What.
The toaster handle fixed by a clip from IKEA for closing plastic bags.
An image from the movie Avengers: Endgame showing Captain America leading a group of heroes into battle, with the text 'FORMER TECH TWITTERERS ASSEMBLE'.
The image contrasts natural language issues with best practices in code. On the left, it shows problems in natural language: synonymy (one thing, many names like DataAccess, Repository, EntityHandler) and polysemy/homonymy (one name, many things like Client, Order, Entity). On the right, it illustrates the solution in code: integrity through consistent naming, where one thing maps to one clear concept, such as Customer, procurement.Order, and data.*Entity. The image emphasizes the importance of conceptual integrity in software architecture to prevent confusion.
The image illustrates an extended version of Simon Wardley's idea of evolution, incorporating the concept of "enshittification." It shows both the consumer and producer perspectives as a system evolves from its genesis to commodification and eventually to degradation or exploitation for profit (enshittification). Key stages include: - Genesis: Both producers and consumers have no clue/idea about the product. - Custom Built: It's something novel but starting to be seen/used. - Product (+rental): Used regularly by consumers, while producers are more accustomed to making it. - Commodity (+utility): It's embedded in daily life and is regularly provided. - Enshittification: The final stage, where the system is fully commercialized and optimized for profit at the cost of user experience.
An image of a book titled "Quality Tactics: Develop Quality-Driven Solution Strategies for Software Architectures" by Markus Harrer. The cover features illustrations of people interacting with various icons representing different quality tactics. The image also showcases various strategy cards like "Fake Progress Bar," "Parallelization," "Data Quality Checks," and "Microservices" with descriptions. A banner reads "Systematically find solutions aligned with quality goals," and there is a note about early access and PDF flashcards availability at https://leanpub.com/qualitytactics.