Posts by Sebastian Hädrich
View profileFeature Request: Make posts either searchable by tag or display posts on the tag page
Currently, when clicking on a tag in a post and no user with this tag is endorsed yet, the tag page is entirely empty, despite this tag potentially being used in multiple posts.
There’s also some precedence for letting people use the search to search for posts with this tag. Why is tag: a people-only filter?
github.com/wintermeyer/vutuv/…
️✅ Edit: Implemented in v7.114.0 (#965) 🚀
Feature Request: Filter posts by type
If one wants to know what kind of content a user posts, they might go to their profile but find their posts cluttered with reposts and not a single own post. They might then go to the “All posts” sub page but even there, they might have to scroll for quite a while. This could be made easier.
github.com/wintermeyer/vutuv/…
️✅ Edit: Implemented in v7.116.0 (#971) 🚀
Feature Request: Revamp search page
Having a search feature is great. But vutuv has grown rapidly and beautifully since it saw the light of day. Search needs to keep up with that.
Feature Request: Follow tags
Like the Fediverse, vutuv could allow its users to follow tags. Unlike adding them to your profile, they could allow for the feed and the recommendations (should this be controllable?) to show posts/people with said tag.
It should go without saying, but apparently, there are still companies who make the mistake to measure and communicate time to first deployment to production as the primary metric to tell how long a feature takes. But this is misleading: A feature isn’t actually finished until the last bug (sure, there will be more in the future, but “last” as in “it can be used without bugs for now as promised to the customer”) is fixed. So, trying to deploy as fast as possible might make marketing happy, but in the long run, it will hurt you (and probably your reputation as a company).
That being said, there sure are some aspects of #software_development which are in fact optional and #software_testing can cost more time than it saves—when it is done wrong. However, generally speaking, testing, be it #TDD, #BDD, #ATDD, or other approaches, should not be optional. Same goes for #code_quality. Sure, this needs to be done at a reasonable level, perfection doesn’t need to be the goal, but “no matter how bad the code is as long as it is written fast” shouldn’t be it either.
