News for hackers. Stuff that matters.
Re:Why Problem Statements Aren't Enough by ericyd on Tuesday June 30, 2026 @08:35AM (#48731836)
[flagged]
Re:Why Problem Statements Aren't Enough by lukan on Tuesday June 30, 2026 @09:03AM (#48732171)
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.

Re:Why Problem Statements Aren't Enough by ericyd on Tuesday June 30, 2026 @02:01PM (#48736637)
Right, but their top level credential is as a staff software engineer. Glaring webpage styling issues don't bode well for such a credential.
Re:Why Problem Statements Aren't Enough by lukan on Tuesday June 30, 2026 @02:55PM (#48737564)
Software engineer and (web) design are not the same thing.
Re:Why Problem Statements Aren't Enough by ericyd on Tuesday June 30, 2026 @10:27PM (#48741662)
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.
Re:Why Problem Statements Aren't Enough by MDCore on Tuesday June 30, 2026 @12:20PM (#48734945)
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.

Re:Why Problem Statements Aren't Enough by ericyd on Tuesday June 30, 2026 @02:00PM (#48736610)
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.