Junior Developer Toolbox

In this episode we’ll be talking about different considerations when building an application outside of your day job. We’ll talk about gathering requirements, choosing a tech stack, and setting the right expectations with your client.

“Sharpening the Tools” – the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.

————————–

Erin:

Making progress on the Python track. Finished the Lists course and workshop on __dunder__ (double under) main. Currently working on Object-Oriented Python.

Spent a couple of weeks being a Teacher’s Assistant in NSS’s Jumpstart class.

Also, got a job promotion to “Software Engineer”, so I suppose I’m officially no longer a “junior” developer.

Dave:

Followed a dotnet core tutorial for a simple Todo App, and built the Angular UI to integrate with it. Excited about Angular Testing workshop that work is sending me to later this week!

 

“Opening the Toolbox”

Today we’re discussing things to consider when getting started on a side project.

Considerations:

* What are we going to build? How to approach it?

* Talk with stakeholders about Requirements

* Plan for getting feedback from them throughout the project

* Tech stack

* Hosting

* Deployment platform (Heroku, Digital Ocean, etc.)

* Cost? Budget?

* Timeline & availability for those working on the project

* Splitting up the work

* Tracking the project

* Use Trello or a similar project tracking tool

 

References

==========

 

Extra Links

===========

 

Enjoy the podcast? Consider supporting our work by becoming a patron on our Patreon page. Every little bit helps cover our basic expenses and keep the show going.

You can also donate to our JDT PayPal page.

 

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

Patreon: https://www.patreon.com/juniordevelopertoolbox

PayPal Donation Pool: https://paypal.me/pools/c/86X3cA2N3O

 

www.juniordevelopertoolbox.com

In this episode we’ll be talking about popular languages in 2019, some common traits they share, and deciding which ones to learn next.

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

“Sharpening the Tools”

————————–

Erin:

Finished with JavaScript Objects. Started digging into Python a bit just because.

Dave:

Office Olympics, remembering to take care of your physical self.

 

“Opening the Toolbox”

Episode Outline

===============

According a TechRepublic article, here are the 10 most popular programming languages as of December 2018:

* Java

* C

* Python

* C++

* Visual Basic .NET

* C#

* JavaScript

* PHP

* SQL

* Objective-C

We wanted to take a cursory dive into some of the different languages if you’re curious about them or trying to figure out which one you want to learn next.

 

Erin has experience with: JavaScript, C#, SQL, Python (minimal), and Java

Dave has experience with: JavaScript, (minimal) PHP

 

Lots of languages are based C in some ways, borrowing some ideas and syntax.

 

Compiled vs. Interpreted languages –

* Interpreted means executed directly – JavaScript, Python, PHP

* Compiled means it gets translated first (into machine code or similar) before it’s executed – C, C++, C#, Java, Objective-C

 

Static vs. Dynamic (Timing)

* Static typed languages are those in which type checking is done at compile-time

* Dynamic typed languages are those in which type checking is done at run-time

 

Weakly Typed vs. Strongly typed (Behavior of variable types)

* Strongly typed means a variable will not be automatically converted from one type to another. (explicit conversion is required)

* Weakly typed means variables can be implicitly coerced to unrelated types

 

Strongly typed languages: Must use explicit type declarations when declaring variables

* Examples: Java, C#

 

Dynamically typed languages:

* Examples: JavaScript, Python

 

JavaScript, Java, and C# are popular Enterprise languages and are very well established.

While Java and C# are server side languages, JavaScript is both a client side and server side language (Node.js).

 

Python and R are popular for Data Science

 

PHP: Hypertext processor: an early web language that’s pretty widespread throughout the internet, especially due to use of popular CMSs like WordPress.

 

Objective C

* A general-purpose, object-oriented programming language that adds Smalltalk-style messaging to the C programming language. … It was selected as the main language used by NeXT for its NeXTSTEP operating system, from which macOS and iOS are derived.

 

10 Best Programming Languages to Learn in 2019 (for Job & Future):

https://hackr.io/blog/best-programming-languages-to-learn-2019-jobs-future

 

References

==========

Top 10 Programming Languages as of December 2018:

https://www.techrepublic.com/article/10-popular-programming-languages-developers-should-learn-in-2019/

 

10 Best Programming Languages to Learn in 2019 (for Job & Future):

...

In this episode we talk to Jonathan Edwards about final bootcamp projects and presentations, job interviews, and landing your first developer job!

