I want to pause here and clarify: JHipster and Angular are not bad platforms. Ultimately, I decided to re-write most of it using frameworks that were more familiar to me. And after a few months, it became clear to me that my choice of technologies was becoming a hindrance to making the application better. I was learning some of the limitations that now felt like major roadblocks. I spent a lot of time looking up how to do new things that weren’t part of the boilerplate setup. However, the more I tried to improve it, the harder things got. And so I did what any other developer who is already stretched thin and trying to balance a full time job and a family and hobby projects would do: I spent my nights, weekends, and every free moment I had working on it. Knowing I had created something useful for a large audience was really satisfying. Other people started using the application. But a funny thing happened soon after I launched. Within a few weeks I had a functioning application that met all my needs. It’s been around for years, is very well documented, and has great community support. I settled on JHipster, a development platform for building web applications using modern technology: Angular, React or Vue for the client side, and Spring plus Gradle or Maven for the server side. The main goal was to get it working fast. My project was meant to be a hobby application that would only be used by me and a few friends, so I didn’t spend too much time thinking about a long term roadmap or requirements. But lately I have found myself wanting to branch out, and dabbling more in HTML and UI development.Ī couple of years ago, this natural curiosity led me to start a new side project. The so-called back-end of the software stack. As a Java developer, I have spent most of my professional life working on the parts of software systems that most people don’t see.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |