Green-eyed Microsoft Mouse bundled with Word for $195

Microsoft Mouse was born 38 years ago.

  1. Gergely Orosz strikes again. This time with short Twitter thread about predictions about future of mobile engineerning

    • Kotlin Multiplatform will become the de facto native way to share code between iOS and Android;
    • Flutter will become the most popular way to build cross-platform apps;
    • Full-native mobile development is not going anywhere with large apps with millions of users;
    • Tooling will keep being an issue, and a pain point for most mobile teams;
    • Mobile engineering done at scale will keep being siloed: so much more than e.g. on the backend;
    • “Mega mobile teams” of 20-50+ mobile engineers working on a single app will keep increasing the coming years.
    • VC funding for mobile engineering tools and vendors will remain low. But VCs that fund the right teams will see large returns in 5-10 years.
  2. How Technology Architects make decisions A rather short article but very important summary on how to make architectural decisions. In short, four strategies (but check the whole article):

    • Compensatory Equal Weight – total of criteria scores
    • Compensatory Weighted Additive – total of weighted criteria scored
    • Non-Compensatory Conjunctive – drop those which doesn’t fit requirements
    • Non-Compensatory Disjunctive – choose what exceeds significantly in one of the categories, forget others

    Compensatory decisions are good when you have time and resources to analyze a problem, non-compensatory when you lack it.

    Fun fact: It’s all also used in marketing, to find out how a customer decides between alternatives.

  3. If you don’t document right, after some time you will need to analyze the code or even reverse engineer your system. Like US Army needs to find out how cooling system parts work in the most advanced aircraft B2 Bomber. I bet it won’t be a cheap contract!

  4. Simon Sinek about “non-existing soft skills”. There are hard skills, and when you excel in them, you become highly impacting individual contributor. But there are no “soft skills”, but “human skills”, which build trust in you among other people. And those skills make you a leader.

  5. How can you not be romantic about programming? When you code […] emotions are involved. Code, we say, can be: neat, nice, clean, crafted, baroque, minimal, solid, defensive, hacky, a hack, art, a piece of shit, the stupidest thing I’ve ever read, beautiful, like a poem.