Never work unpaid overtime. Go the contract route early. Learn Python and SQL.
Ask HN: What is your best advice for a junior software developer?
361–370 of 460 posts
Re: Ask HN: What is your best advice for a junior software developer?
#362Earlier quoted context omitted.
This is my experience with Clojure stack traces ~60-75% of the time. Perhaps it is a symptom of functional programming? A lot of function passing and anonymous functions make it difficult to generate a meaningful stack trace.
Clojure's stack traces are an issue with Clojure specifically, and how it's hosted on top of the JVM. A lot of the stack trace you get is actually implementation details of the Java objects making up the Clojure runtime. In effect, the program that you get stack traces of is the Clojure interpreter rather than your Clojure program which is running inside that interpreter.
I've heard similar things about Scala, though I haven't had a chance to confirm this for myself yet. Not 100% sure if this supports your hypothesis or not given that Scala is multiparadigm?
Re: Ask HN: What is your best advice for a junior software developer?
#363Earlier quoted context omitted.
> Read at least HackerNews and possibly some other tech news site regularly. And then make sure to not get too caught up in the hype for new stuff. Interesting because I advise the exact opposite: do not waste time reading HN, just find one thing that is interesting and master it. Then repeat. As much as I like HN there is a lot of noise here. Novice mind can easily fall into a trap looking for signal here.
I've gotten a lot of value from reading HN. I've also wasted a lot of time. It helps to develop a personal filter. Mine is * Avoid headlines that make me angry, unless the news is really important. The discussion is never worthwhile, don't even bother. * WSJ, Bloomberg, and WaPo won't let me read articles with w3m, so I skip the article. If the topic is tremendously interesting, I'll check the comments. * TED and nau…
> WSJ, Bloomberg, and WaPo won't let me read articles with w3m
w3m, nice! I tried lynx, w3m, eww (emacs) lately, and liked w3m the most, but found it terribly slow on many sites. In particular GitHub. Just measured 12 seconds for loading my Profile. lynx takes 5s. Opera takes 2s.
Do you have similar experiences?
Re: Ask HN: What is your best advice for a junior software developer?
#364Earlier quoted context omitted.
I've gotten a lot of value from reading HN. I've also wasted a lot of time. It helps to develop a personal filter. Mine is * Avoid headlines that make me angry, unless the news is really important. The discussion is never worthwhile, don't even bother. * WSJ, Bloomberg, and WaPo won't let me read articles with w3m, so I skip the article. If the topic is tremendously interesting, I'll check the comments. * TED and nau…
> WSJ, Bloomberg, and WaPo won't let me read articles with w3m w3m, nice! I tried lynx, w3m, eww (emacs) lately, and liked w3m the most, but found it terribly slow on many sites. In particular GitHub. Just measured 12 seconds for loading my Profile. lynx takes 5s. Opera takes 2s. Do you have similar experiences?
Yup, it's slow for me too. I like it anyway. I want to like links, which is way faster, but w3m is just so simple. If I had to guess, I'd say it's because w3m doesn't support gzip compression.
Re: Ask HN: What is your best advice for a junior software developer?
#365Earlier quoted context omitted.
This is my experience with Clojure stack traces ~60-75% of the time. Perhaps it is a symptom of functional programming? A lot of function passing and anonymous functions make it difficult to generate a meaningful stack trace.
Clojure's stack traces are an issue with Clojure specifically, and how it's hosted on top of the JVM. A lot of the stack trace you get is actually implementation details of the Java objects making up the Clojure runtime. In effect, the program that you get stack traces of is the Clojure interpreter rather than your Clojure program which is running inside that interpreter.
Why do they do this, though? Shouldn't they have realized from the start that such messages are not helpful, and should have given messages related to your Clojure program? (Or is there some difficult technical issue related to achieving this?)
Asking because reading about this issue in the past is one thing that has kept me from trying out Clojure.
Re: Ask HN: What is your best advice for a junior software developer?
#366Run
In seriousness: get exercise. If you aren't in good shape it's draining, and making your life harder. Coding is hard enough
Re: Ask HN: What is your best advice for a junior software developer?
#367I've already written down everything I know in https://www.quora.com/What-are-the-best-secrets-of-great-pro.... I keep updating that answer from time to time.
Re: Ask HN: What is your best advice for a junior software developer?
#3681) If you're not a native English speaker, always improve your English. 2) Start your open source side project and work on it in your spare time. 3) Improve your skills by reading books and attending online courses. 4) Change your job/project every year.
re: 4) - if your CV has a new job on it every year, I would be much less inclined to interview/hire you. After all, 1 year in is when a developer really becomes valuable to an organization.
Re: Ask HN: What is your best advice for a junior software developer?
#369Stay a software developer as long as you can. Don't jump into management prematurely. You'll miss the days where you used to work on interesting technical problems rather than people problems and politicking.
Re: Ask HN: What is your best advice for a junior software developer?
#370Earlier quoted context omitted.
That’s only true if the developer of the class module let the entire stack trace get through to the consumer. In C# it’s the difference between... try { .... }catch(Exception e) { //Do stuff throw new MyCustomException(“Something Bad happened”); } And try { .... }catch(Exception e) { //do stuff throw; }
Erh, exception types should include an inner exception parameter, for the generic one they wrap. So neither of your two examples are all that great.
Why would I wrap an exception if I don’t plan to have special handling? If it is exception that I didn’t throw because of a business reason, why not just throw the original exception?