PostHog's open source platform has everything engineering teams need in one place. Product Analytics, Session Recording, Funnels, Feature Flags, Experimentation and more — all seamlessly integrated. And you can self-host, so user data never leaves your infrastructure.
this week's favorite
In software development, the silent majority are the engineers who write the code, debug the programs, and solve the complex issues behind the scenes. They do not participate in controversial discussions about Visual Basic or Pascal — they just do their work in those languages without even knowing that there’s so much controversy surrounding their language of choice.
This blog series will examine Git’s internals to help make your engineering system more efficient. Part I discusses how Git stores its data in packfiles using custom compression techniques.
Scrum (and Agile as a whole) promised to liberate the developers. It was supposed to be a new way of working that would break with the traditional approaches to delivery. It was an acknowledgement that software development isn’t the same as building a house or a car. Which calls for a different approach altogether.
With more than 25 photos and 90 likes every second, we store a lot of data here at Instagram. To make sure all of our important data fits into memory and is available quickly for our users, we’ve begun to shard our data — in other words, place the data in many smaller buckets, each holding a part of the data.
There’s nothing wrong with a fondness for data. The trouble begins when you begin to favor bad arguments that involve data over good arguments that don’t, or insist that metrics be introduced in realms where data can’t realistically be the foundation of a good argument.
Accelerate your professional development with Wilco’s flight simulator for software engineers and engineering teams. Complete “quests” using a tech stack of your choice, explore new technologies, brush up on skills, and never stop developing. Skip the waitlist and signup.