[-] FizzyOrange@programming.dev 4 points 3 weeks ago

This is really terrible advice. Sometimes it's better to do that, but definitely not in the example from this article.

If anyone says you should always prefer polymorphism to switches they are a bloody idiot.

[-] FizzyOrange@programming.dev 4 points 4 weeks ago

There’s no value for the higher ups in fixing it

Well there is, it's just long term value that they don't even understand.

Really you should just make fixing technical debt part of your regular job. Don't ask for permission, just do it. (Except for really big things obviously.)

[-] FizzyOrange@programming.dev 4 points 1 month ago

Think of it from the company's point of view. If you're hiring a new employee then the options for a good candidate are a) move jobs and work for you, b) move jobs and work for someone else. You're competing with other companies.

If you're reviewing an existing salary for a good employee their options are a) do nothing and accept the shitty raise, b) move jobs and work for someone else.

Moving jobs has significant cost for most people - it's time consuming, stressful, might involve moving house, etc.

That downside gives employees who haven't proven they are looking for a new job a significant negotiating disadvantage.

If you really want you can tell your boss you are actively looking for new jobs. That will increase your chances of getting a bigger raise, but of course it has other downsides so most people don't do that.

[-] FizzyOrange@programming.dev 4 points 1 month ago

I think those jobs are a myth. You probably get like a 20% premium for using COBOL, so if you look up the salary of a Cobol consultant in America it's going to seem like an enormous salary on an absolute scale.

But so is a C++ consultant in America or whatever. Probably not worth learning COBOL for.

Feel free to correct me if I'm wrong, but I have looked once or twice and the COBOL salaries seemed entirely normal.

[-] FizzyOrange@programming.dev 4 points 2 months ago

I dunno maybe once a week or so? We don't actually have a system that detects if your pip install is out of sync with pyproject.toml yet so I run it occasionally just to make sure.

And it runs in CI around a dozen times for each PR. Yeah not ideal but there are goodish reasons which I can explain if you want.

[-] FizzyOrange@programming.dev 4 points 2 months ago

True but it'll have to be like 10% and I don't see that happening ever really. Unless Microsoft really screws up, which to be fair they are doing their best.

[-] FizzyOrange@programming.dev 4 points 3 months ago

Haven't tried Rye but I have used uv (which Rye uses to replace pip). Pip install time went down from 58s to 7s. Yes really. Python is fucking slow!

[-] FizzyOrange@programming.dev 4 points 5 months ago

Functional programming doesn't just mean higher order functions. There's a range of other features that it implies.

[-] FizzyOrange@programming.dev 4 points 5 months ago

You don't have to install it on the machine where the script is run. That's the point.

[-] FizzyOrange@programming.dev 4 points 6 months ago

I think he's being downvoted because he's one of those "who needs type safety?" fools. And because of the general rambling nonsense. Yeah JSON works fine for 99% of use cases but that isn't what he said.

[-] FizzyOrange@programming.dev 4 points 6 months ago

Why is that a hard pill to swallow? Longevity doesn't imply goodness, especially in software. Same for Bash, C and gnu utils.

It also doesn't mean it's a good idea to use it. I would strongly recommend... basically anything else over Jenkins.

Maybe I missed your point there.

[-] FizzyOrange@programming.dev 4 points 6 months ago

I liked Netbeans much more than Eclipse. It didn't have that stupid workspace system at least.

view more: ‹ prev next ›

FizzyOrange

joined 1 year ago