Johannes Ptaszyk retweeted
User stories are supposed to be unclear. They're anything from a word to a sentence long with no implementation details. (They describe the user's work, not yours.) They are a reminder to have a conversation just before and during implementation. Fill in the details during Sprint Planning or equivalent—just enough detail to start, not finish. Collect additional details with more conversations as you work. Collecting lots of detail up front is just a waterfall requirements-gathering phase. No agility there.
Johannes Ptaszyk retweeted
Well, shit.
Encrypted traffic interception on Hetzner and Linode targeting jabber.ru, the largest Russian XMPP (Jabber) messaging service.
The instant messaging have been wiretapped for 3 months, on both hosting providers in Germany.
notes.valdikss.org.ru/jabber…
Johannes Ptaszyk retweeted
Building Coil 3.0 and the plans for Compose Multiplatform support: code.cash.app/multiplatform-…
Totally in love with this!
Introducing "Tomato Architecture" influenced by "Common Sense Manifesto"
github.com/sivaprasadreddy/t…
Johannes Ptaszyk retweeted
I've had this in the works for quite a while now, very excited to publish it. Bottom up, animated guide to HTTP load balancing algorithms.
samwho.dev/load-balancing/
This is probably one of the most ambitious pieces of writing I've ever done. I would love feedback. 🙏
Whoever needs to hear this today:
It is totally fine to close branches after merging. You do not have to hold on to that weight from your past.
3
647
With being able to manually adjusting weights on AI input, are we going back to manually programming on top of AI? 😂
35
"I doubt that" will be my go-to argument from now on for Twitter. 😂
47
Johannes Ptaszyk retweeted
Let me explain the story behind this poll. It recently came up as the Kotlin design question, and it is a great illustration of the tradeoffs in the language design and complexities that come up as different language features interact. /1
This is not a trick question, just probing your programmer's intuition. Assume that you have a property that coerces its value in the setter:
var percent: Int = 0
set(value) { field = value.coerceIn(0, 100) }
Don't run it! What should this line print?
println(--percent)
47%0
21%-1
32%Just show the answers
1,491 votes • Final results Johannes Ptaszyk retweeted
- Architecture
- Testing
- Deployment pipelines
They are often used as separate roles in a team.
But they should be mandatory skills for most developers.
Johannes Ptaszyk retweeted
Apparently we all now refer to humans as “resources” by default. I, for one, will not give in to this dehumanization even if I end up the last human standing in a sea of resources.
Anyone with me?
#WeAreHumansNotResources
Johannes Ptaszyk retweeted
I've been teaching TDD for a number of years, and it is very challenging for less experienced (and even for very experienced) devs to grasp it. Unexperienced noobs get into it no problem. It is the need to unlearn so many bad habits that is preventing many devs from grasping TDD.
Did anyone try to do TDD with @GitHubCopilot ?
It's nice that it spits out code, but how would one go about the usual TDD cycle?
I imagine it being hard to do.
Would love to get some insights :)
60















