At the end of last month I turned 35 years old and I realised I have been a developer for about ten years. I began coding when I was 21 and I got m...
For further actions, you may consider blocking this person and/or reporting abuse
Right now, I'm working on 6 android application at a time. Because it's a start-up, my boss would often, no always tell me the consequences if I don't finish it soon. He's a great but breathing down my neck everytime has greatly decreased my performance.
I need my space to work on the things my way. Running behind deadlines like a mad man won't be of any help to me or the company.
I greatly appreciate the parts about stress and contract. I have decided I be straight forward and tell him my issues.
There is no point piling too much work on someone, it never ends well. I hope you sort your situation out. Good luck.
I have also a Degree un History and I've started a new career as Dev 6 months ago at 30. I work in a startup with Laravel, sometimes it's very hard, you have to learn everything at the same time and quickly, but I don't give up and hope I can improve my skills by the time.
Thanks for sharing your experience ! It's very useful and inspiring for beginners like me
Good luck with your new career.
To be honest, I was a little skeptical of this article when you started. Thoughts like "SQL isn't real coding" unfairly ran through my head.
But you won me over with the bit about ignorance, your focus on TDD and quality, using the Socratic method, working with QA. These are the things I also believe/recommend.
Where you helped me is in the part about how being a contractor helps with companies who don't want to fix problems.
I'm also really happy you included the bit about alcohol.
Thanks for writing this; I hope many more people get to read it.
Apologies if you thought I meant "SQL isn't real coding", I don't think that at all. I'm glad you enjoyed the rest of it though.
I've been writing code for over 10 years now, and although I've been doing more management lately, at my peak I was able to write 500+ lines of well-performing code a day. Here are the principles that helped me with this:
- Don't over-generalize
- Don't optimize your code in advance
- Name and group everything that happens correctly
- Don't mix algorithms and other technologically complex pieces of code with business logic
- Don't use any advanced features of any language
- It is worth throwing all OOP out of your head
- Use as many asserts, logs and other methods to catch unplanned system state as early as possible
- Every extra line of code is evil
Every extra line of code is evil:) Wherever possible, you should not use someone else's code that you have not read and understoodHere I placed just names of my mistakes, but if you are interested here the full version with each point explanations
Very nice article. Thank you for sharing a bit of your experience.
Glad it was useful.