spread_thin

4 ms·

1. 1.▲
   by spread_thin 16y ago

   I wish that were an option. The mentality here is, "If it ain't (too) broke, don't fix it." Which means people actually get in trouble for doing refactor work that doesn't add new functionality. But you're right--compared to what I could be
2. 2.▲
   by spread_thin 16y ago

   i think you're right in the context of learning for the sake of learning, but to learn in order it enough for it to count as an employable skill... not sure. i'd love if two hours/day for six months would get me up to speed.
3. 3.▲
   by spread_thin 16y ago

   1. completely agree 2. yep. your last comment is a pretty succinct description of my goal. i guess what i should be asking is, what's the best way to make that transition? i kind of fell into .NET development--no real passion there and it's
4. 4.▲
   by spread_thin 16y ago

   Do you do contract work? Or has it been run-of-the-mill full-time employment? I agree about not living based on what other people think--I guess it's the typical decision between "take a risk" and "comfortable misery"... although put that w
5. 5.▲
   by spread_thin 16y ago

   Yeah. The wrinkle is I've only been at my current gig for five months... the pragmatic side of me doesn't want to have two back-to-back five month stints on my resume. I left my last job after five months because a former coworker presented
6. 6.▲
   Ask HN: Career advice for a torn developer

   5 points by spread_thin 16y ago|13 comments