Do engineering managers need to be technical?
Not sure where I stand on this but interesting read
I don't want to know a bit about everything and a lot about nothing.
This isn’t about minimalism, mind you; it’s about clarity. Expressing yourself so clearly that someone doesn’t have to perform any gymnastics to follow along with what you’re saying. The problem here is that a lot of writers think that the gymnastics is what makes for good writing
An extensive piece on the current best monitor setup for programming
Great in depth article about naming in design systems
How methodologies made software development loose it's focus
Some gold content for UI developers. What they talk about is really the latest learnings about how to build quality UIs
Rather than beeing focused on beeing 100% correct with the delivery date we can paint the reality with statistical forecasts
The power of yet (growth mindset)
A reflection on where we stand with technology as a society.
A great essay about intellectual humility
It’s not about the giving answer. It’s about discovering questions
Great essay about a different aspect of parenthood
Old yet great read. The plan is only a tool. What matters is the outcome of the project.
Great look at svelte an it's motivation.
Opinion a bit too one sided but this probably make our development tools better
From the Author of emotion (css-in-js library).
Very wise words there.
I have huge respect for people like him that can put opinions in context and don't tell only a one sided story
Narrow down the problems you would like to solve and then ask yourself if CSS-in-JS is going to help you with those or avoid them altogether. Let’s pretend it will. Ok, now you’ve got a new set of problems you are going to learn how to solve and they are much more interesting than the problems that classical css presents, but you still have to learn how to deal with them. That takes time and energy that is precious in development cycles.
My larger point is to think about why we chose to use a library, framework, or pattern. Sometimes we create a problem for ourselves just so we can try something new. That is perfectly fine and its how we learn but just know that the context of that decision is everything. From my experience, the better route is to learn about this new thing and gain some understanding of the context of its use but do not force it but rather wait for a situation to arise when it is needed. Just be patient.
Nice concise article about a few biases relevant in a work environment.
Pleading guilty on many
OKRs misconceptions and best practises
"Bring your own design" components
Some great parallels in this talk
Multi-part article about best practices for styleguides.
Very detailed & lots of examples
Nice little hidden feature to turn off notifications
Even if it’s complicated, this looks like a great way to have container queries in css before it actually becomes a standard.
More and more of those great posts giving a better understanding at the huge potential of decentralized networks. The bubble of cryptocurrencies/ICOs will probably burst at some point, but the technology behind is here for a revolution.
Great short talk about the value of passion + persistence. Via @simonraess
He's just one of the best at making analogies that explain complex concepts.
Great short explanations of a few biases in the context of programming
Jeremy sharing his thoughts about CSS utility classes movement
Great post to go further in the CSS utility classes vs components classes debate. Spoiler: it's not black and white
Great reminder of small steps to care more about yourself
TIL Poop transplant is a thing
Probably would change some of the points but this phone contract is a good food for thought. Not just for kids but for anyone.
This, a thousand time this,
"However, having a style guide is never the end goal. Pattern libraries are created to make it easier for designers and developers working in a company to iterate on a product or to maintain a website in a consistent way. The end goal is to have an up-to-date style guide that is consistently used by both designers and developers in an organization, thereby getting results faster."