HackerTrans
TopNewTrendsCommentsPastAskShowJobs

neowise

no profile record

Submissions

[untitled]

1 points·by neowise·8 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·8 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·8 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·9 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·9 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·9 bulan yang lalu·0 comments

[untitled]

1 points·by neowise·9 bulan yang lalu·0 comments

Building Developer-First APIs

blog.pragmaticdx.com
1 points·by neowise·9 bulan yang lalu·1 comments

Why Developer Experience Is More Than Just Better Tooling

blog.pragmaticdx.com
33 points·by neowise·9 bulan yang lalu·5 comments

The Cost of Bad Onboarding

blog.pragmaticdx.com
3 points·by neowise·9 bulan yang lalu·1 comments

The Problem of Interruptions

blog.pragmaticdx.com
4 points·by neowise·9 bulan yang lalu·1 comments

comments

neowise
·8 bulan yang lalu·discuss
The three-layer system, exact scripts, and implementation playbook for protecting your focus when everyone's convinced their request is the exception.
neowise
·8 bulan yang lalu·discuss
Success isn’t about pushing developers harder, it’s about shaping the system around them. When doing the right thing feels effortless, excellence becomes inevitable.
neowise
·9 bulan yang lalu·discuss
Three Forces That Quietly Shape How Developers Work
neowise
·9 bulan yang lalu·discuss
Engineering teams waste time tracking vanity metrics instead of the factors research shows actually predict productivity and retention.
neowise
·9 bulan yang lalu·discuss
Code reviews aren't slow because developers are lazy. They're slow because they expose every dysfunction in how your team actually works.
neowise
·9 bulan yang lalu·discuss
Technical debt isn't a coding problem, it's a culture problem. An exploration of why "fix it later" becomes "never", and what teams who escape this trap do differently.
neowise
·9 bulan yang lalu·discuss
Behind every great API is a team that remembered what it feels like to be the developer on the other side of the screen.