Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
flavianh
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
Productivity in software development: the lean response to McKinsey
(blog.buildtosell.org)
1 points
by
flavianh
3y ago
|
0 comments
2.
▲
Beyond features: crafting apps users love
(buildtosell.org)
1 points
by
flavianh
3y ago
|
0 comments
3.
▲
Three common mistakes we make with software bugs
(buildtosell.org)
2 points
by
flavianh
3y ago
|
0 comments
4.
▲
LLPhant – A Comprehensive PHP Generative AI Framework Using GPT4
(github.com)
1 points
by
flavianh
3y ago
|
0 comments
5.
▲
Three anti-patterns in bug management
(buildtosell.org)
2 points
by
flavianh
3y ago
|
0 comments
6.
▲
by
flavianh
3y ago
Well, productivity measures how fast you deliver new value. Fixing a bug is about repairing value that you thought you had delivered but actually did not. Counting bugs as "value" would be double counting.
7.
▲
by
flavianh
3y ago
Interesting to note that two of your decision points are on "shipping product improvements at a regular cadence" or "shipping so slow that it's negatively impacting customers". Both relate to a productivity discussi
8.
▲
by
flavianh
3y ago
That’s very interesting, what is the score based on?
9.
▲
by
flavianh
3y ago
I agree 100%, you need to have a strong product foundation to turn good output into good business outcome. A productive team that delivers features no one wants is pointless. Both go hand in hand, but as far as engineering management goes,
10.
▲
Ask HN: How do you measure eng team productivity?
8 points
by
flavianh
3y ago
|
17 comments
11.
▲
Why agile is not enough to build great products
(buildtosell.org)
1 points
by
flavianh
3y ago
|
0 comments
12.
▲
Achieving zero customer-reported bugs in 3 months
(buildtosell.org)
1 points
by
flavianh
3y ago
|
1 comments
13.
▲
Cadl: A language to describe APIs and generate schemas
(github.com)
3 points
by
flavianh
4y ago
|
0 comments
14.
▲
by
flavianh
4y ago
Your comment got me curious, so I've just asked one of the best developers at Google. If you want to tag along and make some noise: https://twitter.com/FlavianHautbois/status/15972300521436733... (he has not
15.
▲
by
flavianh
4y ago
I'm actually curious about this, so I've just asked one of the best developers at Google. If you want to tag along and make some noise: https://twitter.com/FlavianHautbois/status/15972300521436733... (he
16.
▲
by
flavianh
4y ago
Don't get me wrong, pairing has merits. Let me give you an example. I'm in the middle of going through type challenges in Typescript ( https://github.com/type-challenges/type-challenges ). If I knew absolutely
17.
▲
by
flavianh
4y ago
1. Yes, that's the point. 10x doesn't say "compared to what", but hints at "compared to now" 2. For sure. My 3 former companies let people spike while working, and I've seen mediocre engineers (lots of bug
18.
▲
by
flavianh
4y ago
Being independent or in a co-op, what would be your training system?
19.
▲
by
flavianh
4y ago
It looks like your company is ticking a lot of boxes, they're a keeper for sure. Would you share their name?
20.
▲
by
flavianh
4y ago
This. I genuinely think this is one of the best comments in this thread!
21.
▲
by
flavianh
4y ago
You're right in a way, but you're missing the "10x compared to what?". Consider the 1x baseline as being the median productivity of your development team (which is definitely hard to approximate, but for the sake of the
22.
▲
by
flavianh
4y ago
I assume some of the skills you're trained on are technical too. Your organization sounds like it does a lot to develop engineers, do you think it's paying off regarding competition or other tech companies?
23.
▲
by
flavianh
4y ago
I found it to be very challenging to deep-dive into harder subjects when doing pairing
24.
▲
by
flavianh
4y ago
Most don’t, I’m wondering if they should.
25.
▲
Ask HN: How is your company training you to become a better developer/engineer?
97 points
by
flavianh
4y ago
|
149 comments
26.
▲
Life Satisfaction and Age
(flowingdata.com)
1 points
by
flavianh
4y ago
|
0 comments
27.
▲
Three months to change a product concept and increase retention
(buildtosell.org)
1 points
by
flavianh
4y ago
|
0 comments
28.
▲
Understanding react hooks through a timeline
(julesblom.com)
1 points
by
flavianh
4y ago
|
0 comments
29.
▲
User errors: are we dealing with idiots?
(buildtosell.org)
1 points
by
flavianh
4y ago
|
0 comments
30.
▲
User errors – they are not just idiots
(buildtosell.org)
2 points
by
flavianh
4y ago
|
0 comments
More ›