I have a new friend on Linkedin, a Googler named Jon Youshaei. This is his latest post that appeared in my Linkedin feed and really got me thinking about creativity and imitation:
0 Comments
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. One of my favorite bloggers, Seth Godin, is an author and entrepreneurship coach who emphasizes making quality products that people want over mindless "marketing" tactics to get customers. This is one of his favorite quotes:
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.
At my last company I was really the first and for a while only coder there. At previous jobs they had always used one of the two popular version control systems: git or subversion. These are fantastic for backing up source code, reverting to previous versions, and sharing code across workstations. These days it's almost a given that if you're going to be coding full-time you're going to use (at least) one of these two platforms- almost. This was previously a company of all designers, and most of them did their work in adobe programs like InDesign, Illustrator, and Photoshop. They faced the same risks of losing their files, and the solution commonly used was a combination of a shared cloud drive and each computer station backed up by Time Machine, which is a mac os program described as a, "built-in backup feature of OS X". It is sometimes called a "ghost drive" because you have an external hard drive that continuously copies and stays in sync with your main hard drive. This is a mac-only program, but I'm sure you can do a similar "ghost drive" technique on Windows or linux. After using this system for a while I began to like it a lot and started to wonder if this could be a viable option for more code-focused development companies.
|
AuthorThe posts on this site are written and maintained by Jim Lynch. About Jim...
Categories
All
Archives
March 2023
|