Live data from Hacker News

Leveling up as a Junior Engineer

medium.com

1–10 of 32 posts

Re: Leveling up as a Junior Engineer

#2
If you're interested in php and/or laravel I highly recommend laracast. He'll go through the exercise of creating a certain feature, and then refactoring that feature with an explanation as to why. And often, that refactor is the difference between entry level code that just works, to intermediate code that's scalable and easy to read. I highly recommend it.

Re: Leveling up as a Junior Engineer

#3
post #2

If you're interested in php and/or laravel I highly recommend laracast. He'll go through the exercise of creating a certain feature, and then refactoring that feature with an explanation as to why. And often, that refactor is the difference between entry level code that just works, to intermediate code that's scalable and easy to read. I highly recommend it.

Would you recommend Laravel and PHP? I know PHP is seen as outdated by some people... But now that that NodeJS/MongoDB hype is finally receding, PHP actually seems like a sane alternative.

Re: Leveling up as a Junior Engineer

#4
post #2

If you're interested in php and/or laravel I highly recommend laracast. He'll go through the exercise of creating a certain feature, and then refactoring that feature with an explanation as to why. And often, that refactor is the difference between entry level code that just works, to intermediate code that's scalable and easy to read. I highly recommend it.

Would you recommend Laravel and PHP? I know PHP is seen as outdated by some people... But now that that NodeJS/MongoDB hype is finally receding, PHP actually seems like a sane alternative.

I use Laravel and PHP for my job at a trendy start up. We use it to spit out JSON. I have no complaints, it's an absolutely fantastic framework - good support for the set of actions common to most web apps via the community and libraries.

Re: Leveling up as a Junior Engineer

#5
My advice:

- Never call yourself a Junior Engineer. If you have experience, even just a little, you are an experienced engineer.

- Develop your communication skills. The barrier to entry to start presenting at meetups is extremely low, do that with the goal of presenting at tech conferences.

- Skip the side projects. Of the 10 or so water walkers I've worked with, 0 have github accounts.

- Don't buy into the last paragraph of this blog. Software development isn't hard, and the last thing you want to do is think you need to constantly keep up with the latest and greatest tech. If you step back it looks a lot like an industry that doesn't know whether it's coming or going, don't fall for the trap.

Re: Leveling up as a Junior Engineer

#6
post #2

If you're interested in php and/or laravel I highly recommend laracast. He'll go through the exercise of creating a certain feature, and then refactoring that feature with an explanation as to why. And often, that refactor is the difference between entry level code that just works, to intermediate code that's scalable and easy to read. I highly recommend it.

Would you recommend Laravel and PHP? I know PHP is seen as outdated by some people... But now that that NodeJS/MongoDB hype is finally receding, PHP actually seems like a sane alternative.

Any mention of PHP's merits at this point is going to start a flame war. It's pretty easy to be a terrible developer with it. JS/Node can allow you to be just as bad of a developer. The key to being good and getting a good start is to learn the fundamentals of whatever language you choose. Don't pick a framework and definitely don't rely on one without knowing a language. Frameworks come and go. I personally like Python but mostly use PHP in my day job due to it being the company standard for web apps. It works just fine for the company's needs. Most people can learn the basics of a language in a day so it may be worth running through a few tutorials in a few different languages to see if there is something that suits you. In my opinion it's good to have a toolbox of languages because sometimes a certain language is just better than others at different things.

Re: Leveling up as a Junior Engineer

#7

My advice: - Never call yourself a Junior Engineer. If you have experience, even just a little, you are an experienced engineer. - Develop your communication skills. The barrier to entry to start presenting at meetups is extremely low, do that with the goal of presenting at tech conferences. - Skip the side projects. Of the 10 or so water walkers I've worked with, 0 have github accounts. - Don't buy into the last par…

Are you https://en.m.wikipedia.org/wiki/Daniel_J._Bernstein?

Re: Leveling up as a Junior Engineer

#8

My advice: - Never call yourself a Junior Engineer. If you have experience, even just a little, you are an experienced engineer. - Develop your communication skills. The barrier to entry to start presenting at meetups is extremely low, do that with the goal of presenting at tech conferences. - Skip the side projects. Of the 10 or so water walkers I've worked with, 0 have github accounts. - Don't buy into the last par…

> Of the 10 or so water walkers I've worked with, 0 have github accounts.

I have the complete opposite experience.

Re: Leveling up as a Junior Engineer

#9

My advice: - Never call yourself a Junior Engineer. If you have experience, even just a little, you are an experienced engineer. - Develop your communication skills. The barrier to entry to start presenting at meetups is extremely low, do that with the goal of presenting at tech conferences. - Skip the side projects. Of the 10 or so water walkers I've worked with, 0 have github accounts. - Don't buy into the last par…

> Of the 10 or so water walkers I've worked with, 0 have github accounts. I have the complete opposite experience.

My guess is it's subfield/language dependent.

Re: Leveling up as a Junior Engineer

#10
In my opinion, side projects don't have to ship. Some people do need to ship side projects, some people do not. It's important to challenge yourself with code, absolutely, but enforcing deadlines on yourself is usually just met with disappointment when you don't do it. Additionally, by allowing yourself to stop working on side projects when you want, you can focus on doing the parts of coding that you enjoy which means you can find your preferences and passion.

However, I do believe that everyone should be able to set up a server and a web page to show off the functionality of any side project they make (or an app). The best part about any side project is taking your phone out with your friends and showing it off.

Post reply on HN