88 karma · joined March 5, 2016
If you do the math on their TC to see how it actually works out from month to month, it makes sense. Unless you get more RSU's, you take a huge hit in pay, unless you weren't cashing in on them to make ends meet.
Obviously, the one who uses the most wood wins! ;) If told right, they should easily figure out why LoC is a horrible metric.
Build an ecosystem, not a science project.
Build an ecosystem, not a microbiome.
> I can quickly train a person to have knowledge in some domain,
This part I have a little bit of trouble with. If you have a trivial domain, sure. In my experience domain knowledge takes a while to truly get your head wrapped around. But I expect that's why there's always other things that people do in an interview.
...And what comes when people are under the cloak of anonymity, or otherwise feel there will be no negative consequences to whatever they choose to do.
The other problem I see is that a person says what they feel in the moment---and then they move on. But the (emotionally charged) comment from that moment lives on, potentially for years. The "energy" doesn't dissipate with time like it does in "real life".
There was a time I thought I'd trained it to stop telling me about what celebrity said or wore what, but those are creeping back into my feed.
After you're done with that corner case, you may find it better to determine if they don't overlap and negate that.
Imagine you're being taken on a "backstage tour" of the Internet. They open the door, turn on the lights, and as the distinct odor of decay and the chaotic scene of confusion and disarray greet you, you hear the guide blurt out, "Ah, crap! Who made this mess?! I swear it was presentable just a little bit ago! Well, good luck getting ME to clean this up! OK folks, we're outta here!"
And THAT is AWS in "plain English".
Those who can't do, teach. And those who can't teach? Infosec.
I'm very comfortable in SQL, and would prefer to write my queries. But our team has grown, and we've found that developers say they know SQL, but they really don't. In general, I've found that it's not the syntax that messes people up. There's a significant mental "jump" between the usual procedural coding paradigm and the "set based" paradigm offered by SQL. Some people just never catch on.
So we're going to start using an ORM (Entity Framework Core 2) so that the "mere mortal" developers can pitch in. I know there's a way to run raw SQL, so I know that when we find spots where the ORM fails, we can just rewrite it with some good SQL if we decide that's best.
But maybe that'll never happen? We've been trying to do simpler SQL stuff as of late so that the heavier lifting in the system is done by the application/client instead of the database (bottleneck). As the database sees simpler, less unique queries, more stay in the plan cache, indexes are more reliably hit as expected, and performance increases.
Canceling "cable" was a bit jarring at first, but I don't miss it anymore. It was kind of like trying to stop watching the show "24". The show had its hold until I missed the subsequent episode, then it was gone; I didn't care anymore.