Links 2016-09-19

More stuff on cloud and service architecture.

Links 2016-09-14

  • What I learned as a hired consultant to autodidact physicists
    It began after I started as a teaching assistant at the department of physics. The first note was a classic – it proved Albert Einstein wrong. The second one solved the problem of quantum mechanics by dividing several equations through zero, a feat that supposedly explained non-determinism.
  • How to Recruit – Rands in Repose
    Recruiting and engineering must have a symbolic force-multiple relationship because the work they do together – the work of building a healthy and productive team – defines the success of your team and your company.
  • It’s Not Just Standing Up: Patterns for Daily Standup Meetings
    Daily stand-up meetings have become a common ritual of many teams, especially in Agile software development. However, there are many subtle details that distinguish effective stand-ups and a waste of time.
  • The Ultimate Guide to Remote Standups
    Remote companies have a unique opportunity to create optimal work environments for their their employees. With a few tweaks, the standup format helps remote teams get more done, faster.
  • Meditations Redux
    The company I helped start, DefenseStorm, just celebrated its second year […] I’m posting the lessons I’ve learned because I think they might be useful to others.
  • Being A Developer After 40 — Free Code Camp
    Hi everyone, I am a forty-two years old self-taught developer, and this is my story.

Links 2016-09-06

Some food for political thought, ranging from the IT perspective to the global economy.

  • What Amazon Learned From Microsoft
    SaaS is the new proprietary. Truly the AWS Console is this generation’s Visual Studio.
  • What is Google Up To?
    This has led us to a curious but reasoned inference, that Google is not always acting as a business in the conventional capitalist sense. The company’s motives at times appear to have a broader agenda, better described in social, even artistic terms, rather than exclusively business terms.
  • A lesson in social engineering: president debates
    There is no debate, there is only social engineering.
  • America Has Never Been So Ripe for Tyranny
    The freedom in that democracy has to be experienced to be believed — with shame and privilege in particular emerging over time as anathema. But it is inherently unstable. […] And it is when a democracy has ripened as fully as this, Plato argues, that a would-be tyrant will often seize his moment.
  • How American Politics Went Insane
    Chaos syndrome is a chronic decline in the political system’s capacity for self-organization. It happened gradually—and until the U.S. figures out how to treat the problem, it will only get worse.
  • The end of capitalism has begun
    Capitalism, it turns out, will not be abolished by forced-march techniques. It will be abolished by creating something more dynamic that exists, at first, almost unseen within the old system, but which will break through, reshaping the economy around new values and behaviours.
  • The Age of Disorder
    Authoritarianism, mercantilism, and nationalism are beginning to replace democracy, capitalism, and internationalism.

Links 2016-07-18

Thoughts and recipes to build and run systems and services.

  • How to build stable systems
    The first decision is easily the most important. It is one of ideology: the developers are in control of the software. Not the other way around. Managers are not in control of the software. Product Owners are not in control of the software. Developers are.
  • The 15-point DevOps Check List
    The checklist could help you proceed with setting up a DevOps culture but don’t consider it as a unique way to proceed with your organization transformation.
  • 10 Philosophies for Engineers
    In this post and podcast episode, I convey some loose philosophies about modern software engineering. These are strong opinions weakly held. I welcome debate and discussion.
  • 3 Reasons AWS Lambda Is Not Ready for Prime Time
    When I first sat down to write my microservice using Lambda, I really wanted it to be the greatest thing since sliced bread. […] Sadly, it was too good to be true.
  • Microservices & Einradfahren
    Zu meiner großen Enttäuschung muss ich nun feststellen, dass die Leute in der IT, bzw. Developer wie sie heute genannt werden, mit den gleichen Denkmustern arbeiten wie die Business Kasper.
  • Creating a Microservice? Answer these 10 Questions First
    Microservices appear simple to build on the surface, but there’s more to creating them than just launching some code running in containers and making HTTP requests between them.

DevOpsDays Kiel 2016

I finally attended my first DevOpsDays in Kiel. I cannot compare to other events in the DevOpsDays series, but in any case it was a wonderful small one-track IT conference. One with the cosy atmosphere because with less than 200 attendees you can talk to everyone. We had two great days with a beautiful venue on the science campus, good catering, several sponsors, competent speakers, and last but not least a professional and dedicated organizing team.

One interesting observation: DevOps certainly has become mainstream already; because even IBM tells us how to do it.

To see more impressions take a look at the flickr albums. For summaries of the talks read Manuel Pais’ articles on InfoQ (Day 1, Day 2).

Links 2016-05-17

A failure, a success story, and several thoughts on system design.

  • Inside the sad, expensive failure of Google+
    Create a social network or risk everything.
  • Jetbrains: The unicorn Silicon Valley doesn’t like to talk about
    The reason why Jetbrains has such little competition is because few startups and programmers are willing to learn and embrace non-sexy tech.
  • Why I Strive to be a 0.1x Engineer
    Given the cost of maintaining everything we build, it would literally be better for us to do 10% the work and sit around doing nothing for the rest of our time, if we could figure out the right 10% to work on.
  • Boring Systems Build Badass Businesses
    Build the most minimal solution you possibly can. See if customer’s like it, use it, and will pay enough for it. Only then build it into a full solution.
  • Logging v. instrumentation
    Logging and instrumentation are two perennially hot topics in software development generally, and seem to be enjoying a certain renaissance in the context of microservices particularly. And I see quite a lot of confusion on the topic.
  • How to build stable systems — Medium
    The first decision is easily the most important. It is one of ideology: the developers are in control of the software. Not the other way around. Managers are not in control of the software. Product Owners are not in control of the software. Developers are.

OSDC 2016

This year was my second OSDC, and the first one as a speaker. Thanks to Netways for organizing this great conference (and also for inviting me to talk there). The conference archive for 2016 with all presentation slides is now online.
Read the rest of this entry »

AWS Summit Berlin 2016

A few remarks on the AWS Summit in Berlin this April…

Thanks to several sponsors the event was free of charge and a welcome opportunity to visit Berlin. Given this background it is probably not fair to compare it to normal tech conferences. Although it did have several tracks with technical talks and presentations, most of them were on an introductory level so you might as well watch a few AWS webinar videos. So one has to see the summit as a pure marketing event, one you should attend to celebrate AWS itself, meet fellow AWS user group members, and see a few product demos as well as startup pitches.