Welcome to the 320th #CodeNewbie Twitter Chat!
We are the most supportive community of programmers and people learning to code and we’re so excited to chat with you!
We are the most supportive community of programmers and people learning to code and we’re so excited to chat with you!
Before we kick off the chat, a few ground rules:
1. Be supportive
2. Be honest
3. Be nice
#CodeNewbie
1. Be supportive
2. Be honest
3. Be nice
#CodeNewbie
How does it work? We will post a question, discuss with you, then post a new question.
All questions will be labeled (ex: Q1) so please include the label in your answer (ex: A1) and the #CodeNewbie hashtag
All questions will be labeled (ex: Q1) so please include the label in your answer (ex: A1) and the #CodeNewbie hashtag
Feel free to respond directly to each other, just make sure to include the #CodeNewbie hashtag :)
In 45 minutes (ish), we’re going to do “Shoutouts.” If you’ve got some #programming news, an event, a blog post, tell us then!
In 45 minutes (ish), we’re going to do “Shoutouts.” If you’ve got some #programming news, an event, a blog post, tell us then!
Today we’re talking about technical debt. Inspired by our latest podcast with Nina Zakharenko. Let’s get started! #CodeNewbie
Q1: What do you think technical debt is? How would you define it? #CodeNewbie
Second question is on the way! #CodeNewbie
Q2: Technical debt can happen when code or technical processes build up over time. When does it make sense to put up with some technical debt? #CodeNewbie
Third question is coming up next! #CodeNewbie
Q3: What are some ways to manage technical debt? #CodeNewbie
Q4: Time for shoutouts! Tell us this week’s coding-related event, win, blog post, resource. GO! #CodeNewbie
That’s all we got for the #CodeNewbie twitter chat! See you next Wed 6PM PST/9PM EST for another #CodeNewbie Chat!