webel0
Joined 7 years ago
Joined 7 years ago
I found that neither side of the market wanted to rethink the market, they just wanted something that worked well for them. Even today, job seekers may be reaching for something like this but employers have no interest; there is a glut in the market.
I’m sure I never quite got the messaging correct. However, I distinctly recall that triplebyte attempted a pivot in this same vein and also failed bad.
It doesn't _really_ solve python dependency/import issues. Instead, it helps to you keep your project in discrete chunks and well-organized. It also makes it easy to package up the separate projects as artifacts.
I've run into some issues with versioning separate projects but I suspect that is a matter of bandwidth rather than an actual, insoluble issue.
I'd use it again at a startup or on project where you need to ship a bunch of artifacts but don't have a lot of bandwidth.
I'm talking about whether a human can read the document comfortably.
When I was in grad school I was very hesitant to ask others for help or feedback. Big mistake! I see similar things with interns: they'll wait until a daily or weekly check-in to raise problems.
My approach now is to set a time budget; if I don't figure it out myself within X hours, then I have to ask someone for help.