Playing: 135: Hasty Treat - Cranky Developers
Potluck - Interview Qs × Headless CMS × React Hooks × Resume Design × Redux vs Context × More!
How We Manage Our Lives — Notion, Todos, Notes, Focusing, Calendars, Goal tracking, and more!
Potluck - Changing careers × Repo organization × CSS Grid × Certifications × Freelancing × Spammers × More
Potluck - Where to start with JS × Freelancing × Cron jobs × Split testing × Frameworks in 2019 × More
Potluck - $100/hr × Redux Replacements × Full Stack Designers × JWT × VS Code Tips × More
Potluck - Editor Fonts × Portfolios × Meetup Tips × Switching to Windows × Freelancing Sources
Potluck EP × Remote Work × Headless WordPress × Good Client Questions × Alternate Careers × React API Credentials
Potluck EP × Is Redux Dead × Learning Quickly × Developing Solo × Specialist vs Generalist × Funnest Projects × Wes’ BBQ Course
Potluck EP × Vue.js × Headless WP × Typescript & Flow × Productivity × Server Side Rendering × Yeoman
Wes and Scott's Lives - Breakdancing, BBQ, Wives, Work/Life Balance, Problem Solving, YouTube Subscriptions
Snack Pack — CSS Frameworks, React HOC, Render Props, Coding Designers, Early Career Advice and a sound board!
Hosting & Servers — Heroku, Now, Galaxy, Digital Ocean, Linode, Docker, Netlify and more!
Apr 15th, 2019
Hasty Treat - Cranky Developers👇 Download Show✏️ Edit Show Notes
In this Hasty Treat, Scott and Wes talk about cranky developers — those devs who never seem happy about anything, always mad about tech choices, and constantly writing off any new tech as simply a "fad" or unnecessary.
If you want to know what's happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code "tastytreat".
2:20 - How to deal with cranky devs
- Many experienced developers prefer older, stable technology for a reason. They have been through it before.
7:14 - Questions to ask when considering new tech:
- Is it better for the product?
- Is it better for the users?
- Is it better for the business?
- Is it better for the developer?
16:39 - How to convince them:
- Proof of concept - show them it's better.
18:28 - Things to acknowledge:
- There are risks in changing technologies.
- There are costs - training, tooling, hosting.
21:20 - Some people are not interested in improving themselves
- They got the job they want and are short sighted about the future.
- You can appeal to management about making progressive choices.
- If management isn't interested, you should look for a new job.
- Gulp Babel
- React for Beginners
- Swix --> Getting Closure on Hooks