mtVessel

True, the stacks are more complex today, but the resources are greater. Back in the days when the error was in the beige box, if the books/CDs/DVDs you had on your shelf didn't address the exact problem, you had to roll up your sleeves or you were SOL.

Nowadays, research skills are more important, but I see a lot of devs who just don't have them. Can't find the answer on the first page of your first (poorly formed) search? Run get the senior dev. To me it reads like incuriousity and laziness, or lack of training.

I don't mind doing some coaching, but if you're a dev, and you can't even be bothered to read the error message, what does that say about your effectiveness?

/rant

Because what better way to configure a parser than to require it to use a completely different parser for configuration? /s

It's not just on mobile.

Thanks. It would have been nice if the author had explained that, instead of you.

Now, when is git-gc run? Of course, it's "[w]hen common porcelain operations that create objects are run".

So, what are common porcelain operation? And which ones create objects? On second thought, never mind. I'll just try not to leave anything inaccessible for more than two weeks.

> "...your work will not be lost for at least two weeks unless you really work at it"

What happens after two weeks?

You're being kind. The author's statement is utter nonsense. If you store the same fact in two places and only change one of the them, it doesn't matter whether you update in-place, or create a new version of record -- your data is still corrupted.

As much as people like to talk about "footguns", that's the value proposition of C++, zero cost for anything you don't use.

Managed/interpreted langs have a different proposition: pay up front for all the features, but your complexity never increases whether you use none, one or all of them.

I agree. One does not "throw the kitchen sink". I think the author is conflating it with the "throw the book" idiom.

> Don't think god needs to rest.

Remind me again what happened on the seventh day?

I'll tell you in one word. Tradition![1]

[1]https://www.youtube.com/watch?v=sWSoYCetG6A

Am I understanding this correctly? Are you saying it's better to change things rather than understanding the existing code?

If it's implemented at all, it's typically "long press", which, for my money, is about as counter-intuitive as it gets.

Thanks, that's much more informative.

Is it? How do you know? Have you reviewed the budgets? Do you work in education in Baltimore, and thus, have a sense of what an appropriate number would be?

I don't know the answers, but I do know this -- it's a hell of a lot less than what gets spent in the NY metro area.

Wait, is that right? I thought that was one of those "lies to children". I mean, yes, the electrons move (er...drift), but I thought the important thing is that it's the charge that moves, not the electrons.

At least it's not just me that thinks the usual explanations are lacking.

How does horizontal sharding help with HA/DR concerns?

Okay, that makes sense. I appreciate the concrete example.

Thanks, but I still can't see it from where I am. The problem isn't that I can't see the use of (to take your example) sum types. I've coded around C#'s lack of them before, and sure, it was clunky and painful. But I've needed them like < 1% of the time.

If I had them as a first-class language feature, would I use them more? What for?

With all of the enhancements to C# over the last decade, is this still relevant in 2021? None of the benefits listed seem that compelling. (Serious question, not trolling.)

Anyone who has worked with a team in a time zone 8+ hours away from their own can already answer this question. It depends entirely on the technical and communication skills of all involved parties.

> Logically, it should be exactly, equally hard to be wrong all the time, but somehow more people achieve it.

Cipolla's first law of stupidity[1]:

Always and inevitably everyone underestimates the number of stupid individuals in circulation.

[1] https://en.wikipedia.org/wiki/Carlo_M._Cipolla

I like the idea, in general, but I'm finding this makes for confusing navigation. In particular, the idea of a "node" being the set of subnodes with the same name is counterintuitive to me. Maybe it's just the terminology, or maybe I just find things easier to navigate when they're presented in a strict hierarchy.

I did immediately get the "Everything2" vibe, which is cool, but the thing is -- I've never done anything other than a random walk through Everything2. I couldn't imagine trying a directed or semi-directed traversal of related topics in Agora.

What am I not grokking?

I agree with gp. The opposite of "neither this NOR that" is "both this AND that".

> Imagine if pharma companies went "gosh, but hiring quality inspectors to make sure all of our drugs are untainted just doesn't scale!"

What do you mean, "imagine?" They do say that[1], and it's a tremendous problem.

[1] https://www.newsweek.com/2019/07/19/bottle-x-exposing-impuri...

My favorite feature of logical names was that they didn't just point to directories -- they could be a search path!

To test new code, all I had to do was create a directory to hold my changes, and copy in just the files I wanted to update. Set the logical name aliasing the code location to search first in my "branch" directory, then in the main directory. Any code in found the top-level search location takes precedence over the main directory.

Boom! Instant branches, but supported at the OS level.

Similarly, you may repeat this mantra as many times you like, and yet, "theft of services" will still be a crime in most jurisdictions.

I worked in a VAX shop early on. We had an intern who was pushing Linux on us. He said to me, "Sure, VMS is great, but the downside is you need a wall of manuals." My reply was, "Downside? That's the UPSIDE! You can get an entire wall of manuals for it!"

I still feel that way.

> Pick any random ingredient you enjoy and cook it using a few different techniques and a few different time/temperature combinations.

This, incidentally, is also the best way to improve your programming skills.

You know what's funny? I've read the promo material, signed up, and there's little mention of how this program works, whether it's synchronous, async, or what? I'm assuming it's all async, since otherwise, it would be titled "Startup School for future founders who are comfortable with open-ended commitments, because they're young, single and unemployed."

In the third example, is function isProlific missing a parameter?