> I'd like to see a revival of awk. It's less easy to scale up, so there's very little risk that starting a project with a little bit of awk results in the next person inheriting a multi-thousand line awk codebase. Instead, you get an early-ish rewrite into a more scalable and maintainable language.
Taco Bell programming is the way to go.
This is the thinking I use when putting together prototypes. You can do a lot with awk, sed, join, xargs, parallel (GNU), etc. But it's really a lot of effort to abstract in a bash script, so the code is compact. I've built many data engineering/ML systems with this technique. Those command line tools are SO WELL debugged and have reasonable error behavior that you don't have to worry about complexities of exception handling, etc.
The problem Perl and the like have to contend with is that they have to compete with Python. If a dependency needs to be installed to do something you have to convince me that whatever language and script is worthwhile to maintain over Python which is the next de jure thing people reach for after bash. The nice thing about awk is that it’s baked in. So it has an advantage. You can convince me awk is better because I don’t have to deal with dependency issues, but it’s a harder sell for anything I have to install before I can use
And it’s not even that Python is a great language. Or has a great package manager or install situation. It doesn’t have any of those things. It does, however, have the likelihood of the next monkey after me understanding it. Which is unfortunately more than can be said about Perl
> The problem Perl and the like have to contend with is that they have to compete with Python. If a dependency needs to be installed to do something you have to convince me that whatever language and script is worthwhile to maintain over Python which is the next de jure thing people reach for after bash
A historical note: Perl was that language before Python was, and it lost that status to Python through direct competition. For a while, if you had to do anything larger than a shell script but not big enough to need a "serious" C++ or Java codebase, Perl was the natural choice, and nobody would argue with it (unless they were arguing for shell or C.) That's why Perl 5 is installed on so many systems by default.
When I first started using Python, I felt a little scared for liking it too much. I thought I should be smart enough to prefer Perl. Then Eric Raymond's article about Python[1] came out in Linux Journal in 2000, and I felt massive relief that a smart person (or someone accomplished enough that their opinions got published in Linux Journal) felt the same way I did. But I still made a couple more serious attempts to force Perl into my brain because I thought Perl was going to be the big dog forever and every professional would need to know it.
But Perl was doomed —- if Python didn't exist, it would have lost to Ruby, and if Ruby didn't exist, it would have eventually lost to virtually any language that popped up in the same niche.
Perl is installed by default on most Unix systems. FreeBSD being the exception. Python isn’t. Although Python is popular; if we’re comparing the probability of someone having the interpreter installed already, it’s greater for Perl, even if people aren’t aware they already have it.
Though one would probably never be able to work with an assumed install of Python anyway because one would not be able to assume a specific version. I am guessing this is a lesser problem for Perl, since it’s been frozen at some version of 5 for the past 25-30 years correct?
There's no greater source of professional resentment than suffering under a manager who's incompetent and a narcissist (my summary of his blurb). After 18 years at Google he probably feels safe burning that bridge.
After 18 years at Google he's likely at a stage in his life where he's at f-you money in his bank account.
If he cares more about the company culture than being rehired by the people that disagree with his outlook, why not let it fly? If it instigates a culture change, he wins at the cost of a professional bridge he doesn't value anyway.
One great way to lose the f-you money in your bank account is to get involved in a harassment or slander lawsuit because of some offhand things you said that got pasted all over the interwebs.
I'm not saying that will happen here, but if I were writing this blog post I would have deliberately avoided specifics like this because of that, in part.
It's one thing to legitimately trash Sundar Pichai; another to name some middle-level manager like that.
Zero risk of that. Libel requires proof, and having this go to court would require airing that proof in open court. If this is truthful at all and it only casts shade on one director, and retaliatory suits would be more harmful to the company and illuminating of internal affairs than this blog post. Any competent HR would much rather mediate in private.
The point is, you weren't the person who wrote this. And I'm glad someone did. We need a little more scrutiny on how given people run industry leading ships aground despite making more in a year than some people make their entire lives.
Pretty much half the people who work at any given bank have some sort of "VP" title. "Middle-level" would be overestimating the standing of many with that title.
What a truly arbitrary comment. This is a conversation that is clearly about Google. What possible value did you think you added with what you wrote here.
You wrote Since when is a VP middle-level management ? in reply to the parent commenter's observation It's one thing to legitimately trash Sundar Pichai; another to name some middle-level manager like that. A VP is very much middle-level management.
To be clear, since I guess we're really drilling down on this: VP denotes senior management at Google? So Hixie's blog post wasn't really dumping on a random middle manager as cmdrporcupine (an ex-Googler, I think) suggested, which was the point of all this, but rather picking on a potential C-suite executive or something?
People who never had the misfortune to work with a truly toxic manager or co-worker are often oblivious to the damage they can cause. I'm speaking of psychological damage, burn out, anxiety, stress, depression, health problems. Naming their abuser can be helpful to people who had to endure such a thing.
Absolutely. Walmart used to have a policy of refunding gift cards in cash. You'd buy many at one location, and return them at another. Less trackable. Gift cards are also used quite regularly in human/sex trafficking to control the victims.
I have doubts about this too. I remember seeing a Humvee autonomously driving around the CMU campus back in 1998. I get the feeling research institutions and, now, product companies have been working closely with local city governments about safely releasing these into the wild for some time.
In the US retaliation by an employer for an employee reporting inappropriate or unlawful conduct to a superior is unlawful. This is a protection granted at the federal level.
If you present a document you know to be untrue, that’s the same as lying.
OP, get a pen test scheduled and tell the client, “You know, we’ve had a lot of changes since we rolled out. Since you asked, we felt it was best to get a current pen test to reflect our present state.”
No lies (just a slight deception with the truth) and you get a legit pen test your client can rely on.
That sounds like a very reasonable course of action. However... given the circumstances the author is in, I don't think his director is the type to schedule a pen test and then wait for all the violations to be resolved in order to get the contract. (I assume the client, as a government entity, is legally required to obtain a minimum number of bids for contracts and make a decision in a timely manner.)
Lying and fraud aren't the same, which is the author's concern. Lying incurs a social cost. Fraud incurs both social and legal costs.
I don't... think so? He clearly intended to create a deceptive document, and wrote separately that it was false (don't delete this, wink wink, nudge nudge). The director didn't hold a gun to his head.
A determination to perform a particular act or to act in a particular manner for a specific reason; an aim or design; a resolution to use a certain means to reach an end.
It doesn't matter if the OP wanted to deceive the client or was pressured to do it, they still intended to do it. Again, IANAL, but people are held liable for their illegal actions all the time, even if they were pressured. Also, think about the kind of pressure this manager is applying relative to the (potentially) fraudulent thing they're asking the OP to do. If the manager was holding their family hostage, by all means, lie about the pen test. I know it's easy to advise the OP to "just quit", but not everyone has the luxury of doing that for personal or financial reasons. That being said, I'd rather be out of work and struggling instead of on the hook for fraud.
Magnesium saves me too. I've had persistent leg cramps since my teens. If I look at my right calf the wrong way, it seizes up, especially after a night of drinking. All of that went away when I started taking 200mg supplements daily. Big, big difference.
Do you find a certain type works better? Last time I looked into it there were various types like malate and glycinate and I got a bit of analysis paralysis. I also get the leg cramps at night!
Citrate and oxide are laxatives. amazon basic is decent. Threonate is thought to be able to be best absorbed and available to brain. Also very expensive. For bulk, I buy at nootropics depot for Threonate or just Amazon basics.
In the article:
> “The pros are certainly fundraising development. I think people like to think that if they give a lot of money to a university, their children will get special preference,” he said. “I can sort of understand the other side saying it’s unfair to other applicants.”
The quoted person doesn't deny it helps, but people like to think it helps.
Also, please don't donate to your university. You paid them for an education, food and housing. You don't owe them anything else. Compound interest on their takings is your contribution.
Taco Bell programming is the way to go.
This is the thinking I use when putting together prototypes. You can do a lot with awk, sed, join, xargs, parallel (GNU), etc. But it's really a lot of effort to abstract in a bash script, so the code is compact. I've built many data engineering/ML systems with this technique. Those command line tools are SO WELL debugged and have reasonable error behavior that you don't have to worry about complexities of exception handling, etc.