2,656 karma · joined August 16, 2011
Further, because your human oriented process has now codified your system, changes to the system that's would be beneficial to a software system (i.e. dividing the system into components) are impossible. So incremental scale is achieved by stuffing more into the process, which then gets grafted onto the script monolith in a self protruding cycle.
Honestly I feel this situation is an invitation/opportunity to show your depth. I had a similar experience where I was asked to implement a box filter, which I did naively, and then asked to do it the clever way.
I remembered about Haar classifiers https://docs.opencv.org/3.4/db/d28/tutorial_cascade_classifi... which solve the same problem, and I was familiar with the OpenCV implementation. I mentioned this and started to write code, but at that point the interviewer was much more interested about why I knew about some obscure old-school opencv method than finishing the coding exercise.
I liken it to spaced repetition. The first time I don't know where to find something I grep, after a few times I start to remember. I have a vim layout with 12 windows, so I have many views into the code and always have space to pull up more without losing context. I genuinely feel claustophobic with less.
> What do you do if you need to look up the definition/implementation
Sometimes I feel "jump to definition" trades immediacy in favor over natural exploration of the surrounding code. I work on a 10 year old mono-repo with 1000s of contributors. After two years I have a good feel for the basic layout, and would say I have a good mental map of the stuff that most affects me. During code review I'm often pointing people to existing implementations that they've just duplicated.
Basically there are log2(12) + 1 bits or log2(24) of information (which ball and heavier or lighter). Any solution must reveal all information.
For example, a first weighing with an initial (4,4,4) split has three possible outcomes with equal probability (left, even, right), so reveals log2(3) bits. 3 independent weighings with equal outcomes would reveal 3*log2(3) bits, or log2(27). Of course the weighings cannot be independent since 27 > 24.
The trick is to design a scheme which reveals all 24 bits. With the static solutions this is trickier since all bits need to be revealed in all 27 possible outcomes, but if you work through them it should reveal why the solution works.
I think before passing judgement though, I would like to know how a human would have performed. Aviation investigations often recreate scenarios in a simulator and then have other pilots fly them. I'd imagine something similar could be done for cars.
FSD is pretty good at motorcycle detection and has the advantage of cameras looking in all directions.
It truly is 60s level wizardry.
It's used by some of the pytorch back ends.
https://github.com/herumi/xbyak
Example use: https://github.com/oneapi-src/oneDNN/blob/main/src/cpu/aarch...
I learned about these through a blog post about speeding up pytorch on ARM: https://pytorch.org/blog/optimized-pytorch-w-graviton/
I think it is the only time though that I've been faced with a stationary car suddenly appearing where I wouldn't expect one, and that's very different to the car in front needing to slam on the brakes with whom you can share some stopping distance.
fwiw 6 seconds at 45mph is 120 meters. That we can comfortably go that far in 6 seconds is a modern marvel, but it's also 20 car lengths.
But the light changed before they made the turn and they became stuck in the middle of the intersection once they lost the protected left ...
So now they're sitting in the "going straight" lane where you wouldn't expect a stopped car. The car in front of me changes lanes without really slowing down, and the FSD prediction model didn't pick up that the stopped car was stopped. I can't really blame it, it took me half a second to figure it out as well and by that time I was hard on the brakes.
Ancient populations certainly left their mask, Romans deforested Europe for the sake of glass making. But that is nothing compared to the resource extraction and ndustrial waste that support the world 9 billion people.
Willing it away with "the sky has always been falling" is denialism at best.
FWIW, I grew up in Australia, live in the Bay Area, and lived 4 years in Denmark. I have friends on both sides in that income bracket.
For what is worth, looks like a big Mac meal is 99kr, ~$15
Basically labor becomes vested in being part of high value activities. You will order your big mac from a touch screen and pick it up from the window when called. The burger meal will still cost $20, but not $50.
You also need the generous unemployment policy with (actual) retraining options. There's a common refrain "who has time to learn how to code?". The person who's union will provide 70% of their salary while pursuing a free education does. But that's done by agreement with the union, if the person would be better off training as a plumber, that will probably happen instead. Basically you need to remove the incentive for clinging onto unproductive jobs for the sake of jobs.
It's not a utopia though, don't get me started about the Danish job center which is basically state funded harassment.
It gets interesting when these systems need to be productionized and scaled. A strong software engineer who can speak the math is invaluable. My first year on the job was basically removing N^2 loops and making 3D visualizations.
So why are investors clamoring over houses that have a negative rate of return? The speculation that the value will increase. We should do everything in our power to make real estate a non-appreciating asset. If that means government owned entities constructing social housing as needed, sign me up.
I believe there are leaked emails floating around which pretty much irrefutablly confirm this.
You have to take away cars (parking) first so that they start demanding public transportation.
In seriousness though, I do not believe we should shelter existing residents (read homeowners) from the economics they impose on newcomers. Removing tax breaks (Prop 13) would go a long way.
Therefore "rich" can't be the problem to solve for, it's fairness and equality. Culturally "a fair go" used to be the equivalent of the American Dream, and I think it's fair to say both are dead to most of the unlanded classes.
I've also spent a lot of time in Japan, and in many ways culturally they at 10-20 years ahead. For many life became unfordable there for different reasons, and I buy into that this contributed to the plummeting birthrates.
Societies come under evolutionary pressure, just as life does. It's entirely possible that unsustainable societies will simply die a quiet death while others take over.