Why problem statements aren't enough(letters.unchartedpathbreakthroughs.com)
letters.unchartedpathbreakthroughs.com
Why problem statements aren't enough
https://letters.unchartedpathbreakthroughs.com/posts/why-problem-statements-arent-enough
13 comments
Problem Statement
Think hard (time, money, resources)
Write down solution
Profit!
Think hard (time, money, resources)
Write down solution
Profit!
[flagged]
It is not technical advice. It seems some general career advice for tech people (don't just think in technical context).
But mainly it is a ad to hire her as your coach.
But mainly it is a ad to hire her as your coach.
Right, but their top level credential is as a staff software engineer. Glaring webpage styling issues don't bode well for such a credential.
Software engineer and (web) design are not the same thing.
If you're a staff software engineer of any type and you can't figure out the absolute basics of CSS in 2026 then I don't want your advice, period. I think you think I am not sure what I'm saying, but I'm quite assured in this stance.
You're misapplying your evaluation here. The most you might say is "don't take front-end Dec advice from them".
Instead of discarding the whole thing, just take what's good and leave the rest.
Instead of discarding the whole thing, just take what's good and leave the rest.
The problem is they bill themselves as a staff software engineer. Such a glaring visual issue makes me question their core competency, which makes me question any advice they could offer. Of course they might still be amazing at professional coaching, but maybe don't bill yourself as a former engineer if the first visual impression is very clunky engineering.
The scientists do,
Step 1: Build Model
Step 2: Think of implications
Step 3: Check if observations make sense based on implications
Step 4: If wrong, refine model or go back to Step 1. If right, submit to other people and ask them to verify.
The consultants do,
Step 1: Build model.
Step 2: Tell people this is the right model.