Old and boring is still sometimes the best.
It's not so much old vs new, or cool vs boring, but rather the thing you are most experienced with. If the goal is to just build the damn thing, go with a stack you would be most productive in.
Note: I have some hobby projects with minimal progress, where I ignore the golden rule and try new stuff all the time :)
I reviewed other options, including technologies that I was more familiar with, but the risk of slower development while I came up to speed was outweighed by the increase in speed to market.
My point is that there are technologies that if you are using a technology that is a pain in the ass (Winforms) but that is all you know moving to a newer technology that has been designed to be easier to use can not only benefit what you are building but even save you time in the long run.
While this forum does have people from all over the world (I'm living in London), it also is a forum headquarted by a seed accelerator based in the US.
built on boring [...] Angular 1
This exactly. Customers do not care what the product was written in, as long as it solves their problem. I find this is a hard thing for programmers as we are generally curious and want to be learning. It is important to remember the goal. If the goal is the learn, then go learn. If it's to ship some software to start a business, then use the tools you know and ship something.
It's true that if the company really grows, scalability, code manageability for teams etc. might become an issue if your backend is very poorly engineered, but that's the exception to the rule. As long as it works, it's good enough to launch with.
I think concentrating on the main features and launch quickly is good. You can start getting feedback and doing what customers or potential ones want.
The nice thing about theorems is that even when they're old, they're still theorems.
But in the end it is not the notation that makes or break a theorem. However, a theorem may be more or less clear depending on the notation.
In this case some developers actual go further down the tool rabbit hole and start building tools that build tools..and they wonder why they fail.
I bet this is on the roadmap.
I'm sure we can get around them, but not in v1
That reminded me the article titled "How it feels to learn JavaScript in 2016" https://hackernoon.com/how-it-feels-to-learn-javascript-in-2... https://news.ycombinator.com/item?id=12628921
For example, my day job I work with Android all day long. But as a side project, I wanted to make a small mobile game as a invitation for my wedding. So I loaded up Phaser.io and wrote some really easy Javascript. I had a working, playable game that night. To be fair, it's a really great framework. But I think choosing a framework that fits your needs at hand is much more crucial than which language or database you use.
On the other hand, technologies like Elixir, Erlang, Elm, and Riak, for instance, are immensely enjoyable to me, so they keep my motivation alive. In my opinion, whatever makes you happy and motivated is the best.
When I started a new side project, I wanted to get an MVP out as quickly as possible. I opted for PHP/MySQL, and development time felt like lightning. It was so refreshing.
I plan on rebuilding the code base, now that the side project is making money, and perhaps I can use newer tech for that, but quite happy sticking with PHP for MVPs.
Personally I don't really enjoy the development work on the "for profit" projects I build. I love seeing a finished product, though. Use the sexy untested tech for a "fun project", not a commercial one.
Here's the thing, I'm guilty as charged. But, analyzing my own behavior, trying the sexiest (JS or otherwise) framework is just an excuse to play/learn it. My subconscious mind never had the intention of actually following through with a product...
I hope we can recognize (and avoid) the pattern in the future and use whatever we are more comfortable with to rush the product out of the door.
After a while with the chatbot hype, in comes this external contractor, and started dismissing people left and right that either did not code in javascript or wanted to use his simplistic challenge/response chatbot (we coded a decision tree based system). In any case, at that stage the startup was failing, I ended up leaving, kept working with same cooling in my own startup and have been happy ever since.
So for me, the moral of the story is, work for somebody that is focused on the product instead of trying to win a hipster contest. First time I saw that was when .NET was in beta mode and our tech lead decided to switch everything over to an undocumented/buggy system back then.
Its co-founder and lead engineer is/was very prolific in the ColdFusion community. https://www.bennadel.com/