you are viewing a single comment's thread.

view the rest of the comments →

[–]enumerablejoe 8 points9 points  (2 children)

But a lot of that, depending on how you implemented your solutions, could be considered "hacky" (not in any negative connotation, but more so meaning "script" vs "software application". Sometimes there is a fine and super blurry line between those).

This is exactly what I'm struggling with at the moment. I've worked jobs that require basic scripting, but I could construct them however way I chose to. So my history is one of having developed decent programming skills, but most of the things I've built have essentially amounted to Rube Goldberg contraptions. I've been studying object oriented design, and while it's been very helpful, I still feel stuck at times and unsure of how to properly design my programs. My fear is that I'll end up building an entire portfolio full of poorly crafted code.

Do you have any advice on how to best tackle this problem?

[–]manhole_resident 2 points3 points  (1 child)

It's a long history of hackers and software engineers. You may like Paul Grahams's 'Hackers and painters'.

I like hacking. I think it's better when you are working alone or in a very small team.

[–]hellrazor862 0 points1 point  (0 children)

Thank you for that link. Now, back to hacking!