DIYZ is the DIY app for getting detailed step-by-step instructions and how-to videos that can help you complete your home repair or renovation without ever hiring a professional handyman or contractor!
The DIYZ app has over 1 million downloads. The average user of the app spends 7.5 minutes of engagement in DIYZ. The DIY videos have generated over 2 million views on YouTube. To create this app, the development team at decided to use Google’s Polymer.js framework.
The impact of company culture is reflected in achievement of goals, productivity levels and employee satisfaction. Basically, it can make or break a business.
Yet company culture is the one thing that many aspiring programmers overlook in their job search. Unfortunately, they find out too late after accepting a job that they are working for a company with a very poor culture. That overlook can have a negative impact on one’s career as a software engineer.
To better explain the impact of company culture, let me give your first-hand experiences that I have had in my career. The examples are taken from two different companies.
The 9–5, 40-hour work week is a reflection of how work was performed back in the industrial revolution. During this time workers punched a clock to measure time worked, and management used that as a gauge of productivity.
Today’s software engineers are smart creatives who prefer to work in an autonomous environment in order to create their best work. Unfortunately, management at some companies still cling to hours worked as a barometer of productivity.
Here are examples of how management treated work hours at two different companies.
- Create an object
- Create methods and properties for that object
With functional instantiation, we first create a function. Inside the function we create an empty object and add properties and methods to it. We then return this object.
Every time the function is called we will have access to the methods that were created. Here is an example of functional instantiation:
My journey in the tech world is quite unique. I graduated from university before the IBM PC was introduced and I earned my MBA before there was a world wide web. After an early retirement, I decided I wanted to attend a coding bootcamp. Now I’m a senior developer. Let me share 7 things I learned on my journey.
Table of Contents
- #1 — Learn Github
- #2 — Imposter syndrome is real
- #3 — Master your IDE
- #4 — Company culture
- #5 — Take control of your career
- #6 — Networking
- #7 — Never stop learning
Read review of Day 1 here. Read review of Day 2 here.
The third and final day of ngConf switched back to a single track format. Again every attendee was in one massive ballroom to hear speaker after speaker.
Adding Humor to Authentication
After the keynote opening session, the next speaker was there to explain authentication with Angular router. Normally this is a very dry topic because the gist is user tries to access a URL and if they don’t have access then they are denied.
Luckily for the audience the speaker is also an active improv actor and comedian. He convinced 7 (staged) audience members to join him on stage, get dressed in costumes and act out OAuth.
More than half of the time of the session was getting the 7 audience members on stage, outfitted and given directions. When they actually started to perform how authentication works, it was hilarious. Especially when Mike started to improve on his role as the spinner.