Perhaps you need to define an interface

Google is you friend

Esperanto

I used to do this kind of shit back in the 90s before undo was really a thing, but now, you get what you deserve if you don't save frequently

I once had someone apply for a job who had been teaching in college elsewhere in Europe, he was so bad it wasn't funny. It was for a front-end role, his JS was awful, HTML out of date and CSS was nearly nonexistent.

I was genuinely mad that he'd been teaching that level of shit

Notifications aren't able in iOS

I'm involved in recruiting people for my teams, and once had a recruitment agent say "if we throw enough at it, eventually something will stick". That was the last time I spoke to him, as I realised I was doing his job of filtering out candidates that clearly weren't right for the role

@tombatron you clearly work with better BAs than I do, they always want the moon on a stick as the first iteration

@tombatron you forgot the analytics

@p100sch, for us it was Yammer, which just shows how deep the problem was.

In my last company the product had to be "social" but no one could ever say what that meant

Indeed I did, I can do things either way.

Normally I jump in, then step back and plan, then code again.

Someone I respect always used to say "the more time you spend sharpening the knife the easier it cuts". Development is the same.