agounaris

Where's the AI stuff? :D

This model seems super expensive! I interpret it as traces on steroids which will make query complex and slow!

A lot of businesses haven't even nailed simple histograms with prometheus. I wouldn't like observability to become a full set of problems on its own!

Also timeseries is powerfull in observability because a lot of issues can be represented as cheap counters, gauges and distributions. I want to see a paradigm complimentary to this simple principle instead of producing nested documents with nested objects.

a 2-9% improvement at global scale is insane! This is not a small number by any means.

Starting with the example, I find it counterproductive because our brains are always going for the condition first. (or my brain)

Waiting on a traffic light the thinking is "if light is red/green, then wait/cross" its not like "don't cross unless its green".

Also if there is only one obvious way to do things it's a productivity boost! I cannot stress enough how many times we have debated coding styles, wasting precious development time! No customer cares of your coding style! If you are an engineering who cares more about the length of a line or the import order instead of a critical feature for the customer, you have to rethink the priorities.

I kind of see this as just another yaml abstraction on top of configuration templates. This is not new or different in any way from what we have now.

What I don't understand with patent trolls is how this will even go a trial? How does this work?

There is a random lawsuit therefore you'll either have to pay or go to a trial? Who accepted the lawsuit in the first place and based on what legal ground?

"I kept freaking out and yelling in chats"

I think the interviewer is the problem....

Terraform could have been stateless if the target provider was stateless as well.

Having said that I don't mind state at all! There is always a storage layer and a schema somewhere storing some kind of information.

I was expecting to find some interesting thoughts on this one, but its the usual rant of the "freelancer" who does not understand what production means!

Yes big companies have productivity issues, however they have to create software which will outlive most engineers working at the business. You cannot reach the SLOs of google by hacking something together in 2 months!

Excuse me but I don't see in there any reference to what made peloton stock "actually" explode which was the enforcement of wfh. This is a VERY biased deck.

Is there any practical example on this? Whats a common use casE?

This could be one of the reasons why tech interviews are awkward. Most of them are "optimised" for tall and fat engineers but what you actually get is "luck of the draw" T shaped engineers on random specialties that you may not even need, with the assumption that the T shaped engineer can be transformed on demand to a short and fat or tall and skinny.

The author is very cynical on this series for businesses but I think there is a lot of truth in those writings. There is something fundamentally broken in the way we govern software products. From the interview process to the evaluation of the individual.

No engineering organisation can survive with just engineers. For many reasons. This limitation requires some roles to be there to support this process.

I think that most businesses practice process management. A person is there to make sure the team is compliant with the way the CEO, the board, the VPs etc, want to run the business.

What if we ban the term "manager" completely and instead focus on self organising teams and naturally elected leaders. Those leaders will go down with the team or be rewarded with the team. What if we treat product development like a well organised heist! The mastermind, the hacker, the explosives expert etc. will equally split the profits if this is job done well.

Engineers are hired to deliver and produce value. Tooling can be a part of it but if you can outsource something which is not your source of income, you have to do it. Engineering time is more valuable.

I also know many startups and small companies investing 5 people and 6 months to get an observability platform up and running while they could just get datadog or new relic for half the price... and I don't get into account outages and updates to the platform.

I remember a recent uber blog post on how they moved from build tool A to build tool B and a couple of weeks later, 3000 people where laid off. It's important to spend development time on revenue streams.

This is some nice piece of advice https://nav.al/build-a-team-that-ships

"Outsource everything that isn’t core. Resist the urge to pick up that last dollar. Founders do Customer Service."

I am curious about the actual cost in $! Managing your own kafka or observability infra is expensive, you need a team to do this.

A 67% reduction doesn't say the whole truth. They have more services to manage now, which means they need more people and more time to do this.

Saving 10k from your AWS bill by hiring 2 more engineers is not cost effective.

The article says that monorepos are more efficient but also that "As the monorepo grew, the build target list increased to a point where it became too long to pass it through Bazel’s command line interface.".

Monorepos are not efficient. They are easier to manage when a team is small but as the team grows and you have more and more deliverables with separate versioning you are introducing control structures in your automation. Complexity explodes!

Anyway, all this does matter if you don't make any profit :)

In a cloud native world, code should not be aware of the environment. I don't see a reason to have multiple files per env and not just different configuration. This kinda of creates a mental model against true configurability.

The solution with multiple files actually goes against the 12fapp

"Sometimes apps batch config into named groups (often called “environments”) named after specific deploys, such as the development, test, and production environments in Rails. This method does not scale cleanly"

I don't get it! He complained that it was malfunctioning but he continued using it?

You are all too geeks to get that people who are still on windows 7, they don't access hacker news, they have no clue what vivaldi is and probably will never update to anything else, they will just throw the machine away and get a new one.

I think that programming is a bit more complex. You see I get the difference between the "coder" and the person who cares about adding value and creating something that others will use. The industry needs both "good coders" and "creating thinkers" to move forward and its hard, ofc, to find someone who is able to use all of those parts of the brain. Probably there is a 3rd category of people who are here just for the $ :)

Sorry people but Switzerland is boring and hard to integrate! It's nice for specific types of people who enjoy elitism and time-boxing. I will be always surprised by how fast people vanish once the stores are closed...early in the afternoon.

I stopped reading at "Python, the language used in Django, is a language very commonly used for academic purposes, whereas the Ruby community — thanks to Rails — is more business-oriented."...

Yea you cannot do molecular meta-dynastic micro transdusevelociraptatable programming

Who is Joanna Rutkowska and what is Qubes OS :S

This is 2018, who is using pockets? Everything is on the cloud!

No its not, code review is the team's job, including the manager.

I see a title "The Machine That Builds Itself"....but there is no code! Show me the code or throw the paper away...

Thats not just google mate, every large company is like this. We join thinking that our engineering will make a difference but it does not work like this. If you want to climb the ladder either join high, or grow through a smaller company.

I admire how mozilla is so passionate about what they develop but still, in 2017, firefox needs restart every couple of hours for performance reasons. I kinda of feel like they have the proof of concept working but its never good enough for the wider audience.

You can never trust data that exist on someone else's machine. Period. Everything else is a misconception. Just try to control what you share.