5 ms·
Sure, because 'you' aren't really a generalist. You are just a 'junior' developer that dabbles a bit in things. Don't get me wrong, someone like that has a pla
by blablablame 11y ago
Sure, because 'you' aren't really a generalist. You are just a 'junior' developer that dabbles a bit in things.
Don't get me wrong, someone like that has a place in some companies, but it is the difference between being payed 20 bucks an hours vs 200.
All the stuff I've mentioned before, I've done. I've worked in more industries than some have jobs. Right now, I can pick and choose what I do and get payed way too much for it. I didn't specialise (but I admit there is a place for that) but I have enough breadth that I can go from games, to AI, to 'deep learning', to crud, to mobile apps without an issue, and with all that baggage, I can ask for the big money as well. Let me just put a quick list of language where I've worked professionally charging those values:
- C
- C++
- Ruby
- Objective C/Swift
- Haskell
- F#
- Java/Kotlin
- Python
- C# (and Visual Basic, both .net and not)
- Delphi
- Borland Builder C++ (I don't even remember the right name)
This isn't a brag, seriously, just to point out that what a lot of people consider to be generalist aren't even scratching the surface of it.
- hanniabu 11y agoFair enough, that is pretty impressive. That's how I want to be. I hate being restricted to the language I know. It's nice to be able to pick up whatever framework/language that would be best for the job at hand. For me, idk what it is, but I also hit metal blocks when learning because I don't know how everything connects in the bigger picture just yet. Learning other languages, even if it's only knowing the basics and syntax, tends to help me it greatly with understand and making everything click. Usually when that happens I see a huge busy of understanding as well until my next road block which will usually last a while again. I can definitely see myself being in your position in the future (only started programming a year ago). Curious, do you have a background in something else besides/before programming?
- blablablame 11y agoNot really. When I was 4-5, my father took me to the arcades. Playing games there I had the lightbulb moment where I said 'That is what I want to do'. At 11 I was reading the Turbo Pascal manual trying to figure out how things work (mind you, this was before Internet access was a thing and before I was playing with the ZX spectrum playground). From there to C/C++ (DJGPP anyone?) to VB when at 16 I started doing payed work. At 19 I wrote a book on C++ and games and from then on, games, insurance, banking, industrial processes, etc etc. I did 1 year at university before I realised I preferred to be working. This didn't mean I didn't learn (I have a library that I'm sure some small schools envy). But you know what my turning point in my career was?? Boxing! Boxing was what gave me the discipline and hardwork to go through whatever it was thrown at me. Not sure if that is relevant to 'background in something else' but hardwork, dedication is 80% of the path, the 20% left, well... that is just luck (this coming from someone that isn't really 'smart' by usual standard) ps: I'm slightly tipsy so I apologise in advance for the lack of coherence.
- hanniabu 11y agoGahhh, can't wish enough that I got into this earlier. Graduated with a degree in mechanical engineering, worked for a year at a startup, took a year off to take the plunge into programming. Getting my feet wet with webdev right now. Plan is to get into C++ as it seems that's where the industry is heading with VR, AR, robotics, and web assembly. I was actually wondering if you did something prior to programming thinking that it may have influenced your wife range of fields. I think coming from mech eng is probably the reason why I feel the need to understand how the whole system works.