lan321

It became more of a selling point as regulation came for it. OPF, stricter modification control, etc. Prior it didn't matter as much since it was always decent and you could do whatever you want to it. Now, a pops and bangs tune with a straight pipe will get your car impounded in most countries the first time a cop sees/hears you.

It's a balance. If a country is investing severely in a specific industry you can either tax them out of your swamp, counter invest in your industry or, realistically, do a mix.

It'd be difficult to compete with companies receiving large gov assistance without gov assistance and I find taxing them slightly safer than making it rain on specific people/companies.

The best one I had in that regard was just a nice dude who I wanted to help as much as I could since he'd help me when needed. I don't think any other way would really work in the current landscape. Whenever a manager talks about our grand product and the clients dying to get a taste of our artisinal code stew, even they can't take themselves entirely seriously. The only thing that seems to help is just being liked so your team wants to make your life easier. (outside of money/benefits/promotions and maybe short term gaslighting)

Grandparent:

> Processed foods are much cheaper per calorie than "healthy" options.

Attractive is a separate topic. Regardless of budget, for many people a chocolate cake will always be the most attractive food, regardless of cost. Doesn't mean we should have people living on chocolate cake diets.

I usually prefer

    List<Foo> x = new();

since it gives me better alignment and since it's not confused with dynamic.

Nowadays I only use

    var x = new List<Foo>();

in non-merged code as a ghetto TODO if I'm considering base types/interface.

I see these as separate issues.

On a macro scale you want to see country wide economic statistic numbers go up, regardless of who the money gets to in the end. When your population's age isn't evenly distributed it causes spikes in productivity and costs associated with the elderly which makes the metrics go down. Combined with short term politics that are not incentivized to prepare for it, but rather to play hot potato with it, it makes for interesting situations. If, in the worst case, the country is functioning paycheck to paycheck, you have every member of the workforce supporting multiple elderly and children via taxes, since their taxes were already spent on X or stolen long ago during the productivity boom.

Not always without a performance cost which is a no go in projects with very expensive hardware (ahem Cisco).

Good point.

Not even capitalism. Every economic system has pensions and healthcare costs rising with age, coupled with a decreased productivity.

Outside of the maternity leave issue there's a cultural issue with stay at home dads. I believe in essentially all countries, if the family isn't financially secure, it's assumed the dad's a bum, so leaving the financial situation to your better half feels like it can backfire.

Worded like this it sounds stupid but it's just one of those things..

Weird link to gas chambers.. Do you think 'genocides' will go down if we bring first world militaries to third world standards?

Oops, meant the S85 of the E60 BMW M5. Where I'm from we call it S60 since it's the S engine. Forgot it's not a real thing...

It's like the S60, VW W12, old V12 Continentals, etc. If it's expensive to maintain no one wants to buy it off you so you get hit with massive depreciation costs. You can get a 20y/o 'no issues' 500+hp V12 Continental for 10k where I'm at. They've had a brutal cost/year and cost/mile.

> These cars are just for show

I love vans more than any vehicle, but they're garbage at offroad compared to trucks (even 4motion, etc can't compare). Most people don't use them for that, but in villa constructions sometimes you really want a pickup to get to the site. They're also better than vans in snow. Edge cases but they exist and they're not so obscure that I haven't experienced them.

> an M1 Abrams tank has less blind spots

Absolutely not. You can't even turn around in the driver position of a tank.

The question seems legit to me.. Otherwise worded it's essentially whether there's correlation between both. Without evidence it's more difficult to justify regulation. At the end of the day a pickup is adjacent to a midsize van. To me, both seem like you're essentially getting hit by a wall...

You'd be surprised to see people can't be classified meaningfully based on how much their car weighs.

I feel this is more true in the sense that when they don't care about money you can get them below market value and not that they are better. I find the most valuable employees to be the financially literate ones. The ones who're constantly thinking about the money aspect.

'Will we get more customers?' 'Will they be more likely to stay with us?' 'Are we screwing ourselves out of sales by offering to host a server for remote control on the PC connected to the tool, even though it's cool and we can implement it in a week?'

