I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
Thanks for you comments, leob. Based on 4 you might benefit from reading the Effective Executive. It's my favorite business book of all time. I wrote a series of blog posts on applying its concepts to programming, which might interest you.
Great writeup, but I wonder if this also solves my problem (well I think it's one of my problems) of not only managing my time effectively but also to decide WHAT to spend my time on. There's too much stuff and only 24 hours in a day (and then again you shouldn't be working 24 hours in a day even when you could).
Especially in the software development world there are so many trends, fads, new things all the time, you can spend 24x7 just following all the news about new tech. You need to be able to decide "will this benefit my bottom line" and you need to make choices or choose your 'niche'.
Or should you? You could also be successful as a "generalist" but I'm starting to believe that presenting yourself as a specialist might ultimately "sell" better. Everybody and their brother sells themselves as a "full stack developer", it's lost all meaning. I know I have a broad skillset but telling a customer "I'm quite good at anything you throw at me" doesn't quite cut it, it's too vague.
So this is actually more about about strategy (making strategic choices) than about efficiency (working efficiently once the choices are made).
Bane of the modern 'homo sapience', too many options for anything you can think of ... choices, choices, choices.
But ultimately you should not think TOO much about choices because it leads to analysis paralysis. The best advice I've read about this said you need to build and contribute stuff (attitude of "make" and "give back") - doesn't really matter what you do as long as you do something (productive).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for you comments, leob. Based on 4 you might benefit from reading the Effective Executive. It's my favorite business book of all time. I wrote a series of blog posts on applying its concepts to programming, which might interest you.
Hey that's cool, I'll check it out ... thanks!
P.S. 5 minutes later, I've checked it out ... smallbusinessprogramming.com/what-...
Great writeup, but I wonder if this also solves my problem (well I think it's one of my problems) of not only managing my time effectively but also to decide WHAT to spend my time on. There's too much stuff and only 24 hours in a day (and then again you shouldn't be working 24 hours in a day even when you could).
Especially in the software development world there are so many trends, fads, new things all the time, you can spend 24x7 just following all the news about new tech. You need to be able to decide "will this benefit my bottom line" and you need to make choices or choose your 'niche'.
Or should you? You could also be successful as a "generalist" but I'm starting to believe that presenting yourself as a specialist might ultimately "sell" better. Everybody and their brother sells themselves as a "full stack developer", it's lost all meaning. I know I have a broad skillset but telling a customer "I'm quite good at anything you throw at me" doesn't quite cut it, it's too vague.
So this is actually more about about strategy (making strategic choices) than about efficiency (working efficiently once the choices are made).
Bane of the modern 'homo sapience', too many options for anything you can think of ... choices, choices, choices.
But ultimately you should not think TOO much about choices because it leads to analysis paralysis. The best advice I've read about this said you need to build and contribute stuff (attitude of "make" and "give back") - doesn't really matter what you do as long as you do something (productive).