Daily Prompt: 2024-05-29
What is something that you think is a 'solved problem' that your field just hasn't caught onto yet?
Replies(2)
I feel like programmers are likely to just create something new when there are high quality and supported open source tools for things. I will admit that it is often difficult to know if a piece of technology is flexible enough to handle your use case (and future use cases) but there are definitely times where you shouldn't have to re-write something and you can save yourself a lot of time.
I also feel like never experiencing other people's software is limiting for your growth. Seeing how other projects solve similar goals is an important way to learn. And not just at the code level... There's different ways to document, market and explain concepts that are very important to understand.
I sometimes see engineers who have created entirely strange terminology for concepts that are widely used in the industry and have a standard set of vocabulary. To be properly understood, I think it's important to at least know the words and concepts that are generally used.
@sudorandom Step 0 for me has always been "Has this been done before?" If I dive in and find I need something custom, then so be it, but that research usually informs me of problems or caveats I wasn't even aware of.