Discuss Home · Bootstrapped Podcast · Scribbleton Personal Wiki · HelpSpot Customer Service Software · Thermostat NPS

Do we have time to learn new technologies or languages?


#1

I’ve been a bootstrapper for 4 years now, more or less full-time.

So far, I’ve used C# for everything - for the main product (Desktop software), for tools, and for a small web app.

I’m very familiar with it, I have my own libraries, and I’m very quick in C#.

Now I’m developing my second product, a SaaS app. I’m on the fence which technology to pick.
On one hand, I know I’ll launch sooner if I continue using C#.
On the other hand, I’m feeling that in order to progress as a software developer, I really should try out new technologies.

Any thoughts on that?
Do we, as fulltime bootstrappers, have time to learn new technologies?
Is it wise to start a commercial project in a new language you have no experience in?
Will it hold back my progress as a developer if I do all my projects on the same technology stack?


#2

I thought you’re decided to progress as a bootstrapper?

Learning new fads that are not useful in your business is a waste of time. You may convince yourself that learning this or that new technology will help you down the road, but it unlikely will happen.


#3

You could learn new technologies in your “free” time and apply the learning back into your business and you’d be no worse off.

Personally, I don’t want to try new technology in my business’s code. I want it to be reliable, and I want to be able to reliably fix it when bad things happen. New technology is for play time and one-offs.


#4

Learning/using a new technology for a new product isn’t necessarily a bad thing. Just depends on what your expectations are. If you’re not driven on a fast timeline to launch date, then it certainly is possible. However, I would not let this decision ride based solely on the NEED to learn other technologies.

I think it is beneficial for a developer to understand some basics of other technologies. For example, I’ve tinkered with angularJs a bit, just to see what it can do. I’ve chosen not to use it in my web app because 1) I’m not comfortable with it and 2) it is still highly evolving as a language. But maybe I’ll use it as it matures and as I get more comfortable with it. Continue to learn new technologies as time permits, and use them as you see fit.

With your C# experience, if you simply continue to develop that experience, I don’t see you becoming obsolete anytime soon. .NET development has established itself and continues to grow. As you move toward developing SAAS apps, you’ll certainly get familiar with other languages (CSS, javascript, etc) as well as new development methodologies that you may not have experienced in your desktop app (i.e. MVC).

Good luck and don’t be afraid to learn something new! Just use it wisely. :smile:


#5

I would stick with the language/tech I know. But maybe have side projects using a new tech stack.
This way you get to try out something new and develop your skills, but have your important business code in something your comfortable in case you need to move fast (not have to learn how to something new).

That said, I think I would learn the new stuff faster if I went all in.


#6

I share @jasonforrest 's perspective on this. I consider new technologies & platforms a risk to the core business, so I largely avoid them or try it out on low-risk, peripheral stuff. If it’s valuable to your overall happiness, go for it – but treat it like a hobby. (I play upright bass, and take a little time each week to study jazz. It obviously doesn’t help the business, but it’s part of my “balanced life” scheme, and makes the whole picture sustainable.)


#7

Good point! If you have a desire to learn something, go for a real-world things. I started my boxing classes last month, and I tell you this thing is “stronger than Goethe’s Faust” ©!


#8

I’m in the same boat with C# - I love it, and I’m very productive using combination of Visual Studio and Resharper. Since .Net is now open source, and with existing support for mobile platforms by Xamarin - it can get you pretty far whatever you want to do.

Concerning learning new stuff it’s inevitable even if you stick to C# and .Net. Since you’re moving to SAAS it will bring too much new stuff, especially on the front end, that choosing a new platform on the back end will inevitably slow you down in first few months.

On the other hand, if new platform looks sexy and exciting - it could motivate you and give additional push on psychological level. It could even have business sense regardless of theoretical productivity losses if in practice new and interesting things make you look forward to each day of work. After all, you don’t have a boss, it’s ok to change things for change sake if it makes you happy.


#9

I find the only way to learn a new technology is by using it in a real project. It can bite you sometimes and I suppose the way to avoid that is to create a prototype first. While I like learning new technologies, it has to be right for the project. I try to introduce only one new technology in a project so the learning curve isn’t overwhelming. When choosing technologies I tend to go for stuff that’s fairly mainstream in case the project gets bigger and I need to hire a developer.

Being able to choose frameworks/languages is one of the perks of doing your own thing.


#10

I don’t see how you have time not to. Since I started out way back when (VB6) I’ve had to learn VB.NET, c#, the full LAMP stack, and various Javascript libraries. I’m hardly an expert in any of them but productive enough to be useful. It’s easiest if you have a real project to work on where you can incorporate the learning experience. This year I’ve spent many hours working my way around WordPress (fun) and next I’m doing my best to pick up some new Javascript libraries to see how use them in my existing SAAS product.


#11

Are you building a product or are you playing with languages? It’s that simple.

Unless you’re considering to green field a project based on MS DOS and Turbo C 1.5 you shouldn’t switch tech just because “it’s new”. I’m not seeing C# and .NET going away in the next decades so stick with it and focus on business domain problems instead of fighting a new language and unknown frameworks.

You can always play with new tech in your free time though.


#12

For a SaaS platform you need to know frontend. In terms of usability and UX, the expectations people have for web applications today is on par with native apps. Thus whatever SaaS you have it will likely have an admin frontend such that the user can interface with the platform and access analytics, at minimum.

To achieve a native-like experience you need JavaScript. React, Angular, Ember, etc. will all do for building the front-end.

You gotta keep learning so you can deliver solutions that best competitors, or at worst match them. Some technologies don’t see that much of a change. You can write your backend in C++ if you’d like. Others do change, like the front-end.