Thing is most businesses take time to build. If you're in "dire need", like really about to starve, you probably would take a job you might even be overqualified for.
Even with that being the case finding a new job is a hassle and means you have an interruption in pay and insurance. Gives me a lot of incentive to just work at BigCo and not worry about it until -I- want to worry about it.
Yes. That's essentially what I was getting at. Asking someone to code accurately on a whiteboard is nonsense.
When I interviewed at Google, they asked me if my whiteboard code would compile. I said, "give me a laptop and I'll tell you". I don't think they liked that answer. ;)
When I ask candidates if their whiteboard code compiles, it's a gentle hint that there are major structural issues, or an opportunity for them to point out the parts that are psuedocode-y. In general I don't include whether the code compiles (mostly JS, so "runs") in feedback unless it is amazingly perfect or really far off. This seems standard.
This. When interviewers feel that the question was not hard enough or that they didn't like the answer, they often fall back on "you're missing a semicolon".
Once I get that "I'm getting kinda stuck in a rut here" feeling I usually take a lap around the building. (~5 min). That's usually enough.
I also go to the gym throughout the week but I usually am focusing on the workout too much to think about coding.
Sometimes I just have to more or less sleep on it though. I work on some other part of the project and come in the next day with fresh perspective. It's probably always kinda rolling around in the back of my head to some degree.
I'm just imagining the case where someone has gotten very used to using the smart lock in a way where they lock it remotely. I guess that could be blamed on the user, but it's definitely not going to encourage them to buy any more Nest products.
+1 to Khan Academy. Explanations are super clear. Their website allows you to work through practice problems too, which I think is the most important thing.
I don't really feel the need to complain about languages. I just find the workaround and implement it and move on. All languages have trade offs. I can tell you that this one lends more to scaling projects or this one is easier to maintain, this one is easier to iterate, etc. But getting upset doesn't do anything. You just pick the best you can and work with it. I'm not going to get mad that my hammer isn't also a drill.
Every technology is designed through tradeoffs. Choosing a technology and the using it properly reqires understanding those tradeoffs. What they are, why they were made. I whine about the appetite for secret allocation that my C# program has. I whine about the mess that is writing the equivalent C++ or Go code, and the learning curve of doing it in Rust.
It’s whining on the surface but it’s really 90% tradeoffs and 10% badness.
Being able to critique design mistakes in eg. an API means you have a pretty deep knowledge on the domain (and/or API design in general). Being able to argue the downsides of a certain technological tradeoff (such as GC vs not, dynamic vs static) is also important. No one will be able to win an argument on tabs/spaces or dynamic vs static but everyone should be able to point out some drawbacks and benefits.
Describing the merits of a technology is just as good as describing the drawbacks. I chose drawbacks/whine because (unfortunately) I am myself much more enthusiastic when describing flaws than positive sides - itself a flaw, but a very common one.
I see where you're coming from. I think I just don't like the "complain about it" angle.
I can't change the language itself. I feel like a lot of people stress about those issues and can talk about them at length. I'm usually like "This isn't optimal, here's the workaround, this other language does it better but it's got other issues that are even worse for what we're building. Problem solved, moving on." Like, it's just another problem to solve at my problem solving job. The answer is not elegant, but that's the case with so many things in the real world...but this is probably the stoic in me.
I agree, I think it's better to ask what some of those trade offs are. What's this tech good or bad at? I'm not gonna complain about a language feature that I can't do anything about. I'm gonna implement the work around and move on. What's the point in sitting around and complaining? I can't alter the language itself and it would be unreasonable to change the project language past a certain point.
Reading into how Javascript was created clarified that the "issues" with the language were. I understand the creators(who are probably far smarter than I) chose to make things that way for a reason. I can often just google these reasons "Why does X language do this?" and understand. Any time I think "This seems silly..." there's a reason for it.
Unsubscribe from r/politics and subscribe to r/writingprompts instead. You get free short stories, a good way to read a little something before bed. Just implement a limit of some sort on yourself. "I'll only read 2 stories per night" or something like that. I keep my reddit super positive: DIY, programming, fitness, wholesomememes, finance. That's the beauty of it, you can control that content.
I try to keep HN as my only news source. I still know about the big stuff but I don't get super weighed down. I donate to a charity I know is doing good and focus on what I can do to improve things. I can't fix all the madness in the world but if I focus on a narrow strip of life that I can reach I can have more positive impact than I would sitting around stressed and sad.