Jonathan is a recent graduate of NSS cohort 27. Previously, he received his BS in Communication Advertising from UT Knoxville and moved to Nashville four years ago to pursue music. He developed an interest in web development while working in digital marketing, after which he decided to enroll in NSS’s full stack software bootcamp. He’s a new employee at naviHealth, and we’re talking to him today about what the post-NSS job hunt was like and the process of landing the job.

“Sharpening the Tools”

—————————

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

Erin:

JavaScript Objects refresher tutorial. And dreaming about JavaScript Objects?

Dave:

Meet-up presentation on Impostor Syndrome – working toward my 2019 goal of submitting a talk to a tech conference.

Jonathan:

Angular tutorials, and finishing a React app

 

*Shoutouts*

We’d like to give a shoutout to Brandon, our newest patron on Patreon. Thanks so much for your support!

 

“Opening the Toolbox”

Episode Outline

===============

* Tell us a little bit about your background.

* From Knoxville, TN. Studied Advertising at UT. Moved to Nashville for music

* How did you get interested in web/software development?

* Always had an interest in learning how to code, but kept coming up with reasons as to why I couldn’t do it

* Was looking for ways to grow digital marketing skill-set when I came across web development and web design.

* Took some online classes to teach myself some basics and fell in love with it.

* Decided this is where I belonged and decided to attend NSS to make sure I was learning the right material in the right way

* Can you describe your overall NSS experience? Do you feel adequately prepared for a junior level developer position?

* Absolutely, attending NSS was the best decision I’ve ever made.

* The second half of the course is spent working on teams doing weeklong sprints with planning, standups, retros, etc

* The biggest thing was learning how to learn, because there will always be something new to learn in this field.

* Another big plus of NSS is all of the extra help they give us outside of the classroom, with resume writing, interview prep, etc

* Were there other paths in development that you considered?

* Originally wanted to do more front-end focused work, but after going through the back-end of the course and getting experience with C# .NET, SQL, etc., doing full-stack work is where I see myself longterm. I like different parts about both front-end and back-end development and look forward to using both in my career

* Can you tell us about your capstone projects? What languages/technologies did you learn?

* Front-end capstone written in React using Bloomer and Bulma for styling

* App called progressions, goal is to help beginning guitar players write better-sounding chord progressions

* Users select the key they want to write their song in and are show the 7 different major and minor chords that make up that key

* Users can press keys 1-7 on their keyboard to hear audio of each chord and write a chord progression that will sound good without ever having to pick up an instrument or even know how to play a guitar

* Users then select their 4 chords they want to use to write a song and are shown a chord chart of how to play it on a real guitar.

In this episode we have a special guest! Lesley Boyd is deep in the thick of her Nashville Software School bootcamp, and is here to talk about her experience. She has a background in corporate roles, from supply chain management and business analyst. In her words, always “on the edge of IT” but she has now taken the plunge and is about 4 months into the NSS program! Welcome Lesley!

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

Erin:

Fixed my website! After finally being contacted by a real person from CloudFlare, they pointed out that I had multiple A records pointing to different IP addresses in my DNS settings, which could cause problems such as the one I was experiencing.

I found an article on Github with different IP addresses (of the host server) that I should point my A records to, and violá, my website resolves successfully.

Dave:

Chugging along with my Angular tutorial, I’ve been learning about building custom Directives and Services and how to use / inject them!

 

Lesley:

Went to a data science meetup, and discovered https://pybit.es/

 

“Opening the Toolbox”

 

Today we’re talking with Lesley Boyd about her experience at Nashville Software School’s bootcamp. We’ll discuss her decision to go into the bootcamp, things she’s learning, and challenges she has faced, and her aspirations after the program is finished.

 

* Tell us a little bit about your background.

* How did you get interested in web/software development?

* Can you tell us about how you made the decision to go to NSS?

* Were there other paths in development that you considered?

* You’ve completed the front end segment, right? Can you tell us about your capstone project?

* Tell us about your cohort, is it a tight knit group, or …? Are a lot of them in the same career phase as you, or is it varied?

* How does it break down in terms of solo work, group work, access to instructors?

* What are you most excited about the bootcamp? Anything you’re worried or apprehensive about?

* Do you have a sense of the kind of role you’re interested in after you complete the program? Front-end? Back-end? UX/UI Design? Web / mobile?

* Have you thought about what kind of industry you want to work in? Fin-tech, healthcare, building websites for an agency, etc.

* Is there anything you wish you had known about the program before you started?

* Any other goals or things you hope to learn in the program?

 

LinkedIn: https://www.linkedin.com/in/lesleyaboyd/

Twitter: @boyd1lesley

Personal site: https://www.lesleyaboyd.com/

 

References

==========

https://pybit.es/

http://nashvillesoftwareschool.com/

 

