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.

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.

That’s an interesting way to start the estimation. My first thought was ‘no way’, but then I thought more about it and I agree more and more. I’d bet that you get a lot of push-back from people when you use that estimate, especially those who don’t understand what goes on behind the scenes.

That doesn’t mean it’s wrong, just that it triggers people into a negative reaction.

I wish that was a panacea. If you work remotely, but they require you to be available via some messenger, they can and will interrupt you just as much as if you were in a physical office with a door.

https://ivopereira.net/efficient-pagination-dont-use-offset-limit

This seems to be the same article.

I have my doubts about the technique, but it could be useful in certain controlled situations.

Even if you release multiple times every day, refusing to release on Friday still makes sense. It’s not about expecting bugs, it’s about guaranteeing that your devs’ time is their own. If you aren’t okay with paying your devs for time they spend dealing with their own problems at home (without charging them their PTO time for it!) then you shouldn’t be okay with making them work on weekends, no matter how rare it is.

I voted you up, but this is tough. I write tests at work when they’ll help me, but nobody else maintains or creates them. Except for the tests that the boss created and insists that everyone run.

I haven’t pushed terribly hard for my tests, but it’s pretty obvious that I wouldn’t get any traction if I did, and I’m picking my battles.

So while I agree with “write your tests anyhow”, it’s a lot harder than it sounds, and a lot less successful than a proper testing strategy that’s embraced by the team.

Yeah, I didn’t watch the video, but my first thought was “no, that’s just FAANG”. Plenty of smaller companies hire entry level developers.