Earning Your Team's Trust as a New Engineering Manager
Earn your team's trust as a new engineering manager through listening, follow-through, individual support, and openness to feedback without forcing disclosure.
Read the article here:
https://t.co/qkiin5F2bV
Prioritize This CRITICAL Skill as a Developer - Interview With Callie Buruchara
This is the first EVER software engineering interview done on Dev Leader, and I was excited to be able to have my first awesome guest:
Callie Buruchara!
Callie knows that communication is a critical skill to have in software engineering, and she's experienced first-hand how big of a difference it can have even in a highly technical field. In fact, most people greatly over-prioritize their technical skills instead of communication!
Watch it here:
https://t.co/8ETv3RUFSR
This one thing kills most of the value of your tests...
Different tests have different types of coverage, and as a result, offer different kinds of confidence benefits.
I like unit tests for ensuring specific code paths are run how I'd expect. They don't help with refactoring but they help prove to me my code does what I said.
I like integration and functional tests for more general confidence and ability to refactor. They might be a bit harder to setup, tear down, and reset, but they are incredibly helpful.
But the one thing killing your tests:
Not running them.
Make sure you wire these up to get coverage automatically or you'll end up like me (in too many situations).
Watch the full video here:
https://t.co/6BS3x2Nlzz
Do You Suck At This Critical Software Engineering Skill?
I have worked with a lot of junior software engineers over the years, whether they are people I manage directly or people that I mentor. There's one skill that comes up repeatedly and I think it's a critical thing to pay attention to and practice as a junior software engineer. Any guesses? Watch and find out how you can put this to use for yourself!
Watch here:
https://t.co/pmG8OWcHSj
So it looks like there's more than one way to compare strings in CSharp, eh?
Read more here:
https://t.co/NyxfmYbumL
#csharp#dotnet#dotnetcore#beginners
MongoClient in https://t.co/j632lViqpy Core: Lifetime and Resource Ownership
Learn MongoClient in https://t.co/j632lViqpy Core with explicit configuration, singleton reuse, borrowed collection handles, and version-aware cluster ownership at shutdown.
Read the article here:
https://t.co/VAcZmR3Vwa
Helping a Mentee Choose a Development Focus
Help a mentee choose a development focus by exploring interests, everyday friction, and useful opportunities without forcing a goal or a larger career plan.
Read the article here:
https://t.co/JjzVJaMm6j
This one thing kills most of the value of your tests...
Different tests have different types of coverage, and as a result, offer different kinds of confidence benefits.
I like unit tests for ensuring specific code paths are run how I'd expect. They don't help with refactoring but they help prove to me my code does what I said.
I like integration and functional tests for more general confidence and ability to refactor. They might be a bit harder to setup, tear down, and reset, but they are incredibly helpful.
But the one thing killing your tests:
Not running them.
Make sure you wire these up to get coverage automatically or you'll end up like me (in too many situations).
Watch the full video here:
https://t.co/6BS3x2Nlzz
I'm not going to debate the "engineer" part of the "software engineer" title but...
Some people aren't aware there are restrictions around this title depending on where in the world you work!
When I was in Canada, "engineer" was classified as a licensed profession that required:
- An education from an accredited university
- An ethics exam
- Accumulated working hours signed off by an engineer
- Yearly dues to the governing body of engineers
Literally -- you could not call yourself a "software engineer" and there are many cases of the governing engineering body going to companies to tell them to adjust their job titles.
We were allowed to say we were "doing work in the field of software engineering", but we could not claim we were engineers unless we met the conditions I listed above.
Tough love, eh?
So by Canadian standards, I'm still not a "professional" to this day.
- I never accumulated the hours under another engineer
- I never wrote my ethics exam
I only had the schooling as part of my experience.
All of this just to let people know that there are different perspectives to take -- even when we're all talking about the same things and using the same words.
Are you a professional software engineer in Canada? Has anything changed since I've been there?
(How about that iron ring?!)
Becoming The Interview Champion - Interview With Dynamic Singh
I had the pleasure of sitting down with Bhupinder Singh, popularly known as Dynamic Singh, to discuss his journey in turning his interview problems... into one of his greatest strengths!
In our conversation, we discussed that it's not just about copying some steps and hoping you land the job -- truly, you need to become the person that you're aspiring to be.
And guess what that means?
You have to put in the time, and the effort, and the practice to become someone who is great at interviewing. It's all a mindset shift!
Watch it here:
https://t.co/0YQ6VgF7b5
#Interview #Podcast #SoftwareEngineering
📌 Have you been tuning into my AMA live-streams I do EVERY Monday at 7:00 PM PST?
Each stream I focus on:
- Reviewing my most recent newsletter
- Providing my perspective on spicy Reddit posts related to software development
- And most importantly... ANSWER YOUR QUESTIONS!
👇 Let me know what you want me to answer in my next stream! 👇