{"id":6309,"date":"2019-08-22T20:29:48","date_gmt":"2019-08-23T01:29:48","guid":{"rendered":"http:\/\/www.killersites.com\/blog\/?p=6309"},"modified":"2019-08-22T20:29:49","modified_gmt":"2019-08-23T01:29:49","slug":"more-than-dress-to-impress","status":"publish","type":"post","link":"https:\/\/www.killersites.com\/blog\/2019\/more-than-dress-to-impress\/","title":{"rendered":"More Than Dress to Impress…"},"content":{"rendered":"\n

How do you impress as a new developer?<\/em><\/p>\n\n\n\n

You just landed your first job as a programmer or a dev… Congratulations! Now how do you keep that job? We gotcha.
First, read this<\/a><\/strong>.
That’s a lot to remember, are you freaking out? No problem.
All you really need to do is remember step 1 or (for those of you that didn’t read it):

Communication.<\/span> “Communicate; listen, that’s a big part of it. …Being somebody they can count on, somebody that gets along, somebody that they can speak to is a huge part of the job. …Just work with people, listen, and that is like 90% of it.”
-also-<\/strong>
Don’t ask Google-able questions.<\/span> “…If you find that you’re having difficulty, don’t be afraid to ask questions …short, concise questions -don’t ask super long-winded questions- keep it pithy\/to the point… …[And] don’t ask too many questions -especially questions that you could research on Google (ultimately they’re hiring you<\/em> to get the job done).” But stuff happens, for example, “…there could be some design issues, there could be some specifics with regards to their particular software…hopefully they’ll be able to provide that [answers] for you…”
-and-<\/strong>
The ‘Ramp-up’.<\/span> It doesn’t matter if you’re a fresh-faced noob or a grizzled old veteran programmer, no one with brain in their skull expects you to get things right outta the gate. There’s a ‘ramp-up’<\/em>: “When they first bring you in there’s going to be some expectation of a ‘ramp-up’ time. You’re not going to know everything …if they have an advanced piece of software, …you’re going to have to get to know the code base, and that could take time depending on the complexity of the software. It’s not your code, you’re going to have to learn it. And in your first little while go out of your way to make sure you try as quickly as possible to learn the code -don’t kill yourself; don’t get all sweaty and nervous about it-<\/span> …but ask your coworker, your lead. ‘what do I need to do first so I can get up to speed and help you guys?’ “.

After that, it’s like any other job, “…be sure to double-check your work: make sure you don’t make any silly mistakes, …if you’re assigned to a task, make sure you get things done on time, …and hopefully you didn’t lie on your resume and say you were a ‘master nerd’, cuz they’re going to figure you out pretty quickly…”.

Check out the VLOG for some really good advice and <Shameless Promo<\/strong>> generally speaking, if you’ve taken the web stack course, you might find yourself ahead of the game as many people found out once they got the job…
-Enjoy!<\/p>\n\n\n\n

\n