Archive for the 'Links' Category

Links 2017-01-23

Links 2017-01-19

On programming…

Links 2016-12-08

A few notes on monitoring, debugging, and testing.

  • Chris’s Wiki : blog/unix/ManyLoadAveragesOfUnix
    It turns out that the meaning of ‘load average’ on Unixes is rather more divergent than I thought it was. So here’s the story as I know it.
  • Illustrated Guide to Monitoring and Tuning the Linux Networking Stack: Receiving Data
    This blog post expands on our previous blog post Monitoring and Tuning the Linux Networking Stack: Receiving Data with a series of diagrams aimed to help readers form a more clear picture of how the Linux network stack works.
  • Using jemalloc to get to the bottom of a memory leak
    The opportunity to really get to the bottom of a memory problem is quite a rarity in the life of a developer and this showed in the fact that our investigations (alongside other work) lasted over a month.
  • Ten Tired Trends In Software Testing Discourse
    I’ve read your blog posts and I’ve been to your talks and talked to you after the talks too. And here’s what I want to know: if you love automation so much how come all you can do is warn me about how not to use it?
  • Notes on concurrency bugs
    Non-deterministic bugs are rare, but they can be extremely hard to debug and they’re a productivity killer. Bad non-deterministic bugs take so long to debug that relatively large investments in tools and prevention can be worth it.
  • Why Writing Correct Software Is Hard
    The cost of correctness – like the energy cost of reducing entropy – is a result of the “natural laws” of computation, that cannot possibly be avoided.

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.

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.