I'd say "use it as your database if you know your access patterns make it suitable/well-suited for its use as your database". Even then it will probably not be your only database — if it's part of your MSA/SOA.
I would not build in DynamoDB if you suspect your access patterns will drastically change over the lifetime of the application (or if you intend to, e.g., plan to build a data warehouse or something crazy with it).
You don't need to store the timezone anywhere, you just need to know the current local timezone when the stored UTC time is used. And that's why storing in UTC is better, because it only takes one conversion to represent it in some arbitrary local time.
If you stored it as a local time (ie: with TZ), then if it's ever later translated to a different local time (different TZ), you're now dealing with all the quirks of 2 different timezones. It's great way to be off by some multiple of 15 minutes, or even a day or two!
Heck, even if it's the same exact location, storing in local time can still require conversion if that location uses daylight savings! You're never safe from needing to adapt to timezones, so storing datetimes in the most universal format is pretty much always the best thing to do.
It would be less weird if there was any feasible strategy for releasing an app that Apple doesn't take a cut from. Unless you pay for 0 apps, you are supporting Apple with recurring service revenue.
I posted (about three years ago now) in a Who Wants to be Hired thread. Admittedly, it was kind of on a whim, since I’d just left a job in operations after feeling burnt out, and thought I might dip my toes in the water of software dev full-time. I was contacted by four or five companies, I interviewed with three, and landed a gig with the company I’m still with currently.
For what was a two sentence post I made thinking it wouldn’t really amount to anything, it turned out to be one of the best moves I’ve made. (For both parties, I’d say.)
You have a point, but that's also where you come off as indecisive. Since the question was explicitly about that that, presenting 3 options, one of which you have reasons against, when we're all busy and meeting time is constrained, is, in the abstract, a waste of everybody's time. If later on, someone comes up with objections; options A won't work because problem X, option B has issues Y and Z, then sure, bring up option C, which addresses X and Y but has other issues, for further debate, but unless that happens, that's time wasted. imo.
This does hinge on you knowing what you're talking about, and rejecting option C for unbiased reasonable logical reasons you're sure about.
If you’re referring to game dev specifically, there have been (and continue to be) concerns around the weight of C++ exception handling, which is deeply-embedded in the STL. This proliferated in libraries like the EASTL. C++ itself however is intended to have as many zero-cost abstractions as possible/reasonable.
The cost of exception handling is less of a concern these days though.
It seems a bit naive, given his list of business successes, to think that the positive things that happen at these companies under his leadership only happen because his employees overcame him as the obstacle to success.
I can understand not liking his politics or what have you, but logically speaking, what you’re suggesting doesn’t make any sense.
I would not build in DynamoDB if you suspect your access patterns will drastically change over the lifetime of the application (or if you intend to, e.g., plan to build a data warehouse or something crazy with it).
reply