Packt convinced me to bite the d3.js bullet once more. Following the Data Visualization with d3.js book, I am now working on a video course aimed at advanced users.
It's going to be chock full of going into details about layouts, data manipulation, geography and other fun stuff. Definitely none of that "This is how you place a SVG element. This is how you bind data to elements. This is how you ..."
Pretty much all d3.js screencasts and courses I was able to find focus on beginners. There will be none of that here, I'm going to assume you've made at least three things with d3.js before tackling my videos.
So roughly the same experience I've got.
That said, I made a sample screencast last week to test the process out. The topic will fit towards the end of the course, where I try to explain the design part of visualisations.
Now, this is my first ever recording of a screencast. I have no idea what I'm doing. Do not be gentle! If there's something wrong, I have to know. Now!
If you tell me I suck six months from now when the course is published, it will be too late. Tell me my accent sucks, now. Tell me I speak at a funny pace, now. Tell me you can't understand what I'm saying, now.
And tell me I need a better mic. Then suggest which one I should get because this was recorded on the default apple headphones microphone.
Also, I'm going to need volunteers to beta read my scripts and beta watch the videos. The schedule says scripts will be coming out at a decent cadence of one every two weeks over the next two months. Then I'll be making the screencasts themselves over summer and the course should be out in September.
I'm making this for you guys. Help me make it awesomer.
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️