Vita and I discuss her experience as an engagement manager, dealing with customers and developers and advocating for both. We also talk about common hangups and changes in software projects and the things customers and developers should know when dealing with each other. Vita is a gem and can be reached from the Inoxoft homepage https://inoxoft.com/
Good software developers have a passion for knowledge that keeps them trudging on into the unknown. Devin and I chat about his experiences moving from Microsoft to FinTech, Startups and back. Devin clearly loves his craft and it was fun to hear his story.
As a contract software development shop, Inoxoft sees and delivers more projects to more customers than most. To do this well (and maintain our stellar reputation) we need to trust our delivery processes… Maksym and I discuss those processes and why they’re important.
What can hamburger pricing teach us about software development? Let’s talk pricing for development services, what should you be considering when requesting a quote or engaging with a software developer? How can you save money? And how can you stumble when engaging with quotes from disparate sources?
Stack Overflow Median Salary by Developer Type: https://insights.stackoverflow.com/survey/2020#work-salary-by-developer-type
More on the Big Mac Index: https://www.economist.com/news/2020/01/15/the-big-mac-index
below are the average salaries in the US by title, what does this breakdown mean for your project?
Engineering Manager - $152k
Dev Ops- $125k
Machine Learning- $125k
Full Stack Developer $112k
Tech teams are best when people teach each other, are open to learning new things, and are inclusive. Marni and I discuss the good and bad of tech culture and hopefully inspire everyone that good teams are out there and very possible with the right mindset :).
I love the book Moneyball, here's what it means to me and my work in software:
Software is team sport, there are so many positions to play!
10x Full-Stack Heroes exist, but I'd never build a team around them.
Everyone can contribute! Passion and ability to learn are so important.
Good managers focus on process. All-nighters are a sign of bad management.
Assume people are lazy, and setup your project to succeed anyway. Your process needs to work for "normal people", if you're dependtent on a hero to save you, you're being lazy... but assuming noone else is :).
Use Continuous Integration principles in your team, and in the market.
I discussed developments in machine learning with Shiva (ML Masters 2018 @ OSU). We talked about the huge improvements we've made in ML tooling in the past few years, how different communities have sprung up and how to use machine learning to power our future understanding of everything from movies to the atmosphere.
... we also decided we do not live in the matrix, and general AI is best left to the science fiction podcasts (or at least well qualified theorists, or maybe Bill Gates).
Shiva is a gun for hire and looking for new opportunities, you can find him on Linkedin and hire him here.
We spoke about how Daniel went from a self-taught trainee to an architect/wizard.
We spoke about how we build teams that we manage, our favorite teams, and aspects of successful teams.
We also HEAVILY ENDORSE @ESPNS "The Last Dance" as a study in teamwork and teambuilding
I run through some common misconceptions regarding remote work, with my baby in my lap.
Here's the list:
Remote is NOT NEW
Remote is NOT NICHE
Remote is NOT ALWAYS OUTSOURCE OR OFFSHORE
Remote does NOT REQUIRE SACRIFICING QUALITY
Remote IS NOT ALL OR NOTHING
Remote IS ABOUT RELENTLESS OPTIMIZATION (not just your commute)
Remote requires near-perfect information sharing (Internally and in Market)
"Always On” is real (but it is not new, it’ll be OK)
Remote frequently saves money for all parties involved (who saves more isn’t obvious)
I interview Jerrod Howlett about his time at Google, how to motivate the youth and underrepresented groups in Computer Science... and how to make it as the manager of the future (someone with an MBA and coding chops).
How can you tell if you're good at software development? How can you tell if your hires are any good? How can you be the Bill Belichick of software development managers, or the Tom Brady of software developers?
What does it take to be a professional developer? What does it take to build a great development team? Let's discuss some common advice, pitfalls and the stuff you MUST DO to be a professional software developer (or team).
Why do we treat all software projects the same? We can't always follow best practices, and cost needs to be taken into account. Let's discuss different stages of development of companies and projects, and let's agree that technical debt is sometimes good and necessary! If you’d like to suggest a topic or give feedback please email me at firstname.lastname@example.org.
Why don’t we approach software development the same way we approach homebuilding? Few are homebuilding experts, sure we might be handymen but we often hire teams of specialists to design, build, paint/decorate and inspect our home. Why don’t we do the same with software? Let’s discuss this for 10 minutes.
WSJ article on industry salaries: https://www.wsj.com/articles/amazons-typical-worker-is-in-a-warehouse-making-28-446-a-year-1524402003?mod=e2tw
If you’d like to suggest a topic or give feedback please email me at email@example.com