Which do you think is ?
โฆ
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
Completely spec out a project - instead there should be stages where you fill in the blanks ( that you left vague on purpose ) based on what you learnt up until that stage.
I assume this is not original at all at this point - but (extreme) DRY is not a good practice. My experience is that a bit of copying yourself and your colleagues in the code base often make maintenance of the code base easier.
Getters and setters for everything. Certainly, if you want an object to be doing more than just getting and setting a value right now, get them in there!
Planning to add functionality later without breaking code? Stop it! That should break code! If I'm consuming a library and have been using this setter method for 2 years, I don't want it to suddenly introduce brand new validation, caching, or logging behavior!
Bring back timestamps?
No, I like the cleanliness of the design and the concept37%
Yes, but limited to the postโs page and for historical posts44%
Yes, everywhere, I canโt live without them19%
โฆ
No
Finally some breathing room for the brain ;)
Another use-case for timestamps - showing how often someone posts, and how recently they were active. I want to be able to send my friends a link to my user page and say "follow me here for random thoughts". Odds are they're not going to create an account, but they might bookmark it and check for updates from time to time. Timestamps will tell them whether it's worthwhile to do this.
Please no.
This place is special as it is.
Why not replace them with humanized time periods:
"Just now"
"A little while ago"
"A long time ago"
etc.
Yes! I made a similar suggestion on HN, though like your labels better. I was thinking a bit more on it that after "just now" and a hypothetical "new" that the timestamp could disappear so long as there has been a response within X amount of time, for example, after 2 months. After this time period it could start saying things like, "a while ago," "quite a while ago," and "a long time ago" based on (for example) 1 years ago, 2 years ago, > 2 years ago.