ts330

And this is why there is an impedance mismatch... these people are interviewing for a "computer science" role they're filling when really they want a programmer. The two are different.

Considering that it's our fellow programmers doing the interviewing, I'd say we're failing ourselves here. I'd wager that in almost all cases, those doing interviews have had zero training on effectively recruiting anyone (let alone other developers). An effective interview requires preparation - and I bet the majority of developers do this right between saying "fuck, have they arrived already?" and starting the interview. Is it any wonder it falls back to the standard approach of "Google does it, it must be good" or a dick swinging contest trying to prove how amazing your team is, because "fuck yeah, we all write search algos every fucking day - it's why our product is amazing."

Oh stop complaining like MS is the only company to do this. Twitter is just as complicit in this sort of behaviour. If you're going to base your entire business on someone else's platform, don't start complaining when the earth shifts and you suddenly find yourself without foundations.

You take risks and bets in life and business. Use the tools that give you the greatest flexibility and build a robust business. In this case, these announcements increase that flexibility.

While everyone here keeps complaining and debating Embrace/Extend/Extinguish, someone is embracing the changes and out-executing them. I know which I'd rather be.

when those packages are not under your control, it has everything to do with how granular they are and by extension how many you depend on and thus have to trust/verify.

when was the last time you rechecked the entire source of a package you depend on after updating it?

What's not to like? The fact that every one of those dependencies is an attack vector when one of those package's maintainers gets compromised / project hijacked / bought off by some black hat operator.

It's easier to keep an eye on a small number of trusted parties than 200 random strangers.

You thought this SNAFU was bad...

YES YES YES!

In all the debate about this, why is the trust-dependency-fuck-show not getting more attention?

Every dependency you take is another degree of trust in someone else not getting compromised then suddenly finding all sorts of horribleness making it into your production environment.

It beggars belief!

Totally agree. But, as usual with "nice things", this one doesn't align with Spotify's best interests. If it did, this would have been solved a long time ago - it's not like they haven't acquired the tech/skills to do so.

Those nice little lists Spotify helpfully shows are almost guaranteed paid-for inclusion (apart from the chart-style lists, to a degree, but that's another ball game). Labels/Record Companies/Promoters etc are almost certainly paying for inclusion there as it drives huge awareness and subsequent merchandise, ticket etc sales. Much like radio airplay, where the station controls the programming, this is where Spotify gets access to the same revenue stream.

So giving me perfect recommendations filtered through an exclusion list for which, let's be honest, the maths and data science for have long been sorted out via standard ad-tech and e-commerce recommendation engines, is simply not going to aid in the value proposition for a nicely curated list they can charge to be in.

I'm not entirely sure they're the next big thing. More likely, is that 15 years ago, it was people who were used to static sites began moving to dynamically generated ones as sites became more complex. They were the new thing then. Now we have a load of people who have grown up with dynamically generated sites and are suddenly discovering the benefits of static sites - thanks in part to the proliferation of tools that are easy to use.

It's the usual boomerang cycle of discovery and adoption.

Both types of sites have their benefits and it's a balancing act to use the right tool for the job. It's getting this right that comes with experience and an understanding of the current pitfalls of each. It's the rough edges that push people in the other direction and without the experience of the pitfalls of each, it's inevitable that people start predicting that one solves all the problems facing the other.

I fully expect the usual over reliance on the wrong type of tech for the sake of it being the current hotness and then an over correction in the other direction the moment we have a new generation of developers.

Given enough time, we may just have a modern Emoji pictograph set to rival that of the Chinese.

Sorry, you missed the point. My life is better overall because React solves a ton of problems other frameworks are battling with. However, we still have to rewrite this same widgets over and over - energy that may be better spent elsewhere if that were possible. These innovations are not iterative from this point of view - they re-level the field. My point was: "there has got to be a better way of dealing with these basic components"

fwiw, I thought this little project was really cool.

Every time someone invents another framework, 1000s of hours are lost to rewriting these widgets - colour pickers, date pickers, drop-downs, combo-boxes etc etc. And that's before people complain about lack of flexibility and all the missing features their predecessors have accrued over time. More wasted time as people try to get to grips with yet another style of configuration, operation and tweaking to fit real world use cases.

I'm all for innovation and advancing the state of the art, but there has got to be a better way of dealing with these basic components. All we're doing here is creating projects for those with time on their hands, frustrating those with none, and keeping StackOverflow in business.

Someone buy this man a beer.

tell us what you've taught yourself. you never know who's reading. i'm hiring.

it's coming. soon.

this is the first time I've seen APL... and I have to say, as a competent programmer who knows a good few languages backwards, I now know what it must look like when my wife looks over my shoulder when I'm coding... total alien hieroglyphics!