“I was like, I don’t want to just write code every day, I want to be close to the actual product and be a user champion.”
#include <Half Hour Intern>
#include <Handsome, Intelligent>
#include <Justin Washington>
void func(basic);
void do_something(Interesting, Awesome);
int main()
{
std::string str = "Test";
int x = 5;
std::thread t{func, str, std::ref(x)};
do_something(Enjoy);
t.join();
}
“On the consumption side people are like “Man, they should just do this, it’s so easy they should just do it.” But they don’t think, it’s not about just the idea, it’s about the execution… If you release something and it’s supposed to be a flagship feature, it’s hard to get people to change their first impression.”
“There are a lot of different things to think about and I think that someone good is creatively thinking about how to break something. ”
Interview Contents
3:30 - Finding the right software engineer for the show.
4:30 - The various fields under the software engineering and coding umbrella.
8:30 - The ability to try multiple jobs in the programming industry.
11:15 - Front end vs. back end.
14:45 - The role of a QA engineer and what drew Justin to it.
20:15 - Getting the amazing internships Justin got in college.
27:00 - At big tech companies, what percentage of the employees are developers?
29:30 - How specific can each developer’s individual job get.
32:00 - If you come up with a huge, amazing idea at your company, do you get paid a bunch of money for that?
36:00 - The amount of time to code something simple.
38:00 - Do you need engineers to just maintain things so they don’t get buggy and break down?
41:35 - How long does it take to develop something big?
45:30 - What makes a good QA software engineer?
47:45 - The pros of working for a tech company and the culture of tech.
59:45 - Pay and work hours.
1:06:30 - Advice.
Links
THIS EPISODE WAS MADE WITH THE SUPPORT OF
Roxanna
Michelle & Jim Wortner
Janelle Swanson
Jimmy Seymour
