In Episode 38, we dug into the first section of the essay by Robert Read on what it takes to be a programmer. In that episode there was a lot of great information on what to expect and what should be expected of you as a developer. In this episode, we go into the second section of that essay which gives Mr. Read’s thoughts on what it means to be an intermediate programmer. As we do, we share our thoughts on each of the various topics for intermediate programmers.
Link to Episode 39’s Full Show Notes
T-Shirt Giveaway – The winner is…
Manrique Logan – please contact us to send us your ship-to information!
This Episode’s Survey
— Tired of the Carp… (@CatcheNameHere) February 19, 2016
Princess rap battle: GALADRIEL vs LEIA
NOTE: Some explicit language – NSFW
How to be an Intermediate Programmer
- How to Stay Motivated
- How to be Widely Trusted
- How to Tradeoff Time vs Space
- How to Stress Test
- How to Balance Brevity vs Abstraction
https://github.com/RobertLRead/HowToBeAProgrammer/blob/master/2-Intermediate/Personal-Skills/05-How%20to%20Balance%20Brevity%20and%20Abstraction.mdShout out to our friend Will – https://twitter.com/iamwillmadison
- How to Learn New Skills
- Learn to Type
- How to Do Integration Testing
- Communication Languages
- Heavy Tools
- How to Analyze Data
- How to Manage Development Time
- How to Manage Third Party Software Risks
- How to Manage Consultants
- How to Communicate the Right Amount
- How to Disagree Honestly and Get Away with it
- How to Tradeoff Quality Against Development Time
- How to Manage Software System Dependence
- How to Decide if Software is too Immature
- How to Make a Buy vs Build Decision
- How to Grow Professionally
- How to Evaluate Interviewees
- How to Know when to apply Fancy Computer Science
- How to Talk to Engineers
Resources We Like
How to be a Programmer: A Short, Comprehensive, and Personal Summary by Robert L Read
Make a Pull Request to get your thoughts in here:
Or buy your copy here from Amazon:
Succinctness is Power – Paul Graham
You Don’t Know JS
Want to know how fast you type?
Allen’s Typing Speed on the Microsoft Sculpt Ergonomic
specflow – Binding business requirements to .NET code
Tips for this Episode
Allen Underwood: Execution plan for a running query in Microsoft SQL Server
Preface: You can click a button in Microsoft SQL Server Management Studio (SSMS) to see the execution plan of a query to identify any performance problems. The biggest issue with this is that if there’s a query that NEVER returns, or takes an insanely long time to return, then you’re stuck waiting for the query to finish. This tip shows you how to find the ACTUAL (not estimated) query plan of the query that is actively running:
EXEC sp_who2 'active' -- Find the SPID of the query you're running
DECLARE @spid INT = 123 -- From above
SELECT EQP.query_plan, *
FROM sys.dm_exec_requests AS ER
CROSS APPLY sys.dm_exec_query_plan(ER.plan_handle) AS EQP
WHERE ER.session_id = @spid
Once that bottom query runs, you’ll be provided a link in the results grid that you can click to open up the graphical execution plan.
Michael Outlaw: Have Git ignore changes you make to a specific file like you didn’t make the changes, but still have it be part of the tracked files in Git.
Preface: Let’s say you have a connection string configuration file that you change to point to your local database. That config file needs to be tracked in Git, but you don’t want your changes to accidentally get committed and pushed up to the remote repo, then this command is for you.
git update-index --assume-unchanged /path/to/file
Joe Zack: Life Tip – Pay attention to the warnings in your IDE. It’s easy to get used to seeing several warnings and ignoring them because they’re not errors. Eventually a new one that actually matters will show up and by ignoring it, you could be creating heartache for yourself. If you can, resolve the warnings that are currently showing up so that if a new one surfaces, it’ll jump out at you like a sore thumb.