Agile

Companies are complex systems made up of humans and technological systems in perpetual interaction. “Theses socio-technical” systems are Romain's favorite subject. Melvin Conway observed that the communication structures of organizations directly influence the design of technical systems produced by those organizations. In short: the organization chart of the company and the interpersonal relationships across people have more influence than designers and architects!

Tl;dr In my experience, software developers’ skills regarding tasks in a terminal range from desperately slow to impressively swift. I believe that, for a large part, this is caused by an abundance of articles not discussing the real problems software developers are dealing with daily. Namely, how to feel productive on a terminal, after using omnipotent integrated software environments for so long. This article aims at bridging this gap by sharing carefully selected tips that can, in my opinion, dramatically increase the terminal productivity of…

"What if we scaled agile to the entire company..." This is a phrase heard more often than not in companies that becoming more mature at Agile. But what does this sentence mean exactly? What does the idea of ​​"scaling up" imply? Are there solutions that can be applied quickly? Quick overview: Did you say Scaled Agile Framework? What triggers an Agile transformation "at scale"? SWARMing, what is it? A strategy for using scaled agile frameworks ==> Read the entire article (free) <==

The First Law of Technology Transfer: Long-range good tends to be sacrificed to short-range good. The Second Law of Technology Transfer: Short-range feasibility tends to be sacrificed to long-range perfection. Jerry Weinberg - Quality Software Management In this discussion, the term: heuristic refers to a method used in a given context, with no guaranteed outcome, that possibly contradicts other heuristics, and which helps reduce the time required to find a solution. The acceptance of such heuristic depends on the context of use, and not on…

Let’s talk about communication for a bit. One of the most interesting roles I’ve had to fulfil the last couple of years has been the “Operations guy working as a part of a Development team”. This is a fascinating situation to find yourself in. Allow me to elaborate. Historically, Operations teams have been isolated from Development teams. Two separate organizational entities. The reasons for this were manyfold: Operations people were a scarce resource, they needed to accommodate vast amounts of work for numerous Development teams…

Alright, story time fellas. TL;DR; We’re working with Terraform, layering and workspaces. This makes the standard `terraform workspace select x` pretty cumbersome and dangerous. We wrote a Ruby wrapper using Test-Driven Development. It allows us to have a tested, maintainable and efficient solution to the aforementioned issue. You can find the actual project here: https://github.com/sebiwi/terraform-wrapper If you keep reading, we’re going to talk about scripting, Test-Driven Development, Terraform and Ruby.

This is another episode of the “The Wizard” series. If you haven’t read the previous episodes, you can find them here and here. You just don’t know how to do it. You’ve been thinking about it for a while too. It’s an important issue. The crafting of the spell is the most important part. The journey is usually more important than the destination itself. But you don’t feel like you are doing it right.

Auth0 is a SaaS platform that offers a set of tools to implement Authentication and Authorization for your web, mobile and legacy applications. This platform provides a great developer experience with a good documentation and innovative features, such as rules, JavaScript functions that are executed when a user authenticates to your application.

What purpose? How? When? Everything you need to know about BDD in one drawing.

Interview with Woody Zuill who will be teaching a Masterclass Mob programming with Octo Academy on May 28th.