529 karma · joined March 16, 2012
The three key outcomes I observed from the relentless A/B testing were UI antipatterns, team burnout, and a well-attended conference talk about "how we ran 105 A/B tests in a year, and what we learned".
If you're pivoting so hard that your SQL schema breaks, how is a schemaless system going to help you? You'll still have to either throw out your old data (easy in both cases) or figure out a way to map old records onto new semantics (hard in both cases).
I agree with GP that this is a central problem to solve, not something to figure out _after_ you write software. Build your house on stone.
From elsewhere in thread, heavily snipped:
games like that aren’t fun. It’s been tried. [...] hopping online to go do your second job [...] implies work [...] no one wants to do that work
I wouldn't want to do data entry in an FPS game, no, but people love "bakery simulator" type resource management games. It would be cool to link my grocery-line-time-waster score into my overworld bank account, enabling me to shop around for gear in stores set up (but not manually run) by other players, to use in the FPS portion of the game where I steal morsels from the full-sized humans (or am I getting my threads confused?).> between "No, I don't understand you." and "I understand you perfectly well, but [nothing in my nature compels me to care]".
This is where he and I are for lots of other stuff, and I also love him for it.
Great info thanks.
Probably not coincidentally, this was the only place I've worked where KPIs were truly a useful way of framing our place within the organization.
https://books.google.com/ngrams/graph?content=home+in%2C+hon...
I can't imagine having to see them all at once. Realistically, I'm only actually thinking about 1 or 2 of them at a time. If I need to check documentation, I'm no longer thinking about my build output. Slack, email, and calendar are disconnected from development tools. And if I need to do a quick context shift, I can switch over instantly.
Hear hear! OP, if you go this route, treat your implementation as a practice run, and write out exactly how it works in pseudocode.
My 2 cents:
I think that hiring a (good) professional for a rework/reimplementation would be productive, but it would certainly run the risk of exposing errors in your work. If that's desirable or not depends on your timeline to publish, I guess.
My personal idea of hell is cold-calling randos all day, trying to get them to pay me for half-finished software.
Appropriate that _this_ comment is buried who-knows-where in slashdot's archives.
https://www.amazon.com/Ashley-Book-Knots-Clifford-W/dp/03850...
I've been at organizations where local development required connecting to a MSSQL instance in a server closet at HQ; This is unacceptable, and devs will constantly be at war with each other.
Mocking your analytics provider (or whatever) seems much less problematic to me.
There is an excellent episode of The Anthropocene Reviewed[0] that tells his story well.
[0] https://www.wnycstudios.org/podcasts/anthropocene-reviewed/e...