I'm super excited right now. It's Saturday morning of memorial day weekend right, and yesterday I had an interview with a rapid growing music-related tech company. They have a really awesome office in the Chelsea market area of New York City. Everyone has a huge iMac at their desk along with a Macbook Pro (well you can choose but it seems like 99% of people prefer mac there). Oh by they way, your desk is a standing desk with power controls to adjust it up or down. As an Angular developer you get to use WebStorm (I'm assuming I would, the interviewer used IntelliJ which is basically just a more features / languages version of WebStorm). Tons of free snack, drinks, and a pretty cool espresso machine that I got a chance to use, a cool outdoor terrace, and ping pong tables all made it this seem like a surreal workplace. I even saw a little nook that had a Nintendo 64 set up with Goldeneye in it! But this post isn't about how great it would be to work at this company; it's about how the front-end teams of today and tomorrow can use principles from the Java era to craft seemingly bulletproof code.
0 Comments
I was recently viewing the Pluralsight course Making the Business Case For Best Practices by Erik Dietrich, and I really found this to be an excellent slide. This is Erik's view of the common best practices in software development today, and in my descriptions below I'll try to explain how these ideas can be applied to Angular front-end development.
Not to brag or anything, but yesterday I just got my fifth(-ish) legit coding job. Now that I'm finished the job hunting process, I'd just like to record some thoughts about how I go about getting a job for my future self and anyone on the internet looking for a coding job (no one reads my blog except for me though, lol). I am still pretty young and don't know everything, but this post will definitely help someone (and hopefully my future self).
As it turns out I'm looking for a new job right now, and I'm working on my resume. I wanted to make a section of the header in my resume so that you could easily click to different sites of mine: twitter, github, and linkedin. The problem was that my linkedin url looked something like this: www.linkedin.com/pub/jim-lynch/22/814/63a/ |
AuthorThe posts on this site are written and maintained by Jim Lynch. About Jim...
Categories
All
Archives
March 2023
|