News for hackers. Stuff that matters.

A comment on Deep work. Essentialism in asynchronous culture. Parent comment

Re:Deep work. Essentialism in asynchronous culture by woolion on Wednesday December 21, 2022 @02:50AM (#34077830)
He means alone for "code supervision". That means you communicate with clients and/or analysts for your specs, but don't get code review or anything else from a senior engineer. No advice on how to architect, when to refactor, etc.
[ Parent | on HN ]
Re:Deep work. Essentialism in asynchronous culture by mym1990 on Wednesday December 21, 2022 @03:42PM (#34086130)
But if you're working on something so complex that it needs 6 months of heads down time...and you're not getting any technical feedback or advice...is that not a huge red flag?
[ Parent | on HN ]
Re:Deep work. Essentialism in asynchronous culture by yencabulator on Wednesday December 21, 2022 @07:13PM (#34088109)
Grandparent said

> Your level as an engineer should be based on how much deep work you can do without screwing the pooch.

A really good engineer can do 6 months of head-down work without a disaster. A really good engineer does not need technical feedback or advice in that time, as long as the problem is clear enough in the beginning.

Here, try this as a though exercise: "Create a new distributed nosql database that uses WASM modules for non-interactive transactions." A really good engineer really, really, doesn't need "technical feedback" during the process to implement that.

[ Parent | on HN ]