dexterous

But, not because I think schools and colleges would jump at the opportunity and start training the next batch of students in said language just because some government department or a bunch of large corporations supported and/or mandated it. Mostly because that hasn't actually panned out in reality for as long as I can remember. Trust me, I _wish_ schools and colleges were that proactive or even in touch with with the industry needs, but... (shrug!)

Like I said, I still think the original argument is flawed, at least in the general case, because any good organization shouldn't be hiring "language X" programmers, they should be hiring good programmers who show the ability to transfer their problem solving skills across the panopticon of languages out there. Investing in getting a _good_ programmer upskilled on a new language is not as expensive as most organizations make it out to be.

Now, if you go and pick some _really obscure_ (read "screwed up") programming language, there's not much out there that can help you either way, so... (shrug!)

FTFY

(Edit: forgot HN markup doesn't do strikethrough; that's what the ~~'s are for above.)

I'm just glad those just sat on his table and never made it onto anyone's back.

    "Mr. Worf, villains who twirl their mustaches are easy to spot. Those who clothe themselves in good deeds are well-camouflaged."
    - Picard and Worf, discussing both the investigations and the misguidedness of Admiral Satie

It's strange that a general idea expressing (assuming?) overarching maturity has led to quite so many petulant arguments, wouldn't you say @ketozhang?

Would Thursday be a good time to checkpoint on this?

Thank you so much.

Relevant excerpt from It doesn't have to be Crazy at Work.

Let's see... it took them, what, ~7yrs to screw Bungie over and take Halo away from them? So, I guess it's still too early to tell WRT Github.

Think of it as Plaid storing OAuth2 access tokens, sort of; and the tokens do expire (over pretty long periods), though, some bank integrations do allow them to generate their equivalent of refresh tokens.

Plaid didn't go into this blind; they know the tightrope they're walking. As someone who's worked with Plaid to build an integration into our product, I'd say they're definitely in a very gray area, but that's pretty much all of the Fintech space right now.

Although, I'd also say they're not malicious; even if it is just motivated by the fear of the bad press resulting in a customer exodus.

Just how far "back in the day are we talking? 'Cause I've see stuff ranging from VB (just VB, no .NET or WinForms) all the way back to MFC based UIs back in _my_ day. :)

I just feel like we should get our timescales calibrated.

AFAIK they weren't built out of repurposed containers, but new ones. But I could be wrong.

Could you expand on that? I'm curious.

So, basically, everybody is bad at it.