ilovepeppapig

"Agile" is only about software and it doesn't always work even for tiny projects. Apple's products are so much more than this. Distribution, marketing, manufacturing, support etc.

You can't delay a new iPhone release because it's imperfect. They make phones to make money, and they are very good at it.

I honestly can't see any reason to use it over Confluence. Apart from better emoji support

RIP git log

Thanks. Really fun to play

It will be much faster if you don't update the HEX values all the time (they are not that interesting anyway).

The worst way to explain something is to begin with "It's actually pretty simple."

It is rather stressful for the leaving coworker to answer these questions. Just put yourself in their shoes. He/she could be thinking "I don't wanna see these guys anymore", and you're asking at the same time about the reasons. To begin with, try to ask about their plans for the next several months, their future work etc. If they're super excited about it, maybe they just need another challenge. That's totally OK. Wish them the very best and be thankful for the work done together. If they say "oh I dunno, their MacBooks are slimmer", then probably the main reason lies within your company.

If the resignation caught you by surprise, it's unlikely he/she will tell you the real motivation. People often start the contemplation long before they decide to leave. IMO.

Interesting that buses are so "unfriendly". But it probably makes sense if most of the times they cruise with nearly no passengers.

Thanks for the info.

Flying is environmentally friendly? That's a bold statement

The worst production code I've seen (Java) included its own Object interface and a corresponding ObjectImpl (IIRC it was an abstract class).

I've installed LineageOS on my Xiaomi and it's great. Much faster, more stable and fewer bugs.

One of my colleagues once showed me millions of $$$ flowing through functions called `func1`, `func2` etc., both of them are over 1000 LoC. There are many SQL queries more than 100 lines long. Overall it's a huge application with extremely difficult use cases. And yes, there is not a single automated test scenario. But the company is more or less happy with this system and their manual testing. That said, it's a 20 year project and it has probably helped to earn some good money. So, if that project can be successful, any project can. There are bugs and it is has some serious issues, but it is possible to deliver something actually useful w/o tests.

I would assume, it's possible to go without automated testing when your business logic changes every now and then. Not that you necessarily should.

> There seems to exist a "hustle" mentality, where you need to ship at all costs

I'm still to see a developer with experience in the banking industry, who would praise its working conditions. "Low"-tier workers with 25-50% developer salary usually have to deal with even worse conditions.

Remember, working 60h+ a week can lead to unpleasant health problems, both physical and mental.

Try pressing your hand against a flat surface and then slowly applying enough force in the way parallel to the wall so the hand starts to slide. After some practice you will feel the point of losing traction. The concept is the same with tyres. F1 as of 2018 actually doesn't allow drivers to push 100% all the time, otherwise the tyres will overheat and the strategy is screwed.

Plus, 4 tyres may have different traction depending on car balance (braking, accelerating or cornering), downforce (nearly zero at 50km/h but at 300km/h F1 car is on rails, and different for the front and the rear), track specifics (for example, most clock-wise tracks put a lot of pressure on the front left tyre) and many little other things. It's really complicated.