I'm more on the 'do it because it's cool' side and have had to be wrangled a couple times with such questions since what makes interesting work for myself often doesn't align with client needs or hurts sales, as stupid as it might be.

For lobbied ones votekick is great as long as you remove majority vote from premades. So in a 5v5, a 3 man premade isn't able to kick any of the 2 randoms alone.

I remember the misuse of it but it was better than having your only option be teamkilling, which is now punished in all games via reputation systems.

The only thing I don't see this as a solution for are games like Planetside, with massive lobbies. I know they used to have automated detection and manual review by admins teleporting and flying around, usually invisible to sus players. Once we found a bug and got inside the map able to shoot through the ground and in like 15 minutes an admin came, asked us how we got in there and to get out nicely, before he gets us out forcefully :D

IMO the real solution is back in community servers and votekicking.. It works on old games with no anticheat measures..

Maybe add some blatant detection for people teleporting and doing other absolutely impossible things serverside, but I don't understand why my team has to ruin their 'reputation' teamkilling a cheater so he doesn't ruin the game completely in most current games when the anticheat only catches free, old cheats. Just let people votekick and find someone else in the matchmaking queue who's willing to join halfway through.. Once votekicked enough times you can escalate to the AI (always indians) for automated (manual) review.

Also, you don't even have to ban cheaters. Just isolate them to play with each other. Some might find it fun and keep away from the normal players.

Edit: The 'issue' with community server manual review and votekick is you can be kicked for being cracked or garbage at the game legitimately, but TBH at this point you're ruining the fun of everyone else, so you should probably get in another server/match.. Also that premades can have majority, but that's easily solved by reducing their vote weight.

I've never tried AoC prior but with other complex challenges I've tried without much research, there comes a point where it just makes more sense to start doing something on the backlog at home or a more specific challenge related to what I want to improve on.

Obligatory call to free yourselves from having GMail as your (only) main email and especially to not tie it to YT or other unrelated services.

I can absolutely imagine my YT accounts at some point getting banned for using adblock, some stupid private upload or some comment.

This gets me wondering, who does the cleaning at data centers and such? Do you need to do background checks to swing the mop in there? Is there a market for high clearance cleaning personnel? (like with the extended PSP in CH)

My hunch is telling me there could be a couple positions with decent money (by normal person standards) for little work in that direction. Wouldn't be the first time I've been wrong though.

Relax Rambo

Imma pitch them a cinema exit turnstile with a barcode reader and a bat. You pay the retention tax or you get bonked. Once they see the ROI we can expand service via collaboration with services like Uber to ensure equal experience quality at home.

Some cars have 2 gears as well. One for the acceleration and one for cruising efficiency and top speed. So my guess is to get it going easier and then have 2nd as the eco gear for the speed they cruise at.

I might be missing something but the combination of 'we mustn't break anything' and 'we can't test it without 2-3* team size' sounds like release deadlock until you can test it..

The migrations where I've worked at have always been a normal ticket/epic. You plan it in the release, you do the migration, you do the other features planned, do the system tests, fix everything broken, retest, fix, repeat until OK, release.

Otherwise you're hoping you know exactly how things interact and what can possibly have broken, and I doubt anyone knows that. Everyone's broken things at first sight seemingly completely unrelated to their changes at some point. Especially in large systems it happens constantly. Probably above 1% of our merges break the nightly in unexpected places since no one has the entire system in their head.

Or you're keeping a dead product just barely alive via surgical precision and a lot of prayers that the surgeon remains faultless prior to every release.

For me it's 3 videos of what I searched for and then it just goes to my normal recommended. One of the issues I still haven't fixed with an extension so I just search videos via normal web search.

If you can't get permission to update/change IDE, the company processes aren't working at all tbh. Same if cicd is in another department that doesn't give a shit.

Reminds me of an algorithms professor who'd get us to implement some modified standard algorithm in Java and then go over each implementation really quickly at the beginning of the next lecture. He'd find parts of your code weird, replace them really quickly and leave your clean, working implementation with 20 deprecation warnings.

At the end of the day both solutions/syntaxes work, but..