|
|
|
|
|
|
by oblib
1262 days ago
|
|
|
You're probably right. I never went to college but I started learning how to code in my late 20s because I could finally afford a used computer by then (late 1980s). It tore me up to go to friends homes and see a Mac or Commodore 64 sitting on a desk collecting dust. When I got my first used computer in the early 90s, (a Commodore 64) I dove into learning how to program. Back then I didn't know anyone who knew how code. I started buying books in the 90s and still have most of them. So I think you've got a great point about "if tinkering doesn't come naturally". Coding something is often times designing the logic to do something you can't copy and past a solution for. It's that kind of challenge that makes it interesting (and frustrating), but if that doesn't intrigue and inspire you than it might not be a good career choice. |
|
|
Personally what I like is solving business problems and delivering excellent solutions to happy customers. Coding is a means to an end for me. I originally learned to code as a teenager in order to build websites in an attempt to make money from them (with some success here and there). It wasn't because coding itself was particularly intriguing or fun, but it was a pathway to building a product that could generate income. I didn't hate it either, I found/find it somewhat fun, but there are many more things I would prefer to spend time on if my goal is pure recreation. The idea that I could sit at home with a keyboard and generate wealth for myself was what encouraged me to pursue this career.
Right now, if I didn't have customers or start ups to launch I would spend precisely zero time "tinkering" about with code for personal fun, the fun part for me is designing, delivering and selling the solution. I'm not obsessed with coding for the sake of the technology like a lot of people are, yet I love my "job" and I'm highly motivated and effective at what I do.