Enjoy the podcast? Consider supporting our work by becoming a patron on our Patreon page. Every little bit helps cover our basic expenses and keep the show going.

You can also donate to our JDT PayPal page.

 

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

Patreon: https://www.patreon.com/juniordevelopertoolbox

In this episode we’ll be talking about the planning that goes into attending a software bootcamp, comparing different programs, and factors in making the right decision.

We have a special guest today, Sarah Weatherbee is here to talk about her experience with the Nashville Software School Jumpstart program. Sarah has a background in journalism, which she obtained while studying and working abroad in Beirut, Lebanon. We met through discussing her interest in podcasting, and discovered she was attending NSS’s Jumpstart program at time.

 

Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.

 

Erin:

Wrestling with my personal website and CloudFlare.

 

Dave:

Working through a ‘Complete Guide to Angular’ tutorial on Udemy

 

Sarah:

NSS Pre-Work:

Smarter Way to Javascript book

https://internetingishard.com/

 

Cool news! We were recognized on FeedSpot’s Top 10 Software Engineering Podcasts You Must Subscribe & Listen to in 2019! We are #7 out of 8 on the list (not sure what happened to 9 & 10?). Thanks for the shout out, guys!

 

 

“Opening the Toolbox” (main episode)

Today we’re talking with Sarah Weatherbee about her decision to attend Nashville Software School’s bootcamp. We’ll discuss her thought process, pre work and preparation, and how it’s going for her so far. Questions we ask:

Tell us a little bit about your background.

How did you get interested in web/software development?

Can you tell us about the Nashville Software School Jumpstart you did, and how the experience was for you?

You’re starting the full time evening program at NSS very soon, right? What process did you go through for making the decision?

Were there other paths in development that you considered?

Can we ask about the tuition for the program? How did that affect your decision? (Opportunity Tuition Program)

How is your pre work coming? Did your jumpstart help with this, or are you learning anything new?

What are you most excited about the bootcamp? Anything you’re worried or apprehensive about?

Any other goals or things you hope to learn in the program?

Sarah mentioned the Code for Nashville meetup, for those of you in Nashville who’d like to check it out.

How can listeners get in touch with Sarah?

She’s on LinkedIn at: https://www.linkedin.com/in/sarah-weatherbee-a518556/ and Instagram at: @sweatherbeez

 

Enjoy the podcast? Consider supporting our work by becoming a patron on our Patreon page. Every little bit helps cover our basic expenses and keep the show going.

You can also donate to our JDT PayPal page.

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

Patreon: https://www.patreon.com/juniordevelopertoolbox

 

In this episode we’ll be talking with Corey Gross about setting goals for the new year, and reviewing some goals we set this time last year, and discussing how we did!

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”————–

Erin:

Looking into SSL certificates and why the one for my personal site has been having issues. Learning about CloudFlare to see if it’s a viable option/solution.

Dave:

Web Application Security class at work – learning about OWASP Top Ten vulnerabilities.

OWASP Top 10 Vulnerabilities on Treehouse

Corey:

Wes Bos ES6 For Everyone, Learn Node refresher (Webpack and Passport, really)

Syntax – Web Bos & Scott Tolinski’s podcast

 

“Opening the Toolbox”

Guest Intro:

Corey Gross is a web developer, tabletop gamer, Nintendo Switch evangelist, and Former Professional Nuisance to Dave Harned. He studied English Literature and Writing at the University of Pittsburgh, but immediately pivoted to web development within a year. He later earned a degree in Software Development from Bellevue University in Omaha, Nebraska while working his first dev job at a leading creative agency. Hopping from city to city, Corey’s currently back in his home town and working as a web developer in Philadelphia. Welcome to the show Corey!

Anything else our listeners should know about you?

I’ve invited Corey on the show to talk about a big audacious goal that he’s set for 2019, but before we get into that … Happy New Year everyone! As it happens this episode will be dropping on New Years Day, 2019! We hope you all had a safe and joyful holiday season, and now it’s time again to look ahead at a brand new year.

 

Let’s take a look and discuss goals we set last year (Episode 7 – wow!). How did we do?

 

Erin:

* Landing a new job by the end of January 2018

* ✅Accepted my current job shortly after New Year’s and started on January 19th

* Moving out of parent’s house (within 6 months of new job)

* ✅Moved out within 9 months of starting the job, but I started looking to buy a house around 6 months after starting the job

* Ongoing learning – finishing iOS track on Team Treehouse (end of 2017)

* I’m still currently halfway through the track. I got distracted in learning other things and completing other courses

 

Dave:

