I have literally fixed a coffee grinder at one of the startups I worked at.
I think I would fail this test since most coffee machines are hard to repair unless it is something trivial and the idea of just repairing something is kind of odd. A better answer might be you work with the office manager, go to the store and grab a temporary one.
I also think this is a terrible idea for other reasons:
1. You are working at a small company and its easy to communicate, its broken and you are going to fix it. However, focus is critical even if it doesn't feel like it all the time.
2. It is hard to tell but it seems like saying you would talk to the office manager would cause you to fail but this seems like the most rational answer. You should work with them and see if you can fix it together or at least keep them in the loop.
Bias for action is great but you also need people who can focus, know what they are good at, and communicate with others.
Had a similar experience. Was on this for a bit when I had a GP who seemed hesitant to prescribe stimulants even though I had historically taken ritalin and it was fine (all side effects were manageable).
I think also knowing which streets to avoid entirely are good too. Each street has its own vibe and always has. 3rd and pike was bad way back in 2000's in ways that are similar to now. The ambient level of visibly homeless, and more importantly those in actively crisis has gone way up IMO--and you can't really avoid that.
Be interesting and depresisng to make map for people to use like that but I am not sure how it wouldn't devolve into fearmongering like nextdoor does.
I feel bad for the occasional wide eyed family from the burbs I see walking streets even I wouldn't dare tread on from my car or lyft.
The problem is that 3rd is where all the downtown bus stops are. If you commute by transit, it's almost impossible to ignore. Your only option is to rush to the next block and hope nothing goes wrong.
ya there is always some scary characters around McStabbys/StabDonalds at 3rd and Pine. I have trouble following the logic when a company decides to plop a corporate office down in the middle of the Seattle sketch corridor. Witnessed a straight up drug deal go down as people with corporate lanyards walked past.
Hey, I used to work there in the 90s, it’s always been like that. We had off duty cops staffing the place along with a frequently used banned list. And this was when it was two stories, I think it must be easier these days given that they smartly got rid of the second floor dining area.
Worked at an office on 2nd and Pine for a few years - every summer, if you opened the windows, you’d get a steady wafting of crack pipe smoke coming in the building. You could tell if any cops were nearby because people outside would be singing or whistling as a warning call. Good times.
It is always worth taking a look at what you need to accomplish and the data you have and the tools for manipulating it then build (or not build) a system.
If you just hit everything with the REST, OOP or db hammer you end up with things that more complicated than they need to be.
> It has high latency: because build is costly, it is invoked at most once per x seconds, which means you either have to wait to get the results, or get stale results.
I find this is the worst part right now. Latency is everything if it is tied to actual typing in of code.
Excited to see this get fixed, or at least improved!
I have been using specs ECS in rust for about a year and a half now and I think rust + ECSs work really nicely together.
However, I started with a simple stupid solution you describe. Despite that, I quickly realized I was going to end up coding an ad-hoc version of an ECS if I keep trying to do my own thing.
For reference, I am making a sim game like dwarf fortress so it has been kind of nice, though I think in the fullness of time I will probably end up writing my own ECS to replace specs or start contributing stuff to it.
I have used unity and UE4's "ECS" and I could see how they get a bad wrap. They aren't very good ECS systems and because the engine uses this model it forces people to use it.
One of the big advantages of writing a game from "scratch" is you are not burdened by weird architectures that don't make sense so experimenting first before makes sense. I don't know if I agree that ECS never have a place in game programming.
I think I would fail this test since most coffee machines are hard to repair unless it is something trivial and the idea of just repairing something is kind of odd. A better answer might be you work with the office manager, go to the store and grab a temporary one.
I also think this is a terrible idea for other reasons:
1. You are working at a small company and its easy to communicate, its broken and you are going to fix it. However, focus is critical even if it doesn't feel like it all the time.
2. It is hard to tell but it seems like saying you would talk to the office manager would cause you to fail but this seems like the most rational answer. You should work with them and see if you can fix it together or at least keep them in the loop.
Bias for action is great but you also need people who can focus, know what they are good at, and communicate with others.
edit: formatting (need to not post while raging)