hoboon

8 ms·

31.
by hoboon 12y ago
> Alternatively you can always decide to work on something outside of work that can help sharpen your skills. I do, a lot. It's all garbage, though, and no one really looks at it. Don't get trapped into work you don't wan
32.
by hoboon 12y ago
> and there is work for you, engineering work, that is a valuable contribution to a company. This is a pretty good time to be in tech, and there are plenty of positions. This just drives home how much of a loser I really am. I live in SF
33.
by hoboon 12y ago
> Reading through your responses, I'm not sure I can give you great advice because the two large software companies I've worked at welcomed moves out of what you call sustaining engineering I've heard this is what they do
34.
by hoboon 12y ago
Thanks for your advice. I do code on the side. I have a github and some OSS patches I've put in. Feedback from interviewers regarding it is that it is all amateurish and not so great/clean/beautiful. Usually people don't
35.
by hoboon 12y ago
I was wrong, then. I apologize. But I felt like you were talking down to me -- like you don't trust me. Yes, I understand solving problems is part of the job. Every software engineer has had that told to them forever, it seems. It&#x27
36.
by hoboon 12y ago
> You're just going to have to really look for them. yes, that's true. But how long? Especially compared to the brilliant people fresh from school I'm competing against. Thanks for the advice, though. and I wish i had talk
37.
by hoboon 12y ago
> have u tried rewriting most critical parts to do things in different ways? Also keep in mind that these critical paths of the code produce more money for the company in a minute -- globally -- than I will produce in my entire life. You
38.
by hoboon 12y ago
> Embrace the suck of your underachievement and get busy learning to master your craft. That's what I'm asking. How do people get good at this? I figure it's practice and acting on things I can control but I don't kno
39.
by hoboon 12y ago
> Apply around to a lot of places, and look for somewhere that values the skills you have but also will allow you to develop into the longer-term role you want to hold. Applying for jobs is what I've been doing. Why would you assume
40.
by hoboon 12y ago
Yes, I figure out how dots are connected. In sustaining engineering, if it's not assigned to you, you can't really do it. I'd thought about doing what you suggested many times, but throughput is the #1 thing about bug fixing.
41.
by hoboon 12y ago
> Your #2 problem is that you think writing code is the most important skill of a programmer. It's not. Learning is. Are you a fast learner? If so, there are hundreds of companies that need you. I'm told in my interviews that I
42.
Ask HN: Career trajectory? I'm terrible
14 points by hoboon 12y ago|39 comments
43.
by hoboon 12y ago
I wonder if they're going to do the same for the lab manual? I have a copy of the 2nd addition and there are instructions to mail a physical paper letter to addresses for parts.
44.
by hoboon 12y ago
I'm at least a little excited to see this. I've been reading about home automation for decades in the likes of Popular Science , and now, to perhaps see it really happen, finally. It makes me feel old, feel young.
45.
Short tutorial on Bag of words for Naive Bayes(data-science.tips)
1 points by hoboon 12y ago|0 comments
46.
Logistic Regression, with an OCR trick to boot(data-science.tips)
2 points by hoboon 12y ago|0 comments
47.
by hoboon 12y ago
congrats! :D
48.
My braindump on Bayes Networks(data-science.tips)
3 points by hoboon 12y ago|0 comments
49.
In which I try to learn about linear regression(data-science.tips)
1 points by hoboon 12y ago|0 comments
50.
by hoboon 12y ago
I once heard about a system based around a game: Where Are Your Keys? ( http://www.whereareyourkeys.org/ )