* Dive deeper into Angular”

* Although I have done a lot of Angular development this year, did I meet my goal? Not sure it was well defined – not specific or measurable

* Achieve work goals / deliverables

* ✅I did meet my work goals, and at performance review received an “exceeds expectations” ranking

 

Podcast Goals:

* ✅Starting to bring guests on the show

* ✅Wider range of content

 

SMART Goal Characteristics:

* S – Specific (or Significant).

* M – Measurable (or Meaningful).

* A – Attainable (or Action-Oriented).

* R – Relevant (or Rewarding).

* T – Time-bound (or Trackable).

 

What are some new goals we have for 2019?

Corey set a “big hairy goal for 2019, let’s discuss! Corey, can you tell us a little bit about your plans?

I’m starting my own web agency with a buddy of mine from high school – one of the two Best Men at my wedding. We’re looking to do web design and development work in the Greater Phi...

In this episode we’ll be talking about the QA role on an agile team, skills and knowledge beneficial to this role, and how developers and QA can work together collaboratively.

Today we’re happy to welcome Peggy Sturman to the show. Peggy has been a long time listener and supporter of the show. We met her through our Slack channel where we often have discussions around technologies we’re learning, career and interview advice, and thoughts about the field in general. She has nearly two decades of Quality Assurance experience and is currently learning about software development and coding in her free time.

Welcome to the show Peggy! Is there anything else you’d like our listeners to know about you?

 

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

===============

* If you were to describe Quality Assurance in an elevator pitch, how would you describe it?

* Quality Assessment, trying to break the application

* Did you have any formal education to prepare you for working in QA? If so, did you feel adequately prepared for your first QA role?

* Can you take us through a typical day as a QA Engineer?

* What technologies and tools do you use?

* What’s the structure at your job? Are you doing QA for multiple teams / projects?

* What allows your team members/software developers to help you do you your job effectively?

* You’ve talked about learning to code in your free time, what languages and frameworks are you learning? How are they coming along?

* Do you feel that your QA experience helps when learning code, and / or does learning code help with your QA role?

* Black box testing – also known as Behavioral Testing, is a software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional. http://softwaretestingfundamentals.com/black-box-testing/

* Smoke testing – also known as “Build Verification Testing”, is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing. http://softwaretestingfundamentals.com/smoke-testing/

* Regression testing – s the process of testing changes to computer programs to make sure that the older programming still works with the new changes. Regression testing is a normal part of the program development process and, in larger companies, is done by code testing specialists. https://searchsoftwarequality.techtarget.com/definition/regression-testing

* What would you tell someone interested in learning about or exploring Quality Assurance? Are there certifications you can get? Recommended resources?

* https://www.ministryoftesting.com/

* What’s something you wish you knew before starting this role?

 

Peggy’s LinkedIn: https://www.linkedin.com/in/psturman/

 

References

==========

https://www.ministryoftesting.com/

Extra Links

===========

 

You can reach us at helloworld@juniordevelopertoolbox.

In this episode we’ll be discussing Alon’s role as a Security Service Delivery Lead, how he applies digital anthropology to his job, and security issues facing companies and developers.

Alon’s IT career spans academic, start-up, and corporate environments. His experience ranges from software development, qualitative analysis, CRM design, building platforms, Security Operations, automation and project management. He is currently a Security Service Delivery Lead here in Nashville and was recently married!

Welcome Alon!

 

“Sharpening the Tools” – the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development

 

“Opening the Toolbox”

Episode Outline

===============

* Let’s start by getting into what you do. What would be your elevator pitch, to describe Information Security? Your current role?

* Can you walk us through a typical day at your job?

* On your website you describe yourself as a ‘digital anthropologist’ … what does that mean, and how does it relate to what you do?

* You mentioned computer to human interaction – let’s get into what that means

* What kind of additional education, certifications, or training have you done?

* How much do you interact with code in this position? What technologies and tools have you used?

* Tell us something you *don’t* particularly enjoy about your job or something you would like to improve?

* What’s something you wish you knew before starting your current role?

* What are some things Jr Developers should know or be aware of regarding security and infrastructure?

* What advice would you give someone wanting to go in this career direction?

Alon’s Article: Downloading Culture: Community building in a decentralized file-sharing collective

www.alondc.com

facebook.com/alondc

twitter.com/thealondc

https://www.linkedin.com/in/alondc/

 

References

==========

Moodle LMS Tool – https://moodle.org/

Extra Links

===========

 

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

 

www.juniordevelopertoolbox.com

In this episode we’ll be talking with Dan Weese about his perspective on interviewing and assessing developer candidates, and building strong teams.

‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

Sharpening the Tools

————–

Erin:

Continuing with Docker and starting with ElasticSearch!

Dave:

Shifting gears with containers … also, 64 bit encoded strings!

Dan:

 

“Opening the Toolbox”

Episode Outline

===============

Today we welcome Dan Weese to the show to discuss a Hiring Manager’s perspective on hiring junior developers.

Dan is Software Development Manager with over 20 years in software application development, including 14 years in healthcare, 12 years in commercial software, 10 years in Supply Chain Management and Warehouse Distribution, and 10 years in operations. (By my math some of those experiences must overlap, since added together that’s 46 years of experience!)

He is self-taught in 4 programming languages. While Dan’s degree is in Audio Engineering, his skills have led him to become a Microsoft Certified Trainer, Certified Scrum Master, Certified Scrum Product Owner, and Certified Scrum Professional.

Dan’s unconventional entry into the IT community gives him a unique perspective on hiring and he’s been able to take several people with skills outside of IT and apply them towards a successful career in the technology sector.

* What do you look for when hiring junior developers? Particular skills? How much proficiency in those skills? Demonstrating a drive to learn etc.?

* Job descriptions often vary and are unclear between whether they are entry level or “junior level”, so junior can mean anything from it’s your first job up to I’ve seen 5 years of experience preferred. How do you evaluate junior developer skills?

* When you write a job description, how many of the skills listed are you expecting your candidates to meet? What’s your advice for juniors applying for junior-level positions?

* What differences do you notice in education background? Traditional CS degree vs. software bootcamp vs. self taught?

* How do you typically interview a junior? Do you give them a whiteboard or take home coding test? How effective do you think those methods are?

* How do you come up with interview questions?

* What non-technical skills are you looking for in an interview?

* What are some things you can’t tell about a person from an interview, that you only learn on the job?

* One of our listeners wants to know, how should they dress for an interview, especially in a casual workplace? Is it weird if the interviewee is overdressed compared to everyone else?

* When you’re reviewing a lot of resumes, what are you looking for? What makes someone stand out?

* Are cover letters still a thing? Does the email you’re attaching the resume to suffice, or do you appreciate a formal, separate letter?

* Final words of wisdom for junior developers applying and interviewing for jobs?

 

You can reach Dan at:

LinkedIn: https://www.linkedin.com/in/daniel-weese/

Twitter: @danweese

Instagram: DanWeese

E-mail: [email protected]

Happy Thanksgiving everyone!

 

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

www.juniordevelopertoolbox.com

In this episode we’ll be talking about giving your brain a break! We’ll touch on strategies for recovering from mentally taxing work, and the importance of taking time for ourselves.

“‘Sharpening the Tools’ is the section of the show where we discuss what tools we’re using, concepts we’re learning, and generally how we are continuing our learning in software development.”

“Sharpening the Tools”

————–

Erin:

More Docker. How it differs from virtual machines. The Dockerfile is the config file for managing images and containers. Etc.

Dave:

Docker docker docker! Went to EEConf and learned some exciting news. Also had a Docker workshop that was interesting, now I’m trying to figure out some other ways to set up and use docker

“Opening the Toolbox” (20 – 30 mins)

Episode Outline

===============

Today we’re going to be discussing the importance of taking time to care for yourself. In episode 25 we discussed physical ways to take care of yourself while you’re working – today we’re going to continue that theme in a more general mental way.

Disclaimer: We’re not doctors! Anything discussed here represents our opinions, and shouldn’t take the place of real medical advice.

Mentally taxing work / Burnout

Ways to give your mind a break:

* Meditation / yoga

* Unplugging! (camping?)

* Take a bath

* Go for a walk or a hike

* A hobby – woodworking or other arts & crafts

* Whatever works for you and makes you feel relaxed or re-energized

Why is it so important to take time for ourselves?

* Diffuse thinking – mentioned way back in Episode 5 – The N00b Never Stops

* Mental fatigue – some days you just feel like your brain is fried

* “Mental health days” – mini vacations, long weekends

* Vacation – widely considered to be good for your health, reducing stress, etc

* Not everyone gets this perk. Contractors / freelance may have a harder time

* Not everyone TAKES this perk. Places with unlimited vacay show people use less

* Tends to delay stress. Slammed when you get back, playing catch up, reduces the benefit by injecting all that stress back

How could we better plan for a relaxing break?

 

You can reach us at [email protected]

Facebook: Junior Developer Toolbox

Twitter: @JrDevToolbox

Instagram: JuniorDeveloperToolbox

www.juniordevelopertoolbox.com