Because they prefer electing republicans to winning if the cost of winning would be compromising even a fraction of an inch with the left
Because they prefer electing republicans to winning if the cost of winning would be compromising even a fraction of an inch with the left
You can just do
grep Error5 log.txt
To appeal to people who don’t really understand how stuff works but think GPU is AI and fast
Well yea… If you write “return <object of some other type>” that is actually wrong, as opposed to just not having gotten around to filling it in yet
The thing you’re missing is that other people come in and say the same thing as you, and when they listened to them once, they absolutely freaked the hell out, left bad reviews, maybe threatened to sue or something. So you just have to live with that unfortunately.
the token is only used for governance (and possibly also fundraising)
That should make you just as worried
It’s not too crazy here :) 25 days a year is the legal minimum and I get about 10 more than that, plus a few extra from doing overtime here and there. That’s why I say the lifestyle is on the whole better here even though we don’t earn nearly as much. It’s still plenty to pay the mortgage, and Europe is right on the doorstep to spend all that holiday time in.
Sure, yes, but those kinds of positions in the US make 300k or more too. Also, then you work in finance and you have to live with the fact that you are categorically making the world a worse place every day.
So you never stumbled upon bugs while doing work
That’s not what I said… Either the bug is related to the task, or it isn’t. If it’s not related to the task, there’s no reason to fix it on the same local branch either.
Also, some teams do care about building their work on atomic commits, because they understand the problems caused by mixing up unrelated work on the same PR, specially when auditing changes to track where a regression was introduced. You might feel it’s ok to post a PR that does multiple things like bumping up a package version, linting unrelated code, fixing an issue, and post comments on an unrelated package, but others know those are four separate PRs and should be pushed as four separate PRs.
Well, these things don’t meet the standards of your earlier example at all. Linting unrelated code and posting comments on an unrelated package clearly aren’t needed for someone to work on the main issue fix they’re doing. If it’s unrelated code you again lose nothing by switching branches to do the work.
Yes, depending on where you live rent might be similar (London isn’t much cheaper than NY or LA) but cost of living is otherwise less. Also, people tend to work much shorter hours (a limit of 37 for me, any extra is returned as PTO) and start with much more annual leave (25 days discretionary, for me, plus public holidays, plus we close over Christmas and new year’s). Furthermore there’s no health costs to pay etc. On the whole it balances out and I think the lifestyle here is better, but I do envy the extreme salaries of those in the US.
About half of the equivalent in the US, often less. It’s exceedingly rare to make 100k here even in a senior position, although it does exist. Median is 40-50k (pounds, so times that by 1.2 for USD).
Oh, okay. I’ve never encountered a situation where I needed that bug fixed for the task but it shouldn’t be fixed as part of the task; if they’re touching the same functionality like that I really don’t see the need for two PRs. But sure, sounds helpful in that really niche case.
I think I understood the example; I think it’s faster to switch branches for the bug-fix than to reorder those commits later
It doesn’t disrupt my workflow to switch branches and it’s much faster than some ugly rebase
deleted by creator
When it’s right wing domestic terrorism
What is this turnout for? There aren’t general elections every two years.
deleted by creator