Things are moving fast. Microsoft is introducing AI generated meeting notes, recommended tasks, and personalised highlights and chapters in Teams powered by ChatGPT.
https://t.co/ThmvqhnhNW
“Developer Productivity 2.0
What practices do productive teams follow? (did a survey, 75 responses)
- pair programming
- ownership & autonomy
- focus
- clarity, clear vision
- having a plan
- great people: hiring well, growing them”
@GergelyOrosz#LeadDevBerlin
🎉 It’s happeninggg!!!
Engineering Management for the Rest of Us is now on sale!
I’m so excited to finally release this after so much went into it. 50% of all of my profits will go to She Code Africa! @SheCodeAfrica
https://t.co/bljqSvUtun
// Stable Diffusion, Explained //
You've seen the Stable Diffusion AI art all over Twitter.
But how does Stable Diffusion _work_?
A thread explaining diffusion models, latent space representations, and context injection:
1/15
"One way to see indirectly what is important in an organization is to see what is measured, because that often communicates what is valued and influences the way people behave and react." - The SPACE of Developer Productivity - ACM Queue https://t.co/ldNboLmowF via @ACMQueue
The other day someone who disagreed with me told me "well you're welcome to do your own research" so I responded with a pubmed link to my 60 peer reviewed articles on the topic and labeled it "my own research." Fair response? :)
1) Trust the teams
2) Reduce WIP (work in progress)
3) Quality is not optional—defects are waste.
Basic rules. Most orgs could vastly improve doing nothing but that.
It isn't true that facts never change minds. They just don't change minds that are already made up.
If you see your ideas as identities to defend, you twist and resist data to rationalize your views.
If you treat ideas as hunches to test, you embrace data to update your views.
You'd think this is a problem only startup companies grapple with, but I've been in big companies where millions of dollars were burned chasing ground up rewrites when probably the better thing to do would be to just, you know, focus on what customers actually wanted.
Scientific literacy is important, not just for the people in science community, but for everyone. It makes you look and understand the world from a different perspective. 🧠
Some of the best Science Books that everyone must read. A Thread 👇
People. People. People.
Be there for each other. Push each other and reach for the stars, but also be there for the times you can't. At the end of the day all we have is each other.
A small team of great engineers can make just a shocking amount of progress.
This is one of the most unintuitive things for business people who tend to think more linearly in terms of team size vs. output.
Tell me which is the "best" backend technology to build at scale. Go? Java? .NET? Node? Rust? RoR?
You can make it all work, even exotic ones like Erlang (e.g. Whatsapp).
The same is true for mobile frameworks. Choose based on your constraints and needs. Avoid blindly copying.
Oh, you want relevant interview questions, eh? Scenario: your team is building a new product with functionality that overlaps a product owned by another internal team. Yours is better, but politically theirs can’t be killed. Let’s roleplay an interaction with that team’s manager.