373 karma · joined July 15, 2019
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.
I can't speak to their RVA operations.
If they are doing 50k rides a day, then they would appear to have a remarkable safety record.
It will be interesting to see if these investigations lead to a repeat of the Cruise debacle or if this will become the price of doing business.
[0] https://www.reuters.com/business/autos-transportation/us-saf...
[1] https://static.nhtsa.gov/odi/inv/2024/INOA-PE24015-12348.pdf
[1] https://pandaily.com/hesai-technology-addresses-lidar-produc...
I think that this will start to take off if stakeholders can start to coalesce around a single day. Either Monday or Friday. Once you build up the expectation that people are off on a given day, it becomes that much easier for a new firm to adopt (because, e.g., none of their counterparties are in the office).
After seeing how my doctor iteratively ordered up different sets of tests for me over the course of a few months, I got to thinking about improving decision trees for blood testing (and maybe others).
However, when I spoke to a (first year) med student about this he suggested that doctors actually don’t want something like this. I don't think I followed the thought process completely but it was something along the lines of, “we’ll always find something.”
Would be interested if someone could elaborate on this line of thinking.
I had no idea this existed until just now but I’ve worked at two companies where a lot of coworkers could have benefited greatly from a map app that has a few more features than geojson.io but is less complex than qgis/arcgis.
Thats pretty much what they did. I do sort of like the idea of sharing less-than-perfectly-polished writing. But it does make for an odd read.