text
stringlengths
0
2.35k
[3381.46 --> 3384.10] a software developer and then you looked into gates and so on.
[3384.12 --> 3386.54] And that kind of helped you put this in place.
[3386.68 --> 3391.24] When I started my degree, the first course I did was those logic gates and everything was
[3391.24 --> 3391.46] scary.
[3391.58 --> 3392.34] Calculus was scary.
[3392.46 --> 3394.00] And then those gates, like what?
[3394.42 --> 3395.32] I don't know that.
[3395.48 --> 3396.70] Just let me pass that test.
[3396.76 --> 3397.24] Leave me alone.
[3397.24 --> 3401.98] And if it would be the other way around, start with the programming courses and then
[3401.98 --> 3406.60] you go about semiconductors and then you go about circuits and then you speak about gates.
[3406.76 --> 3410.62] It might have been more interesting and actually would make more sense.
[3410.70 --> 3411.60] Maybe for me, at least.
[3412.40 --> 3415.04] I think that's the path that people take accidentally.
[3415.52 --> 3419.44] Like those who do boot camps and then they actually eventually over like five, 10 years
[3419.44 --> 3423.34] become like systems engineers and are working on like kernel or TLS or something.
[3423.34 --> 3426.76] They don't know they're doing that, but that's kind of what they're doing, right?
[3426.80 --> 3428.08] They're looking back at the fundamentals.
[3428.54 --> 3428.62] Yeah.
[3428.72 --> 3429.18] I agree.
[3429.24 --> 3429.76] It's unpopular.
[3429.98 --> 3432.70] I don't know anyone who does that, but I think it's genius and we should.
[3432.90 --> 3435.02] We shouldn't open a university that teaches that way.
[3435.44 --> 3436.94] I feel like that's how my career has been.
[3437.10 --> 3439.74] I just have gone like down the stack further and further.
[3440.14 --> 3440.72] That's interesting.
[3440.88 --> 3441.04] Yeah.
[3441.22 --> 3441.82] It's been fun.
[3442.26 --> 3445.56] I've written like a few like operating system kernels, like toy kernels.
[3445.56 --> 3447.14] It was infuriating.
[3447.34 --> 3451.64] Modern processors are terrible, but mostly because they're so old.
[3452.18 --> 3454.60] Like, oh, maybe I have this code from the 70s.
[3454.64 --> 3458.82] I might need to run on my Intel 12th gen chip or something.
[3458.94 --> 3459.62] You never know.
[3459.92 --> 3463.68] It's like, no, Intel, I don't need to run code from 1980 on my new processor.
[3463.84 --> 3464.20] Thank you.
[3464.20 --> 3471.58] I like that too, though, that people can start higher up in the stack and still be doing things
[3471.58 --> 3473.18] without understanding everything.
[3473.62 --> 3475.08] Because I've seen it.
[3475.14 --> 3480.24] People help themselves back because they think, well, I just don't know all of this stuff.
[3480.34 --> 3484.86] And they don't know that they don't need to know it necessarily, which is why I say you
[3484.86 --> 3486.58] sometimes don't need to know a lot of the stuff.
[3486.68 --> 3488.42] Just sort of get on with it and try things.
[3488.82 --> 3490.24] But it doesn't work for everybody.
[3490.24 --> 3493.80] I think there's so many different styles and things that people appreciate.
[3493.80 --> 3494.84] Things that work.
[3495.02 --> 3498.16] And so wouldn't like to force it on everybody.
[3498.30 --> 3500.26] As we like to say, it depends.
[3501.54 --> 3506.66] And I'm afraid put down your goblets of red wine.
[3506.78 --> 3507.70] Yes, it was what?
[3507.78 --> 3509.02] It was definitely wine.
[3509.36 --> 3509.74] Yeah.
[3510.48 --> 3514.48] And put also away those sandwiches of miscellaneous.
[3515.84 --> 3517.20] No, there weren't any sandwiches.
[3517.58 --> 3520.28] No, let's just not do the sandwiches, but we'll do the wine bit.
[3520.28 --> 3523.38] And then keep the wine because I think it's blood.
[3523.80 --> 3524.56] Okay.
[3524.72 --> 3529.32] And that's all the time we have on today's Ghost Time.
[3529.74 --> 3531.30] Thanks for joining us, everybody.
[3531.98 --> 3534.20] See you next time and stay spoopy.
[3534.20 --> 3544.24] Do you have a spooky story that'll scare your fellow devs?
[3544.42 --> 3546.22] Let us know in the comments.
[3546.78 --> 3549.56] The link to discuss this episode is in your show notes.
[3550.14 --> 3552.58] And if you enjoyed this Halloween-themed edition of Go Time,
[3552.82 --> 3554.86] please do share the pod with your friends.
[3555.10 --> 3556.96] We appreciate you helping spread the word.
[3557.32 --> 3559.44] Thanks once again to our partners at Fastly.
[3559.44 --> 3562.88] They ship all of our pods super fast to wherever you listen.
[3563.18 --> 3565.00] Check them out at Fastly.com.
[3565.36 --> 3566.54] And to Fly.io.
[3567.12 --> 3569.78] Post your app servers and database closer to your users.
[3570.24 --> 3571.10] No ops required.
[3571.56 --> 3573.44] Learn more at Fly.io.
[3573.90 --> 3577.66] Next time on Go Time, Ian and Natalie are joined by Tim Smith
[3577.66 --> 3580.38] to discuss Go in medicine and biology.
[3581.08 --> 3583.44] Subscribe now if you haven't yet so you don't miss it.
[3583.44 --> 3585.84] We'll have that episode ready for you next week.
• Definition of Agile methodology as a mindset for making incremental progress
• Agile principles vs. frameworks (Scrum, Kanban, etc.) and importance of choosing the right framework for the team
• Agile vs. Waterfall approach: main differences and how to recognize each in practice
• Agile's focus on iterative and incremental progress with an emphasis on people motivation and collaboration
• Importance of stripping down Agile to its basic principles (lean) before implementing practices like Scrum or Kanban
• Agile vs Waterfall methodologies
• Characteristics of Agile: iterative, incremental, and adaptive process
• Scrum as a framework within Agile
• Choosing the right methodology or combination of methodologies for a team
• Importance of education and understanding different roles in an agile team (product manager, product owner, Scrum master)
• High-performance teams and employee well-being in Agile
• Full utilization of developers' skills and abilities
• Agile development vs waterfall, with more space for input and collaboration in agile
• Product manager role and expectations, including coming from a place of openness and honesty, and involving developers early on in the process
• Importance of regular feedback and communication, especially in remote teams, to maintain social interactions and connections among team members
• Agile ceremonies and practices, such as stand-ups, grooming sessions, and retrospectives, to facilitate collaboration and input from all team members
• Impact of remote work on agile culture and practices, requiring leaders to step up their game in terms of social interactions and communication
• Importance of human connection in remote/hybrid teams
• Benefits of having a "coffee hour" or casual gathering to foster relationships and trust among team members
• Strategies for connecting with colleagues, including meeting people from other teams and engaging in non-work-related activities
• Challenges and limitations of agile frameworks, including difficulties with loose deadlines and tight timelines
• Emphasis on returning to core principles and values rather than rigidly following specific methodologies.
• Misrepresentation of Agile and its true meaning