William

First off, I generally don’t worry about DRY until there are 3 instances, not 2. With only 2, it’s really easy to over-generalize or have a bad structure for the abstraction.

But otherwise, I disagree with the article. If it’s complicated enough to bother abstracting the logic, the worst that can happen in the above situation is that you just duplicate that whole class once you discover that it’s not the same. And if that never happens, you only have 1 copy to maintain.

The code in the article isn’t complicated enough that I’d bother. It even ends up with about the same number of lines of code, hinting that you probably haven’t simplified things much.

Companies won’t hire someone that’s overqualified because the employee is very, very likely to leave again soon. It costs the company a ton of money and headache for very little benefit.

I thought Jekyll just compiled the input files to html/css/js and created a static site?

Hugo, too? I hear Hugo is easier.

I haven’t used either of them.

To add to that last point, I worked for a company (at retail) that claimed to know that keeping customers was cheaper than getting new ones, and corporate even implemented a policy where the clerks on the floor had up to $100 to keep a customer happy. I never once saw that $100 used, and the one time I tried to keep a customer (who had just spent $3000) happy, management refused to let him return a crap $100 printer because he didn’t have the manual in the box. He had left it at home, and was glad to bring it in next time he was in. Nope. And that incident was within a week of implementing that system.

So even when a company understands that point, it’s still really hard to make good on it at the levels that it can matter.

Well, I’ll give it a shot.

Part of it is that they can’t know the point that someone is willing to stay vs leave, and they’re always optimizing for that point. Saving money is always the goal for expenses in a company.

Part of it is that they have a budget that they can’t exceed. Sometimes a person is overqualified for the job, and the job simply can’t afford them. Sometimes that person will stay far longer than they should, when they could get paid much better elsewhere, and sometimes they choose to move when they’re only slightly underpaid for their skills.

Part of it is that there is more to a job than money. Being comfortable, un-stressed, and generally happy is more important at some point than more money. The company tries to balance these things, as it’s often cheaper to relieve or prevent stress than pay someone to put up with it.

In the end, it’s super complicated, but all about money, on both sides.

A torrent link won’t either? In either situation, the site needs to seed their own data, at a minimum.

I use nearlyfreespeech.net. They bill for usage, and since my site gets almost no hits and doesn’t take much storage, it’s ridiculously cheap. Much cheaper than even he $2.50.mo VPS listed in another comment. I just checked, and I spend an average of $.30/mo.

I disagree about humans reading these… As someone who has to read resumes while hiring, I’d rather see this than the word-soup I often get. It gives me an idea of what you’re best at, and I can figure out that you’d also be able to learn/do similar things.

Weird. I just found out about the Warp Terminal today, and now this seems somewhat similar. Weird coincidence.

Yeah, I think it’s pretty interesting. I’m a little worried about how long you have to hold them, how quickly they can be used, and how often they interfere with typing very fast. I think those things would interfere with each other, and I’d quickly find it annoying.

Also, I guess it’s a variant of #7: Tell them that their code has caused bugs in existing code and ask them to fix it.

It’s technically possible to do that, but it’s kind of a pain. I asked about server-side JS because the server is where I’d do something like this as my first choice.

If you really want to do it in the browser, you could use an AJAX call to get the html from the server, then use DOM functions to find that snippet by id. (Or just put them in separate html files and save yourself the pain of those DOM functions.)

I found this for you. https://gomakethings.com/getting-html-with-fetch-in-vanilla-js/ I think it actually has most of what you want to do.

Are you using Javascript on the server, such as with Express?