arunkumarl

I used to be an accountant in practice (equivalent of a CPA in India). Became a web developer by accident 2 years ago. Currently building a web application for the accounting industry that automates a lot of reporting tasks. So far it has gone well and I feel like I should be adding more people to my team to handle the increasing workload.

My stack is Rails/Postgres on Heroku at the moment. And some C# for some small windows tools we have built. I did a lot of googling on this subject and made a to-do list of things to prepare for this. - I found the Joel test which I will soon be passing.

I was hoping you guys could help me with some advice based on your personal experiences regarding: 1. What I should expect/prepare for 2. What questions should I be asking, that I am probably not. 3. Anything else that you think I should do.

I think what I am asking boils down to: "What are some things you wish you knew before you set up your engineering org?"

Thanks in advance.

A startup has a lot of decisions to make. Sometimes they can be tough to keep track of. Sometimes you wonder what you had previously decided about a given question and why. What are some of your suggestions for keeping track of team decisions? Are there apps to do this?

Knowing what you know, what will you do differently in your next product?

I think I will release early and manually recruit customers which I learnt the hard way.

Assuming you could write in any language other than JS for the browser, what language would you write in?