They said they only pick bugs that take 2 days to fix.

Places where you can move fast and actually do things are actually far better places to work for. I mean the ones were you can show up, do 5 hours of really good work, and then slack off/leave a little early.

▲

kykat 14 hours ago | parent | next [-]

Too bad many places care more about how long you stay warming the seat than how useful the work done actually is.

▲

ls-a 13 hours ago | parent | prev [-]

Nothing takes 2 days to fix. Those are definitely not bugs, like someone else mentioned

▲

asdfman123 28 minutes ago | parent | next [-]

I'm sure it has a lot to do with the complexity of the environment but I've fixed three bugs in a day easily.

Our software isn't serving millions of people though, it's a cli tool with a few hundred end users.

▲

toast0 13 hours ago | parent | prev [-]

You haven't seen the same kind of bugs I have, I guess.

This kind of thing takes more than 2 days to fix, unless you're really good.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637

Or this one

https://security.stackexchange.com/questions/104845/dhe-rsa-...

I can find more of these that I've run into if I look. I've had tricky bugs in my team's code too, but those don't result in public artifacts, and I'm responsible for all the code that runs on my server, regardless of who wrote it... And I also can't crash client code, regardless of who wrote it, even if my code just follows the RFC.

▲

ls-a 12 hours ago | parent [-]

That's what I'm saying. Nothing takes 2 days to fix meaning it takes more time

▲

toast0 11 hours ago | parent [-]

Oh. Well, I've done easy fixes too. There's plenty of things that just need a couple minutes, like a copy error somewhere.

Or just an hour or two. I can't find it anymore, but I've run into libraries where simple things with months didn't work, because like May only has three letters or July and June both start with Ju. That can turn into a big deal, but often it's easy, once someone notices it.

	▲	ls-a 6 hours ago \| parent [-]
		If your goal is to fill green github squares then fine