I've just finished my software developer apprenticeship and have about a year of professional experience under my belt. During my training, I primarily worked with C#, which I really focused on, but I've since dabbled in Flutter for app development, C++, Go, and a little Rust. While I've learned a lot about understanding different languages, I still struggle with deciding which language or framework to use for a project.
For instance, at my side job, I had to choose between Flutter and MAUI, and I went with Flutter because it allowed for quicker development and enhanced user experience, while I used Blazor for a website component. However, for my personal projects, I often find myself making poor decisions, like trying to build an API for an old Raspberry Pi using a trendy language. I really want to respect my time and make better choices. So, how do you determine which programming language or framework is the best fit for a project? What steps do you take to research this?
4 Answers
I primarily work with C#. So anytime I do a personal project, if it can be done in C#, that's usually the way I go. It’s familiar and gets the job done, right?
I'd say it's all about mastering one language and its ecosystem instead of spreading yourself thin. For example, if you're learning Python, dive into libraries like Tkinter, Django, or Flask. Don’t get caught up trying to learn every language out there; just focus on one and its related tools.
Definitely agree! Also, if you ever think about back-end services, don't forget FastAPI. It's becoming pretty popular for creating back-end APIs for mobile or single-page applications.
Honestly, I think you just need to pick one and roll with it. If it’s a personal project, use whatever method suits you best—if you want to learn something new, go for that! But if you're in a tight spot and need to finish something quickly, stick to what you already know. Sometimes the choices are pretty clear based on what you need—like using a robust backend language if performance is crucial.
After over a decade in tech, here’s my advice: For work projects, keep it straightforward. 1) Use what your team knows. 2) Consider hiring potential. 3) Look for long-term support. 4) Go for the simplest tool that meets your needs. I've seen projects tank because someone picked a complex language when a simpler solution would have sufficed.
For personal projects, think about your goals:
- If you want to learn, push yourself with something new.
- If you just want to get it done and shipped, use what you’re best at.
- To build a portfolio, pick languages that are in demand.
- And for fun? Just do what excites you!
My actual process involves defining constraints, checking job trends, Googling for real-world usage, and prototyping quickly. I’ve made that mistake of choosing a trendy language for projects where it wasn’t suitable, too! So trust your gut like you did with Flutter over MAUI.
I totally get that. I mainly use Java for work, but if I need to build something quickly outside of work, I'll often stick to C++ just because I know it well.