I mean, if it’s **just ** a normal screen-sized website, that already makes it a lot easier. Not having to deal with responsiveness bullshit would make webdev a lot better experience. That is assuming “normal screen” means 1920*1080, or whatever is the median screen size.
It only needs to look good on whatever screen size the client’s CEO’s favorite administrative director uses, when she checks on it, on a Friday evening, seven weeks after delivery (but still well before I’ll ever see my $500.00…)
Sorry, why would you be “boned” if you have UTC time? Are you thinking of the case where the desired behavior is to preserve the local time, rather than the absolute time?
I think the comment is specifically talking about storing future times, and contemplating future changes to the local time zone offsets.
If I say that something is going to happen at noon local time on July 1, 2030 in New York, we know that is, under current rules, going to happen at 16:00 UTC. But what if the US changes its daylight savings rules between now and 2030? The canonical time for that event is noon local time, and the offset between local time and UTC can only certainly be determined with past events, so future events defined by local will necessarily have some uncertainty when it comes to UTC.
So many things would be fucked by a TZ change that it very rarely makes sense to consider it.
You’re making a calendar app? Fuck it…some folks are gonna get confused…solved by simply emailing your users and telling them to reschedule shit because there’s kind of a big event going on that everyone knows about and has been planning for for years. Hell in all liklihood this is probably easily solved by simply doing a mass migration of events scheduled before the TZ change.
You’re coding for nuclear weapons? Maybe consider it. But probably not.
That is to say: there are ways to solve problems without resorting to writing the most complicated bullshit code ever seen. Unless of course you work on my team - in which case you’d be right at home.
PO: Someone else figure out how to repeat what he did.
Second developer: Sorry, I tried to make sense of his rocket design but I can’t figure out how to make a copy that doesn’t explode before we even put the fuel in.
Tru dat. Agile product management is not the same as agile project management. Agile Project Management is about the ability to figure and changes things along the lines of the predetermined cost and time path (e.g. figuring out features required along the way), not about the agility to prolong/shorten product value proposition time to market.
As a dev, I think agile works best when there's an ongoing conversation with the users, and I usually have to fight with management to get to speak to those actual users.
If I included cussing in “[YTP] Intoducing Apple Pro”, then I wouldn’t have been able to show it in my self introduction presentation in a high school class. I can’t guarantee that cleanness wouldn’t have a similar benefit for this meme.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.