boring work stuff, they entered wrong data and made a ticket to fix it several months after the fact. That data they enter is the input for a bunch of calculations, so cleaning up that mess is a lot of work and I’m the only one equipped to do it. They should be well aware of the importance of being exact with what they enter and only signing off on it when they’re 100% sure it’s correct, yet they keep messing it up. They made a stupid excuse about having to sign off on it even though they knew it wasn’t 100% done, when it’s been made perfectly clear that this is unacceptable regardless of circumstances because of legal ($$$$) ramifications
edit: I should add that those ramifications are potentially severe enough to bankrupt us. That particular administrative body does not fuck around and will tear us a new one if they smell blood
well yes, but I don’t think it’s necessarily bad to go about it like you described, as long as you know that you’re not actually using the smaller issues to procrastinate on the big issues. Tackling the smaller issues first can help you to understand the bigger issues better, both consciously and subconsciously, so as long as it doesn’t actually matter in which order they’re done, I think it can be more effective to do the smaller ones first. That all goes out of the window of course if you’re using the small issues to avoid having to think about the bigger ones
many are yes, but not all. Bitcoin and Ethereum (among others) are legit, and there are a few NFT projects out there that actually try to do the right thing even if they’re not worth much at all. Many other NFTs are nothing but pictures that have no meaningful value except what you assign it to, but they never pretended to be anything else so that’s still not a scam in my book
I guess I don’t understand this obsession with speed?
for me it hasn’t been build speed but rather execution
I’ve run into problems with dayjs slowing down requests where I need to do a lot of processing. There are arguments to be made about replacing dayjs with datefns and how I should’ve been doing it differently anyway, but fact is that if the whole execution environment was twice as fast, it probably wouldn’t have been much of a problem at all
you know what I do me some mechanical keyboards but I recently switched back to a run of the mill scissor switch keyboard because I think I like low profile keys more. Now I know there are some low profile mechanicals out there but I’m not sure I care enough to spend the money to get one. I think I’ll give this one a go for a while, maybe I’ll switch back later
I spent some of my formative years in public housing. It was definitely a bit more sketchy than the privately owned homes across the street but all in all it was a fantastic way for me to get my feet under me as a student and young adult. That’s exactly what scores of young and also not so young people desperately need right now
public housing doesn’t require tax money. It is often facilitated by it, yes, but don’t act as if the rent is necessarily sponsored by the government just because public housing isn’t designed to extract the maximum amount of money from the renters. There’s plenty to criticize about public housing without resorting to falsehoods
a 4 core CPU isn’t going to cut it in 2023 anymore, and anything new that you’d want to upgrade to is going to be bottlenecked by that 1070. You could of course look at used parts if your budget is tight, there are a lot of used (ex-miner likely) GPUs out there that could tickle your fancy and I bet there are plenty of people selling their 8+ core Intel / AMD + DDR4 + motherboard as well to upgrade to DDR5
Certainly but it will last longer.
that’s highly debatable if we’re talking about a $600 PC. I mean, yes you can argue that with games on PC you can always figure something out to get acceptable performance, but people in the market to buy a $300 console likely lack the experience, knowledge or time to do that
a) you don’t have the ability to understand what the client actually needs
the client doesn’t understand either. This I have had to learn to accept and not blame the client for, it’s OK and we’ll figure it out together
b) if you over-architect your solution
we can’t figure out what we actually need by overarchitecting something to death. If and when you find you’ve coded yourself into a corner because you didn’t architect well enough 6 months ago, then congratulations it seems like what you’re doing is good because you’ve made enough progress to actually need a better architecture
obviously I’m oversimplifying and people more experienced than me understand better how to walk the tightrope between unmaintainable spaghetti and an overengineered mess, but me, I try to keep shit as simple as possible because you never know
it has a lot of cruft and gotchas and lacks a good standard library (which is why npm is a thing). That means there’s a lot of bad javascript code out there and a lot of people who have had bad experiences with it. But, if you take care to not shoot yourself with the included footguns and you know your way around npm, it’s a perfectly fine language for its purposes in front- and backend development IMO
they aren’t, except perhaps as a counterexample of some dubious sort