I should specify that I've been mainly listening to WNYC. I wouldn't exactly call their run-of-the-mill pieces "fluff", but they're becoming more of an attempt at radio clickbait. "Stay tuned to hear the tale of a disadvantaged minority!" I can only listen to so many of these before I shut it off and listen to the engine.
I've been listening to NPR for ~2 hours each day during my commutes for about 2 years. While I really like it, they're not unbiased like they may have you believe. They don't always up and say it, but their most common tactic is bringing on an 'expert', who pontificates about X while the host nods in agreement and says how smart they are. Listen closely when talking about Israel, Bernie/Hillary (I couldn't stomach the 15 minute puff piece on her yesterday), and digital privacy (David Greene got called a government shill by Darrel Issa on-air). I still listen to it but occasionally I have to put it on mute for a segment or two.
Good point, I'll update the description - I really want to know what questions I should be asking with regards to my options in order to assess their value.
Or it's "long form", which is increasingly becoming an excuse to neglect any attempt to captivate readers. Images in lieu of good writing is bad, but long drawls of text aren't much better.
Nice! Really liked the sunk cost part. However, sometimes leaving isn't really a good idea because it's another N minutes to another station, which could take you M minutes farther from your destination than your current train, which arrives O minutes after you get there, which takes P minutes to your stop. For each station, would it be possible to instead calculate the point where (M + N + O + P) < max_wait_time?
Not knowing about Leipzig[0], I've been trying to come up with my own representation of music in JS to work with the Web Audio API. My biggest puzzle so far is how to a) keep a rhythm and b) allow musical "blocks", which are indeterminate in length, to fit into this rhythm. I was thinking that these blocks would be pre-defined functions which represent different aspects of music (bassline, riff, etc.) which could be repeated and inserted at arbitrary time in the composition.
If anyone is interested on working on this drop me a pm/comment (it's just for fun)
For automated building/deploying .NET projects on Windows you have very little choice. Powershell has its own libraries to invoke MSBuild and it's integration with .NET saves a ton of effort on more complex tasks (like parallelization, background jobs, and service management). Is it irreplaceable? Maybe not, but it's clearly the most powerful tool for the job.
Is it me, or are there horrible stability issues on Windows 10? I cannot have more than one editor open without one of them crashing. This is an issue on 3 of my W10 machines.
I don't know if a standard library would actually fix the problem of package over-use. I keep seeing examples of projects importing _ or something similar when the feature they use already exists in the standard. You don't need _ for map anymore. You can lead a horse to water, etc.
I don't have an issue with modules or the Unix philosophy, I have an issue with using NPM for all these tiny modules. Hint: you can make your own modules, store them within the project, and add them to your package.json to be required anywhere.
In my experience, pairing interviews usually falls into two categories: one where you're tapping away at a problem while your interviewer is doing a work assignment (but please ask me questions), and the second is where the interviewer is grading you (and interjecting) line-by-line rather than actually participating. It's rarely the case when pairing goes as it should i.e. a collaborative work process.
Can you please show a demo/screenshots without me having to sign up? I'm interested but I have no idea how it works (do I need a microphone? iphone? etc), and I won't sign up until I know I can actually use it.
Finally, a post that validates the usefulness of my BS in electrical and computer engineering (despite being a JS guy now)! But seriously, I believe that hardware understanding is extremely useful for all sorts off tangential tasks related to modern programming. I've found that having intimate knowledge of how a computer works, especially around memory and disk access, helps me to understand how to solve problems from the standpoint of a rote-CPU rather than my high-level brain. It's also really useful for deciphering kernel-level errors.
How is this assessment any better than judging a physical community based on their loudest/most controversial members? The "4chan garbage fire" is a rude stereotype.
You can't directly access the classNames of child components i.e. if the component is composed of an <h1> inside of a <div> (with <div> being the top-level component), you cannot directly set the className of the h1 if a prop doesn't exist to do so
I've used a similar, albeit more opinionated library for boilerplate UI stuff (modals, dropdowns, etc.) and the issue I have with it is styling. It works fine for the well-defined use cases but when you need to style something not part of the proptypes or as a child/parent of the given prop, the treatment becomes worse than the cure. You have to resort to rooting around the DOM with dev tools, determining the proper divs (which are usually horribly long and messy), make the style, and hope the library isn't overwriting it at runtime.
>Given the choice between a software engineer who has demonstrated incredible abilities in algorithms, or an engineer or data scientist who has demonstrated both some fluency and, more importantly, curiosity on the financial and legal implications of the work that they’re doing, we will always choose the latter.
Bullshit. Complete and utter bullshit. If you can't do the algorithm dance on the whiteboard you're "not technical enough" - after all, these companies get such a high volume of applicants that there has to be some way to filter them out. Curiosity isn't a measurable metric - it's a "nice-to-have".
Everyone complaining about how React is just a trend is missing the point of React. It's not some revolutionary flash-in-the-pan technology based on a mystical black box, it's an aggregation of best practices that everyone (including yourself) has been clamoring to have implemented for years. Web components? Check. Object.Observer? Check. Virtual DOM? Check.
I thought I was the only one going insane here. It's become legitimately difficult to discover blog posts/articles on programming topics that don't include the asinine "missing term" suffix. There are plenty of great blog posts/guides out there which DO include the term and are relevant, but are ignored for whatever reason. I end doing "xx yy mdn" with the search range to 1 year for most of my JS needs now. But god forbid you search for an object property (i.e. Object.assign) - you'll end up with 75% of results having "object", "assign", but not both.