Podcasts about dev team

Caroline Marchal joins us to talk about the production of As Dusk Falls, her role as CEO/Designer at INTERIOR/NIGHT, and why romancing Astarion is so hard…Intro – 00:00Romancing Astarion – 01:30Connecting with Characters – 2:45Building a Dev Team – 7:39Work/Life Balance – 11:30COVID Production – 18:38 Streamer Dynamics and Surprising Stories – 24:00Why is the game set in Arizona? – 29:50What should new players know? – 36:30What’s next for Caroline and INTERIOR/NIGHT? – 38:45Games for inspiration? – 40:25Search our archive and join our community through https://dlgaming.net!

Gen AI for dev teams has been a focal point of conversation for the last few years, but the technology and application are both still very nascent. How can you find the best Gen AI use case for your team, and implement it safely?This week, our host Dan Lines sits down with Peter McKee, Vice President of Developer Relations and Community at Sonar. They explore the benefits and risks associated with Gen AI, and whether this new tooling is most impactful for junior or senior developers. Regardless of the persona, there needs to be an emphasis on quality control, static code analysis, and the new coaching strategies to help the influx of new code.Tune in to hear Dan and Peter offer practical advice for engineering leaders on safely experimenting with and integrating Gen AI tools to enhance productivity without sacrificing quality.Episode Highlights:00:33 The ins and out of being a VP of Developer Relations and Community04:48 The Importance of wisdom and experience when applying Gen AI08:32 Is there more of a risk for junior developers in this age?19:51 How tooling can help with the influx of Gen AI Code 26:02 The safe ways to roll out Gen AI to developers29:21 Where to start applying Gen AI for your team Show Notes:Peter McKee (@pmckee) / XPeter McKeeBetter Code & Better Software | Ultimate Security and Quality | SonarDownload The Engineering Leader's Guide to Accelerating Developer ProductivitySupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

What to do when the dev team is failing?

What is the minimum time to gain trust in dev team?

Wenn ihr regelmäßig Insert Moin hört, ist euch bestimmt nicht Crow Country entgangen. Der Indie-Survival Horror hat in der Horrorcommunity viel positives Feedback bekommen und auch Micha ist schwer begeistert von dem Spiel. Es trifft genau den richtigen Sweetspot aus Retro-Nostalgie, typischen Genreelementen und Modernisierungen, eingeflochten in eine starke Atmosphäre und einer interessanten Geschichte.

Hello and welcome back to another episode of The Dive Driven by Kia! Kobe, Azael, and Meteos discuss their fourth of July breaks, soft inting, and punishments toxic players should face in League. Then the guys are joined by Sope May, the Product Lead for Swarm and ask him every question about the new game mode! Week 4 of the LCS will be back on July 20th at 1PM PT/4PM ET where DIG takes on TL, but there will still be episodes of The Dive next week. Thanks for tuning in, and catch you all next week! 0:00 - Intro, July 4th break recap, and Elden Ring 8:03 - Soft inting 13:29 - What is soft inting & League toxicity 24:51 - Red side/blue side advantage/punishments in League  38:45 - Quick break/Intro Sope May, Swarm Product Lead 39:44 - What were the goals with Swarm? 41:43 - Can you play Swarm solo? 43:37 - Was visual clutter a concern? 47:34 - How do you measure success with Swarm? 49:17 - Champ mechanics  50:15 - How long will beating the game take? 51:46 - Any tips or tricks? 54:16 - Champ breakdowns & character builds in Swarm 1:04:44 - What's next for the Dev Team?

Is it important to shield your dev team from external disruption?

Diesmal plaudern wir mit dem Entwicklerteam Regina und Phil von Microbirds über den österreichischen Indie-Titel 'Dungeons of Hinterberg' - Microbird Games Hier ist der Link zu Steam (Playtest + Wishlist): https://store.steampowered.com/app/1983260/Dungeons_of_Hinterberg/

Joël shares his experience with the dry-rb suite of gems, focusing on how he's been using contracts to validate input data. Stephanie relates to Joël's insights with her preparation for RailsConf, discussing her methods for presenting code in slides and weighing the aesthetics and functionality of different tools like VS Code and Carbon.sh. She also encounters a CI test failure that prompts her to consider the implications of enforcing specific coding standards through CI processes. The conversation turns into a discussion on managing coding standards and tools effectively, ensuring that automated systems help rather than hinder development. Joël and Stephanie ponder the balance between enforcing strict coding standards through CI and allowing developers the flexibility to bypass specific rules when necessary, ensuring tools provide valuable feedback without becoming obstructions. Transcript: AD: We're excited to announce a new workshop series for helping you get that startup idea you have out of your head and into the world. It's called Vision to Value. Over a series of 90-minute working sessions, you'll work with a thoughtbot product strategist and a handful of other founders to start testing your idea in the market and make a plan for building an MVP. Join for all seven of the weekly sessions, or pick and choose the ones that address your biggest challenge right now. Learn more and sign up at tbot.io/visionvalue. STEPHANIE: Hello and welcome to another episode of the Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Stephanie Minn. JOËL: And I'm Joël Quenneville. And together, we're here to share a bit of what we've learned along the way. STEPHANIE: So, Joël, what's new in your world? JOËL: I've been working on a project that uses the dry-rb suite of gems. And one of the things we're doing there is we're validating inputs using this concept of a contract. So, you sort of describe the shape and requirements of this, like hash of attributes that you get, and it will then tell you whether it's valid or not, along with error messages. We then want to use those to eventually build some other sort of value object type things that we use in the app. And because there's, like, failure points at multiple places that you have to track, it gets a little bit clunky. And I got to thinking a little bit about, like, forget about the internal machinery. What is it that I would actually like to happen here? And really, what I want is to say, I've got this, like, bunch of attributes, which may or may not be correct. I want to pass them into a method, and then either get back a value object that I was hoping to construct or some kind of error. STEPHANIE: That sounds reasonable to me. JOËL: And then, thinking about it just a little bit longer, I was like, wait a minute, this idea of, like, unstructured input goes into a method, you get back something more structured or an error, that's kind of the broad definition of parsing. I think what I'm looking for is a parser object. And this really fits well with a style of processing popularized in the functional programming community called parse, don't validate the idea that you use a parser like this to sort of transform data from more loose to more strict values, values where you can have more assumptions. And so, I create an object, and I can take a contract. I can take a class and say, "Attempt to take the following attributes. If they're valid according to the construct, create this classroom." And it, you know, does a bunch of error handling and some...under the hood, dry-rb does all this monad stuff. So, I handled that all inside of the object, but it's actually really nice. STEPHANIE: Cool. Yeah, I had a feeling that was where you were going to go. A while back, we had talked about really impactful articles that we had read over the course of the year, and you had shared one called Parse, Don't Validate. And that heuristic has actually been stuck in my head a little bit. And that was really cool that you found an opportunity to use it in, you know, previously trying to make something work that, like, you weren't really sure kind of how you wanted to implement that. JOËL: I think I had a bit of a light bulb moment as I was trying to figure this out because, in my mind, there are sort of two broad approaches. There's the parse, don't validate where you have some inputs, and then you transform them into something stricter. Or there's more of that validation approach where you have inputs, you verify that they're correct, and then you pass them on to someone else. And you just say, "Trust me, I verified they're in the right shape." Dry-rb sort of contracts feel like they fit more under that validation approach rather than the parse, don't validate. Where I think the kind of the light bulb turned on for me is the idea that if you pair a validation step and an object construction step, you've effectively approximated the idea of parse, don't validate. So, if I create a parser object that says, in sort of one step, I'm going to validate some inputs and then immediately use them if they're valid to construct an object, then I've kind of done a parse don't validate, even though the individual building blocks don't follow that pattern. STEPHANIE: More like a parse and validate, if you will [laughs]. I have a question for you. Like, do you own those inputs kind of in your domain? JOËL: In this particular case, sort of. They're coming from a form, so yes. But it's user input, so never trust that. STEPHANIE: Gotcha. JOËL: I think you can take this idea and go a little bit broader as well. It doesn't have to be, like, the dry-rb-related stuff. You could do, for example, a JSON schema, right? You're dealing with the input from a third-party API, and you say, "Okay, well, I'm going to have a sort of validation JSON schema." It will just tell you, "Is this data valid or not?" and give you some errors. But what if you paired that with construction and you could create a little parser object, if you wanted to, that says, "Hey, I've got a payload coming in from a third-party API, validate it against this JSON schema, and attempt to construct this shopping cart object, and give me an error otherwise." And now you've sort of created a nice, little parse, don't validate pipeline which I find a really nice way to deal with data like that. STEPHANIE: From a user perspective, I'm curious: Does this also improve the user experience? I'm kind of wondering about that. It seems like it could. But have you explored that? JOËL: This is more about the developer experience. STEPHANIE: Got it. JOËL: The user experience, I think, would be either identical or, you know, you can play around with things to display better errors. But this is more about the ergonomics on the development side of things. It was a little bit clunky to sort of assemble all the parts together. And sometimes we didn't immediately do both steps together at the same time. So, you might sort of have parameters that we're like, oh, these are totally good, we promise. And we pass them on to someone else, who passes them on to someone else. And then, they might try to do something with them and hope that they've got the data in the right shape. And so, saying, let's co-locate these two things. Let's say the validation of the inputs and then the creation of some richer object happen immediately one after another. We're always going to bundle them together. And then, in this particular case, because we're using dry-rb, there's all this monad stuff that has to happen. That was a little bit clunky. We've sort of hidden that in one object, and then nobody else ever has to deal with that. So, it's easier for developers in terms of just, if you want to turn inputs into objects, now you're just passing them into one object, into one, like, parser, and it works. But it's a nicer developer experience, but also there's a little bit more safety in that because now you're sort of always working with these richer objects that have been validated. STEPHANIE: Yeah, that makes sense. It sounds very cohesive because you've determined that these are two things that should always happen together. The problems arise when they start to actually get separated, and you don't have what you need in terms of using your interfaces. And that's very nice that you were able to bundle that in an abstraction that makes sense. JOËL: A really interesting thing I think about abstractions is sometimes thinking of them as the combination of multiple other things. So, you could say that the combination of one thing and another thing, and all of a sudden, you have a new sort of combo thing that you have created. And, in this case, I think the combination of input validation and construction, and, you know, to a certain extent, error handling, so maybe it's a combination of three things gives you a thing you can call a parser. And knowing that that combination is a thing you can put a name on, I think, is really powerful, or at least it felt really powerful to me when that light bulb turned on. STEPHANIE: Yeah, it's kind of like the whole is greater than the sum of its parts. JOËL: Yeah. STEPHANIE: Cool. JOËL: And you and I did an episode on Specialized Vocabulary a while back. And that power of naming, saying that, oh, I don't just have a bunch of little atomic steps that do things. But the fact that the combination of three or four of them is a thing in and of itself that has a name that we can talk about has properties that we're familiar with, all of a sudden, that is a really powerful way to think about a system. STEPHANIE: Absolutely. That's very exciting. JOËL: So, Stephanie, what's new in your world? STEPHANIE: So, I am plugging away at my RailsConf talk, and I reached the point where I'm starting to work on slides. And this talk will be the first one where I have a lot of code that I want to present on my slides. And so, I've been playing around with a couple of different tools to present code on slides or, I guess, you know, just being able to share code outside of an editor. And the two tools I'm trying are...VS Code actually has a copy with syntax functionality in its command palette. And so, that's cool because it basically, you know, just takes your editor styling and applies it wherever you paste that code snippet. JOËL: Is that a screenshot or that's, like, formatted text that you can paste in, like, a rich text editor? STEPHANIE: Yeah, it's the latter. JOËL: Okay. STEPHANIE: That was nice because if I needed to make changes in my slides once I had already put them there, I could do that. But then the other tool that I was giving a whirl is Carbon.sh. And that one, I think, is pretty popular because it looks very slick. It kind of looks like a little Mac window and is very minimal. But you can paste your code into their text editor, and then you can export PNGs of the code. So, those are just screenshots rather than editable text. And I [chuckles] was using that, exported a bunch of screenshots of all of my code in various stages, and then realized I had a typo [laughs]. JOËL: Oh no! STEPHANIE: Yeah, so I have not got around to fixing that yet. That was pretty frustrating because now I would have to go back and regenerate all of those exports. So, that's kind of where I'm at in terms of exploring sharing code. So, if anyone has any other tools that they would use and recommend, I am all ears. JOËL: How do you feel about balancing sort of the quantity of code that you put on a slide? Do you tend to go with, like, a larger code slide and then maybe, like, highlight certain sections? Do you try to explain ideas in general and then only show, like, a couple of lines? Do you show, like, maybe a class that's got ten lines, and that's fine? Where do you find that balance in terms of how much code to put on a slide? Because I feel like that's always the big dilemma for me. STEPHANIE: Yeah. Since this is my first time doing it, like, I really have no idea how it's going to turn out. But what I've been trying is focusing more on changes between each slide, so the progression of the code. And then, I can, hopefully, focus more on what has changed since the last snippet of code we were looking at. That has also required me to be more fiddly with the formatting because I don't want essentially, like, the window that's containing the code to be changing sizes [laughs] in between slide transitions. So, that was a little bit finicky. And then, there's also a few other parts where I am highlighting with, like, a border or something around certain texts that I will probably pause and talk about, but yeah, it's tough. I feel like I've seen it done well, but it's a lot harder to and a lot more effort to [laughs] do in practice, I'm finding. JOËL: When someone does it well, it looks effortless. And then, when somebody does it poorly, you're like, okay, I'm struggling to connect with this talk. STEPHANIE: Yep. Yep. I hear that. I don't know if you would agree with this, but I get the sense that people who are able to make that look effortless have, like, a really deep and thorough understanding of the code they're showing and what exactly they think is important for the audience to pay attention to and understand in that given moment in their talk. That's the part that I'm finding a lot more work [laughs] because just thinking about, you know, the code I'm showing from a different lens or perspective. JOËL: How do you sort of shrink it down to only what's essential for the point that you're trying to make? And then, more broadly, not just the point you're trying to make on this one slide, but how does this one slide fit into the broader narrative of the story you're trying to tell? STEPHANIE: Right. So, we'll see how it goes for me. I'm sure it's one of those things that takes practice and experience, and this will be my first time, and we'll learn something from it. JOËL: That's exciting. So, this is RailsConf in Detroit this year, I believe, May 7th through 9th. STEPHANIE: Yep. That's right. So, recently on my client work, I encountered a CI failure on a PR of mine that I was surprised by. And basically, I had introduced a new association on a model, and this CI failure was saying like, "Hey, like, we see that you introduced this association. You should consider adding this to the presenter for this model." And I hadn't even known that that presenter existed [laughs]. So, it was kind of interesting to get a CI failure nudging me to consider if I need to be, like, making a different, you know, this other change somewhere else. JOËL: That's a really fun use of CI. Do you think that was sort of helpful for you as a newer person on that codebase? Or was it more kind of annoying and, like, okay, this CI is over the top? STEPHANIE: You know, I'm not sure [laughs]. For what it's worth, this presenter was actually for their admin dashboard, essentially. And so, the goal of what this workflow was trying to do was help folks who are using the admin dashboard have, like, all of the capabilities they need to do that job. And it makes sense that as you add behavior to your app, sometimes those things could get missed in terms of supporting, you know, not just your customers but developers, support product, you know, the other users of your app. So, it was cool. And that was, you know, something that they cared enough to enforce. But yeah, I think there maybe is a bit of a slippery slope or at least some kind of line, or it might even be pretty blurry around what should our test failures really be doing. JOËL: And CI is interesting because it can be a lot more than just tests. You can run all sorts of things. You can run a linter that fails. You could run various code quality tools that are not things like unit tests. And I think those are all valid uses of the CI process. What's interesting here is that it sounds like there were two systems that needed to stay in sync. And this particular CI check was about making sure that we didn't accidentally introduce code that would sort of drift apart in those two places. Does that sound about right? STEPHANIE: Yeah, that does sound right. I think where it gets a little fuzzy, for me, is whether that kind of check was for code quality, was for a standard, or for a policy, right? It was kind of saying like, hey, like, this is the way that we've enforced developers to keep those two things from drifting. Whereas I think that could be also handled in different ways, right? JOËL: Yeah. I guess in terms of, like, keeping two things in sync, I like to do that at almost, like, a code level, if possible. I mean, maybe you need a single source of truth, and then it just sort of happens automatically. Otherwise, maybe doing it in a way that will yell at you. So, you know, maybe there's a base class somewhere that will raise an error, and that will get caught by CI, or, you know, when you're manually testing and like, oh yeah, I need to keep this thing in sync. Maybe you can derive some things or get fancy with metaprogramming. And the goal here is you don't have a situation where someone adds a new file in one place and then they accidentally break an admin dashboard because they weren't aware that you needed these two files to be one-to-one. If I can't do it just at a code level, I have done that before at, like, a unit test level, where maybe there's, like, a constant somewhere, and I just want to assert that every item in this constant array has a matching entry somewhere else or something like that, so that you don't end up effectively crashing the site for someone else because that is broken behavior. STEPHANIE: Yeah, in this particular case, it wasn't necessarily broken. It was asking you "Hey, should this be added to the admin presenter?" which I thought was interesting. But I also hear what you're saying. It actually does remind me of what we were talking about earlier when you've identified two things that should happen, like mostly together and whether the code gives you affordances to do that. JOËL: So, one of the things you said is really interesting, the idea that adding to the presenter might have been optional. Does that mean that CI failed for you but that you could merge anyway, or how does that work? STEPHANIE: Right. I should have been more clear. This was actually a test failure, you know, that happened to be caught by CI because I don't run [laughs] the whole test suite locally. JOËL: But it's an optional test failure, so you're allowed to let that test fail. STEPHANIE: Basically, it told me, like, if I want this to be shown in the presenter, add it to this method, or if not, add it to...it was kind of like an allow list basically. JOËL: I see. STEPHANIE: Or an ignore list, yeah. JOËL: I think that kind of makes sense because now you have sort of, like, a required consistency thing. So, you say, "Our system requires you...whenever you add a file in this directory, you must add it to either an allow list or an ignore list, which we have set up in this other file." And, you know, sometimes you might forget, or sometimes you're new, and it's your first time adding a file in this directory, and you didn't remember there's a different place where you have to effectively register it. That seems like a reasonable check to have in place if you're relying on these sort of allow lists for other parts of the system, and you need to keep them in sync. STEPHANIE: So, I think this is one of the few instances where I might disagree with you, Joël. What I'm thinking is that it feels a bit weird to me to enforce a decision that was so far away from the code change that I made. You know, you're right. On one hand, I am newer to this codebase, maybe have less of that context of different features, things that need to happen. It's a big app. But I almost think this test reinforces this weird coupling of things that are very far away from each other [laughs]. JOËL: So, it's maybe not the test itself you object to rather than the general architecture where these admin presenters are relying on these other objects. And by you introducing a file in a totally different part of the app, there's a chance that you might break the admin, and that feels weird to you. STEPHANIE: Yeah, that does feel weird to me. And then, also that this implementation is, like, codified in this test, I guess, as opposed to a different kind of, like, acceptance test, rather than specifying specifically like, oh, I noticed, you know, you didn't add this new association or attribute to either the allow list or the ignore list. Maybe there is a more, like, higher level test that could steer us in keeping the features consistent without necessarily dictating, like, that it needs to happen in these particular methods. JOËL: So, you're talking something like doing an integration test rather than a unit test? Or are you talking about something entirely different? STEPHANIE: I think it could be an integration test or a system test. I'm not sure exactly. But I am wondering what options, you know, are out there for helping keeping standards in place without necessarily, like, prescribing too much about, like, how it needs to be done. JOËL: So, you used the word standard here, which I tend to think about more in terms of, like, code style, things like that. What you're describing here feels a little bit less like a standard and more of what I would call a code invariant. STEPHANIE: Ooh. JOËL: It's sort of like in this architecture the way we've set up, there must always be sort of one-to-one matching between files in this directory and entries in this array. Now, that's annoying because they're sort of, like, two different places, and they can vary independently. So, locking those two in sync requires you to do some clunky things, but that's sort of the way the architecture has been designed. These two things must remain one-to-one. This is an invariant we want in the app. STEPHANIE: Can you define invariant for me [laughs], the way that you're using it here? JOËL: Yeah, so something that is required to be true of all elements in this class of things, sort of a rule or a law that you're applying to the way that these particular bits of code need to behave. So, in this case, the invariant is every file in this directory must have a matching entry in this array. There's a lot of ways to enforce that. The sort of traditional idea is sort of pushing a lot of that checking...they'll sometimes talk about pushing errors to the left. So, if you can handle this earlier in the sort of code execution pipeline, can you do it maybe with a type system if you're in a type language? Can you do it with some sort of input validation at runtime? Some languages have the concept of contracts, so maybe you enforce invariants using that. You could even do something really ad hoc in Ruby, where you might say, "Hey, at boot time, when we load this particular array for the admin, just load this directory. Make sure that the entries in the array match the entries in the directory, and if they don't, raise an error." And I guess you would catch that probably in CI just because you tried to run your test suite, and you'd immediately get this boot error because the entries don't match. So, I guess it kind of gets [inaudible 22:36] CI, but now it's not really a dedicated test anymore. It's more of, like, a property of the system. And so, in this case, I've sort of shifted the error checking or the checking of this invariant more into the architecture itself rather than in, like, things that exercise the architecture. But you can go the other way and say, "Well, let's shift it out of the architecture into tests," or maybe even beyond that, into, like, manual QA or, you know, other things that you can do to verify it. STEPHANIE: Hmm. That is very compelling to me. JOËL: So, we've been talking so far about the idea of invariants, but the thing about invariants is that they don't vary. They're always true. This is a sort of fundamental rule of how this system works. The class of problems that I often struggle with how to deal with in these sorts of situations are rules that you only sometimes want to apply. They're not consistent. Have you ever run into things like that? STEPHANIE: Yeah, I have. And I think that's what was compelling to me about what you were sharing about code invariance because I wasn't totally convinced this particular situation was a very clear and absolute rule that had been decided, you know, it seemed a little bit more ambiguous. When you're talking about, like, applying rules that sometimes you actually don't want to apply, I think of things like linters, where we want to disable, you know, certain rules because we just can't get around implementing the way we want to while following those standards. Or maybe, you know, sometimes you just have to do something that is not accessible [laughs], not that that's what I would recommend, but in the case where there aren't other levers to change, you maybe want to disable some kind of accessibility check. JOËL: That's always interesting, right? Because sometimes, you might want, like, the idea of something that has an escape hatch in it, but that immediately adds a lot of complexity to things as well. This is getting into more controversial territory. But I read a really compelling article by Jeroen Engels about how being able to, like, locally disable your linter for particular methods actually makes your code, but also the linter itself, a worse tool. And it really kind of made me rethink a little bit of how I approach linters as a tool. STEPHANIE: Ooh. JOËL: And what makes sense in a linter. STEPHANIE: What was the argument for the linter being a worse tool by doing that? JOËL: You know, it's funny that you ask because now I can't remember, and it's been a little while since I've read the article. STEPHANIE: I'll have to revisit it after the show [laughs]. JOËL: Apparently, I didn't do the homework for this episode, but we'll definitely link to that article in the show notes. STEPHANIE: So, how do you approach either introducing a new rule to something like a linter or maybe reconsidering an existing rule? Like, how would you go about finding, like, consensus on that from your team? JOËL: That varies a lot by organizational culture, right? Some places will do it top-down, some of them will have a broader conversation and come to a consensus. And sometimes you just straight up don't get a choice. You're pulling in a tool like standard rb, and you're saying, "Look, we don't want to have a discussion about every little style thing, so whatever, you know, the community has agreed on for the standard rb linter is the style we're using. There are no discussions. Do what the linter tells you." STEPHANIE: Yeah, that's true. I think I have to adapt to whatever, you know, client culture is like when I join new projects. You know, sometimes I do see people being like, "Hey, I think it's kind of weird that we have this," or, "Hey, I've noticed, for example, oh, we're merging focused RSpec tests. Like, let's introduce a rule to make sure that that doesn't happen." I also think that a different approach is for those things not to be enforced at all by automation, but we, you know, there are still guidelines. I think the thoughtbot guides are an example of pretty opinionated guidelines around style and syntax. But I don't think that those kinds of things would, you know, ever be, like, enforced in a way that would be blocking. JOËL: Those are kind of hard because they're not as consistent as you would think, so it's not a rule you can apply every time. It's more of a, here's some things to maybe keep in mind. Or if you're writing code in this way, think about some of the edge cases that might happen, or don't default to writing it in this way because things might go wrong. Make sure you know what you're doing. I love the phrase, "Must be able to justify this," or sometimes, "Must convince your pair that this is okay." So, default to writing in style A, avoid style B unless you can have a compelling reason to do so and can articulate that on your PR or, you know, convince your pair that that's the right way to go. STEPHANIE: Interesting. It's kind of like the honor system, then [laughs]. JOËL: And I think that's sort of the general way when you're working with developers, right? There's a lot of areas where there is ambiguity. There is no single best way to do it. And so, you rely on people's expertise to build systems that work well. There are some things where you say, look, having conversations about these things is not useful. We want to have some amount of standardization or uniformity about certain things. Maybe there's invariance you want to hold. Maybe there's certain things we're, like, this should never get to production. Whenever you've got these, like, broad sweeping statements about things should be always true or never true, that's a great time to introduce something like a linting rule. When it's more up to personal judgment, and you just want to nudge that judgment one way or another, then maybe it's better to have something like a guide. STEPHANIE: Yeah, what I'm hearing is there is a bit of a spectrum. JOËL: For sure. From things that are always true to things that are, like, sometimes true. I think I'm sort of curious about the idea of going a level beyond that, though, beyond things like just code style or maybe even, like, invariance you want to hold or something, being able to make suggestions to developers based off the code that is written. So, now you're applying more like heuristics, but instead of asking a human to apply those heuristics at code review time and leave some comments, maybe there's a way to get automated feedback from a tool. STEPHANIE: Yeah, I think we had mentioned code analysis tools earlier because some teams and organizations include those as part of their CI builds, right? And, you know, even Brakeman, right? Like, that's an analysis tool for security. But I can't recall if I've seen an organization use things like Flog metrics which measure code complexity in things like that. How would you feel if that were a check that was blocking your work? JOËL: So, I've seen things like that be used if you're using, like, the Code Climate plugin for GitHub. And Code Climate internally does effectively flog and other things that are fancier on your code quality. And so, you can set a threshold to say, hey, if complexity gets higher than a certain amount, fail the build. You can also...if you're doing things via GitHub, what's nice is that you can do effectively non-blocking comments. So, instead of failing CI to say, "Hey, this method looks really complex. You cannot merge until you have made this method less complex," maybe the sort of, like, next step up in ambiguity is to just leave a comment on a PR from a tool and say, "Hey, this method here is looking really complex. Consider breaking it up." STEPHANIE: Yeah, there is a tool that I've seen but not used called Danger, and its tagline is, Stop saying, "You forgot to..." in code review [laughs]. And it basically does that, what you were saying, of, like, leaving probably a suggestion. I can imagine it's blocking, but a suggestive comment that just automates that rather than it being a manual process that humans have to remember or notice. JOËL: And there's a lot of things that could be specific to your organization or your architecture. So, you say, "Hey, you introduced a file here. Would you consider also making an entry to this presenter file so that it's editable on the admin?" And maybe that's a better place to handle that. Just a comment. But you wouldn't necessarily want every code reviewer to have to think about that. STEPHANIE: So, I do think that I am sometimes not necessarily suspicious, but I have also seen tools like that end up just getting in the way, and it just becomes something you ignore. It's something you end up always using the escape hatch for, or people just find ways around it because they're harming more than they're helping. Do you have any thoughts about how to kind of keep those things in check and make sure that the tools we introduce genuinely are kind of helping the organization do the right thing rather than kind of being these perhaps arbitrary blockers? JOËL: I'm going to throw a fancy phrase at you. STEPHANIE: Ooh, I'm ready. JOËL: Signal-to-noise ratio. STEPHANIE: Whoa, uh-huh. JOËL: So, how often is the feedback from your tool actually helpful, and how often is it just noise that you have to dismiss, or manually override, or things like that? At some point, the ratio becomes so much that you lose the signal in all the noise. And so, maybe you even, like, because you're always just ignoring the feedback from this tool, you accidentally start overriding things that would be genuinely helpful. And, at that point, you've got the worst of both worlds. So, sort of keeping track on what that ratio is, and there's not, like, a magic number. I'm not going to tell you, "Oh, this is an 80/20 principle. You need to have, you know, 80% of the time it's useful and only 20% of the time it's not useful." I don't have a number to give you, but keeping track on maybe, you know, is it more often than not useful? Is your team getting to the point where they're just ignoring feedback from this tool? And thinking in terms of that signal versus that noise, I think is useful—to go back to that word again, heuristic for managing whether a tool is still helpful. STEPHANIE: Yeah. And I would even go on to say that, you know, I always appreciate when people in leadership roles keep an eye on these things. And they're like, "Oh, I've been hearing that people are just totally numb to this tool [laughs]" or, you know, "There's no engagement on this. People are just ignoring those signals." Any developer impacted by this, it is valid to bring it up if you're getting frustrated by it or just finding yourself, you know, having all of these obstacles getting in the way of your development process. JOËL: Sometimes, this can be a symptom that you're mixing too many classes of problems together in one tool. So, maybe there are things that are, like, really dangerous to your product to go live with them. Maybe it's, you know, something like Brakeman where you're doing security checks, and you really, ideally, would not go to production with a failing security check. And then, you've got some random other style things in there, and you're just like, oh yeah, whatever, it's this tool because it's mostly style things but occasionally gives you a security problem. And because you ignore it all the time, now you accidentally go to production with a security problem. So, splitting that out and say, "Look, we've got blocking and unblocking because we recognize these two classes of problems can be a helpful solution to this problem." STEPHANIE: Joël, did you just apply an object-oriented design principle to an organizational system? [laughter] JOËL: I may be too much of a developer. STEPHANIE: Cool. Well, I really appreciate your input on this because, you know, I was just kind of mulling over, like, how I felt about these kinds of things that I encounter as a developer. And I am glad that we got to kind of talk about it. And I think it gives me a more expanded vocabulary to, you know, analyze or reflect when I encounter these things on different client organizations. JOËL: And every organization is different, right? Like, you've got to learn the culture, learn the different elements of that software. What are the things that are invariant? What are the things that are dangerous that we don't want to ship without? What are the things that we're doing just for consistency? What are things which are, like, these are culturally things that we'd like to do? There's all these levels, and it's a lot to pick up. STEPHANIE: Yeah. At the end of the day, I think what I really liked about the last thing you said was being able to identify the problem, like the class of problem, and applying the right tool for the right job. It helps me take a step back and perhaps even think of different solutions that we might not have thought about earlier because we had just gotten so used to the one way of enforcing or checking things like that. JOËL: On that note, shall we wrap up? STEPHANIE: Let's wrap up. Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeee!!!!!! AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at: tbot.io/referral. Or you can email us at: referrals@thoughtbot.com with any questions.

Bio: For those who love to experience music, look no further than Supertask. With deep roots in hip-hop and a focus towards immersion, Supertask creates sonic landscapes that dance between the intensity and stillness of the human consciousness. With a background in IT, Supertask frequently uses code and programming in his artistic vision, and the idea of infinity consumes his musical escapism offerings. A vision that his loyal community, the Dev Team, are directly involved in. Blending both analog and digital sound design, his unique approach has proven to be a driving force in the forward progression of electronic music. Through soundscapes that feel sentient, interactive live streams, and mind-bending visuals, Supertask is changing the way that we consume art. Supertask Links News: Single Release: 4/21 Collaboration EP With "Seeded Vision" comes out this summer. Show Takeaways: Brain-computer interfaces have the potential to revolutionize music creation, but there are challenges to overcome, such as data transfer and the role of musical knowledge. AI can be a useful tool in music production, from generating lyrics to providing information about plugins and audio files. Creativity is subjective, and the definition of creativity can vary from person to person. AI can be creative in its ability to generate music, but a sense of ownership and sentimental value may be lacking. Imperfections and randomness can add depth and authenticity to music production, and tools like Eurorack can provide unique sounds and experiences. Language has limitations in expressing emotions in music, and the complexity of defining concepts like holes and chairs highlights the challenges of categorization. Chapters: 00:00 Introduction 00:35 Understanding Supertask 04:08 AI and Music in the Subset of Noise 07:59 Human Resolution with Color and Sound 09:39 Resolution and Possibilities in Audio 11:04 The Perception of Music and Noise 12:08 Cultural Influence on Music Perception 13:20 The Universality of Music Perception 14:25 Microtonal Scales and Musical Perception 15:21 Exploring Microtonal Music 19:22 The Concept of Simulation Theory 25:10 The Possibility of Living in a Simulation 28:08 Exploring Music and Visual Art 29:27 Scripted Looping in Music Production 34:29 The Ego and Live Performances 36:15 The Challenge of Performing Live Electronic Music 37:38 The Limitations of Live Performances 37:39 The Role of Input Devices in Music Expression 38:24 Exploring the Potential of Brain-Computer Interfaces 39:05 Speculating on the Future of Music Creation 40:00 The Role of Musical Knowledge in Brain-Computer Interfaces 40:49 The Challenges of Data Transfer in Brain-Computer Interfaces 42:19 The Role of AI in Brain-Computer Interfaces 42:50 The Increasing Predictability of Human Behavior 45:01 Using AI in Music Production 47:16 The Usefulness of AI in Answering Questions and Providing Information 48:34 The Definition and Nature of Creativity 51:17 The Subjectivity of Intellectual Property and Creativity 52:09 Exploring Unreal Engine and its Potential in Music Visuals 53:18 The Potential Disruption of AI and Sora in the Film Industry 54:00 The Limitations of AI in Music Generation 57:52 The Importance of Imperfection in Music Production 58:18 Using Randomness and Mistakes in Sound Design 01:00:19 The Appeal of Eurorack and Imperfections in Music 01:02:41 The Sense of Ownership and Sentimental Value in Music 01:04:34 The Potential of AI in Music Creation 01:06:28 The Interactive and Symbiotic Nature of Music Production 01:09:04 The Difficulty of Expressing Authenticity Through AI 01:11:36 The Limitations of Language in Expressing Emotions in Music 01:12:02 The Complexity of Defining Concepts like Holes and Chairs 01:14:04 The Process vs. the Final Product in Music Creation 01:14:46 Future Plans and Projects  

Welcome to the 2nd episode of Sumo Group x Game Dev London podcast! In this episode, Jimmy Bowers, Jennifer Marshall and Chris Groves will be talking about embedding community management in your dev team.

Kate and Ryan are joined by Anu Smalley to discuss the ways in which Developers can undermine their team's Scrum practice and Agile transformation

How can we break down dev team silos for increased communication and a better-quality end product? Reversing Conway's Law is one way to go about it, and today's guest has a wealth of experience on how to do just that! Krishna Bala is the Senior VP of Engineering at Proscia, a medical imaging startup that is fighting cancer with AI-enabled Digital Pathology. Using the case study of Proscia itself, Krishna outlines the benefits of building common elements across teams and handling change management when reorganizing roles and teams.There is also an in-depth explanation of Conway's Law as well, for those tech companies looking to break down the barriers to better communication between their teams and not be limited in their output by their organizational structure. Higher quality product by design awaits. We just have to reverse a law to do it. Krishna's knowledge of how to build your organization to achieve its goals will surely be appreciated. Please join us."As humans, I think we're just comfortable staying in that hierarchy, staying in our own little system. Work is hard enough, challenging enough that you basically say, 'Okay, this is my box; I'm going to innovate within that box'." ~ Krishna BalaIn This Episode:- Why are silos bad? - What is Conway's Law?- Reversing Conway's Law: what does that entail?- What good comes from breaking down siloes?- How is Krishna using this thinking in his work today?- Organizing a deliberate common core team - Changing the tires while the car is moving!- Appreciating the importance of change management- Figuring out the release cadence for your common core teamAnd more!Connect with Krishna Bala:- LinkedIn - https://www.linkedin.com/in/kbala97/- Website - https://proscia.com/Connect with Debbie Madden:- Website - https://www.stride.build/- LinkedIn - https://www.linkedin.com/in/debbiemadden1/- LinkedIn Page - https://www.linkedin.com/company/stride-build/

What do you do when your Scrum Master's understanding of their role seems to be less about acting as a servant leader to the Scrum Team and more about making the team to work in a way that is most convenient for them? In this episode of the podcast, Jeff Howey joins me to talk through the real-life case of a Scrum Master who seems to have lost their way. Here are some of the concerns shared in the podcast: - Dev Team is offshore and holds a Daily Scrum before 8 AM in Scrum Master's time zone. Scrum Master requires that they hold a second Daily Scrum to provide status to Scrum Master. - SM does not attend Sprint Planning. They require the PO to run it. - SM requires the PO to run the Retrospective. All topics must be submitted in advance of the meeting and must be positive comments (not negative). - Scrum Master does not like the way the Developers have set up their Task Board and requires that they change it to a format that works better for the Scrum Master. During the conversation, Jeff and I unpack these and a number of additional concerns, talk through how they are out of alignment with Scrum and the role of the Scrum Master, and discuss suggestions we'd offer to help reset the understanding of what it means to be a Scrum Master who acts as a servant leader for a Scrum Team. If you'd like to contact Jeff Howey. LinkedIn: www.linkedin.com/in/jeffhowey/ Newsletter: https://www.linkedin.com/newsletters/the-agile-alchemist-7018992829091778560

In this episode, we get into the nitty gritty of front line and emergency services solutions in places where conditions are less than ideal. Our two guests from Delta Dev Team, Monti Leija, CEO and Robert Futch, CFO, sit down and discuss what led them to create the number one blood storage solution to be used in emergency situations. For more information subscribe to Running on Ice the newsletter or podcast. Follow the Running on Ice Podcast Other FreightWaves Shows Learn more about your ad choices. Visit megaphone.fm/adchoices

How to lead your dev team?

In this episode of "Status Go," Jeff Ton speaks with Ramiro Berrelleza, CEO of Okteto, about the significance of investing in your development team, offering insights on industry trends and actionable advice for technology leaders to enhance productivity and innovation. The post Status Go: Ep. 229 – Why Invest in your Dev Team | Ramiro Berrelleza appeared first on InterVision Systems.

How do you help a dev team to stop doing things in an old way?

This episode features Graham Haythornthwaite, VP Of Engineering at Wonde. Questions covered include:Tell us a bit about you, background, journey in tech, what do you work on in your current role?What do you like about leading an engineering team?What prompted your organization to shift to the 4 day work week and what has been the turnout? Pros and cons?Your dev team has recently doubled in size, how do you ensure success when scaling a dev team? Anything to avoid?Graham is VP of Engineering at Wonde where he has helped double the size of the engineering team and successfully transition their practices to embrace a 4 day week. Prior to joining Wonde he created successful software product teams across multiple industries including Unified Communications for Finance and Emergency Services, Energy, Internal IT and EdTech.

Mein heutiger Studiogast ist Moritz Wasserek, Co-Founder von IROIN, Deutschlands größter Influencer Marketing Software-Anbieter wie er sagt. Moritz ist ein OG und hat sich mit der Influencer Marketing Industrie von der technischen Seite sehr früh beschäftigt und war von Anfang an von der Entwicklung von Influencer Marketing auf YouTube etc. fasziniert und hat das Potenzial erkannt. Er selbst hat als Student viel mit Blogs, YouTube und Amazon Affiliate Marketing experimentiert. Mit IROIN hat er deswegen früh den Fokus auf die damals neu entstehende Influencer Marketing Industrie gelegt. In unserem Gespräch gibt Moritz spannende Einblicke in die Entstehung von IROIN und seine persönliche Begeisterung für digitale Trends. Er erklärt detailliert die Funktionen seiner Influencer Marketing Software und weil er großes Potenzial für automatisierte Lösungen durch KI sieht, hat sein Dev Team auch gleich ein paar coole Features eingebaut.Weitere Themen sind Best Practices für Unternehmen fürs Influencer Marketing, Trends in der Branche sowie die Community-Events, die IROIN monatlich hält. Moritz ist ein überzeugter Pionier des Influencer Marketings, der mit IROIN früh auf diesen Trend gesetzt hat und die Branche prägt. Ein sehr spannender Diskurs für alle, die sich für Influencer Marketing interessieren. Hosted on Acast. See acast.com/privacy for more information.

Dans le quatrième épisode de notre série Shots, nous nous concentrons sur le cœur de l'Agile : la Dev Team. Apprenez comment une Dev Team Agile travaille de manière collaborative pour créer des solutions innovantes et de valeur. Quel que soit votre rôle dans le développement de produits - que vous soyez développeur, testeur, designer, ou simple curieux du monde Agile - cet épisode est pour vous. Rejoignez-nous pour une exploration approfondie de ce qui fait battre le cœur de l'Agilité. Rejoignez-nous sur Agile Tonic pour explorer l'agilité avec des experts du domaine. N'oubliez pas de vous abonner et de nous laisser une note pour soutenir le podcast. Suivez-nous sur les réseaux sociaux pour rester informé des nouveaux épisodes et échanger avec notre communauté : Twitter : @AgileTonic LinkedIn : https://www.linkedin.com/company/agiletonic/ Instagram : https://www.instagram.com/agile_tonic/ Votre soutien nous permet de continuer à vous proposer des épisodes de qualité. Merci de faire partie de notre aventure agile !  

Amid the escalating buzz surrounding AI tools, many development teams grapple with deciding which ones suit their needs best, when to adopt them, and the potential risks of not doing so. As AI continues to pose more questions than answers, the fear of falling behind the competition lurks for many.This week's episode of Dev Interrupted aims to dispel these uncertainties by welcoming CodiumAI's founder & CEO, Itamar Friedman. In one of our most illuminating discussions this year, Itamar pierces through the AI hype, explaining what AI tools bring to the table, how to discern the ones that would truly augment your dev teams, and the strategies to efficiently identify and experiment with new tools.Beyond the allure of AI, Itamar doesn't shy away from addressing its pitfalls and adversarial risks. He also probes into the future of the developer's role in an increasingly AI-driven landscape, answering the question: “Will there be developers in 10 years?”Show Notes:Learn more about CodiumAIRead CodiumAI's blogCodium's LinkedIn: https://www.linkedin.com/company/codiumaiItamar's LinkedIn: https://www.linkedin.com/in/itamarf/Itamar's Twitter: @itamar_marSupport the show: Subscribe to our Substack Follow us on YouTube Leave us a review Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Want to try LinearB? Book a Demo & use discount code "Dev Interrupted Podcast"

EPISODE SUMMARYProduct development is the backbone of software companies, so nurturing your dev team is paramount to success. Despite this, the knee-jerk response to product development usually measures the KPIs for an optimal go-to-market. However, the secret to productivity lies in numbers and developer experience.In this week's episode of Scale Your SaaS, DevStats Founder, and DevSquad CEO Phil Alvez shares the ingredients for successful product development with Host and B2B SaaS Sales coach, Matt Wolach. He highlights the importance of culture and encourages minimalism in software development. Set your developers for success and enjoy the domino effect on your bottom line by watching the video!PODCAST-AT-A-GLANCEPodcast: Scale Your SaaS with Matt WolachEpisode: Episode No. 271, "How to Make Sure Your Dev Team Productivity is Maximized - with Phil Alves"Host: Matt Wolach, a B2B SaaS sales coach, Entrepreneur, and InvestorGuest: Phil Alves, Founder at DevStats and CEO at DevSquadTOP TIPS FROM THIS EPISODEFocus on Good Developer ExperienceMake Culture the Bedrock of Your CompanyTalk to Customers to Understand the ProblemCreate Solutions that Target Pain PointsAvoid Copying Bigger CompaniesEPISODE HIGHLIGHTSSmaller Companies Have Lesser BureaucracyThe Best Software Leaders are Expert Visionaries Software Creation will Become Niched TOP QUOTESPhil Alves[7:55] "I want to make my firm like the Disney for software developers."[13:20] "I'm not talking to my customers to understand the solution. I'm talking to my customer to understand the problem.[14:17] "I don't believe we can build software by using democracy."Matt Wolach[12:22] "Once we found the culture that worked for us, it just became so strong within our organization. It was something that we could hire to, something we could train to, something that people just kind of felt, and it helped them become more passionate for the business and what the business was doing."LEARN MORETo learn more about DevStats, visit: https://www.devstats.com/To learn more about DevSquad, visit:https://devsquad.com/You can also find Phil Alves  on LinkedIn at: https://www.linkedin.com/in/philalves/enFor more about how host Matt Wolach helps software companies achieve maximum growth, visit https://mattwolach.com/Get even more tips by following Matt elsewhere: Sales Tips LinkedIn Twitter Instagram

Online multiplayer ranking systems, a ladder of esports opportunity, VR support, car classes, beta roll-outs and modding tools. It's all covered, direct from the source, in this latest Traxion Podcast Episode covering the latest Rennsport and ESL R1 updates.How is the tyre model implemented, what will the second season of ESL R1 look like and where will mods be hosted?It's all here, and more, thanks to our recent trip to Rennsport Summit 2 and ESL R1 Spring Major in Munich. Guests on this episode are:Morris Hebecker - CEO RennsportRoger Lodewick - President Sports Games, EFG, ESLKrzysztof Szczech - Lead Programmer, RennsportWatch our Praga R1 and Monza vehicle handling impressions/gameplay: https://www.youtube.com/watch?v=EOY7t4vLTMcWatch our Rennsport Mod gameplay/hands-on and event opinions: https://www.youtube.com/watch?v=x77pYaPCpfU&t=310sThe latest Rennsport news: https://traxion.gg/category/games/rennsport/If you'd like to hear more episodes like this one, please follow, like and subscribe on your podcast app of choice. If you enjoyed this episode, please leave a comment on the Traxion.GG website or a review. Your feedback is invaluable and helps us to create more episodes in the future.Fanatec affiliate link: https://geni.us/txn-fanatecMoza affiliate link: https://mozaracing.com/?ref=r7OBYTBC8quwTrakRacer affiliate link: https://trakracer.com/?ref=VPpUf1OAhYB0KuBuzzsprout affiliate link: https://www.buzzsprout.com/?referrer_id=1675699Follow Traxion.GGhttps://twitter.com/TraxionGGhttps://www.instagram.com/traxiongg/https://www.youtube.com/traxiongghttps://www.facebook.com/TraxionGG/

Week of: 5-29-2023 Xbox Gaming News, Releases and A Fun Fact

Development is a continuum, with team after team continuing to improve the code base. How do you handle inherited code base and technical debt? How does a new team measure and value its contribution to the product against the inherited code base? Listen to this episode of the CTO Podcast as Hezheng Yin, Cofounder & CTO at Merico, discusses contribution analysis for dev teams. Show NotesConnect With: Hezheng Yin: Website // LinkedIn // TwitterThe CTO Podcast: Website // Speaker ApplicationEtienne de Bruin: Website // LinkedIn // TwitterSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

It's time for your weekly update from the Checkpoint team with all the latest info you need to survive another week in the video games industry! Join Elliot, David and... LEARN MORE The post Up To Date: Sega'a acquisition of the Angry Birds dev team and more! appeared first on Checkpoint.

For this first episode, we want to address the most burning questions from the Brawl Stars community! Once we get this out of the way, we want to investigate specific topics! This is the first episode we have, so let us know if you like it and what would you like to see next!

S ABB přišel v životě do kontaktu snad úplně každý. Obvykle stačí, když si rozsvítíte na záchodě ve vašem oblíbeném baru.

In this episode of Startup Hustle, Matt Watson and Hoss Devin, CEO and Founder of Automotive Innovations, dive into the common challenges entrepreneurs traditionally face when running a dev team. Gain valuable advice from these seasoned founders on what to look out for and how to avoid the traditional pitfalls startup founders make while managing a development team.   Find Startup Hustle Everywhere: https://gigb.co/l/YEh5   This episode is sponsored by Full Scale: https://fullscale.io   Learn more about Automotive Innovations: https://automotiveinnovations.com  See omnystudio.com/listener for privacy information.

Welcome to 'Mentoring Moments', a sub-series of the Podcast Mentoring Moments is composed of clips taken from Jason's 1-1 and Group Mentorship Sessions These sessions cover topics such as: digital, eCommerce, retail, SaaS, marketing, tech and business - plus so much more! The episode title outlines some of the topics covered in the episode for reference If you'd like to join Jason's Group Mentorship Program ('The Mentor Sessions') for free and get answers to your own questions, head over to the registration page to register for the sessions in your time zone and you can also apply for 1-1 mentorship with Jason on this page

Athletes from Strength & Speed jump on the call to talk 2023 goals and how they plan on achieving them.  Brenna Clavert, AC Hale, Jaeme Simmons, Phillip Hucke and Ryan Ardigo share some big goals.  If you are looking at some goals for next year, this episode will give you some ideas as well as how to achieve them.    Apply for Dev Team here: https://www.teamstrengthspeed.com/apps/blog/show/50372787-8th-s-s-development-team-now-open- New Year's Resolutions Article: https://www.teamstrengthspeed.com/apps/blog/show/43749159-why-do-new-year-s-resolutions-fail- Sign up for Mythic Race here: https://runsignup.com/Race/MO/Benton/MythicRace2023 Use code UltraOCRman to save 10%  on every order from www.MudGear.com   Episode brought to you by Yolked, use code Strength20 to save 20% off every order from www.yolked.com Music provided by Dino Sinos

The caregiver shortage is growing, but a lot of caregivers are leaving the industry, especially during COVID. What is the best solution? Probably an on-demand economy. Caribou creates software for home care companies that helps them recruit and retain caregivers with referral and incentive programs. As CTO that works with customers the same as on the technical part, Timothy shares his advice on both his startups related to healthcare, how to define how much to pay for a solution that nothing like this existed before, and how to choose a team that can give you great results. And also, why should project managers be involved very early on in the sales cycle? Enjoy the listening! Links: Tim's Linkedin: https://www.linkedin.com/in/timothyahong/?originalSubdomain=ca Caribou website: https://www.caribou.care/

Custom Mobile Apps

In this podcast episode I interview Tony Howard-Arian and Abby Howard of Black Tabby Games, and we discuss how they balance life and work as they create their game Scarlet Hollow full time in their apartment. ► Wishlist Tony and Abby's game Scarlet Hollow on Steam: https://store.steampowered.com/app/1609230/Scarlet_Hollow/ ►Follow Tony and Abby below! Twitter: https://twitter.com/blacktabbygames Abby's Twitter: https://twitter.com/AbbyHoward Devlog where they talk about marketing, game design and keeping your community happy: https://medium.com/@blacktabbygames ► What I believe: https://youtu.be/jQK3LniPMq4► Get my 2D Game Kit Free: https://www.fulltimegamedev.com/free-game-kit ► Learn my secrets to 6 figures as a game dev, year after year! https://www.fulltimegamedev.com/join-webinar-live-stream ► Learn Game Dev (Get 25% off with code LETSGO): https://full-time-game-dev.teachable.com/p/full-time-game-dev/ ► Learn 2D Art (Get 25% off with code LETSGO): https://full-time-game-dev.teachable.com/p/2d-art-pro ► Wishlist "Father": https://store.steampowered.com/app/1575990/Father/ ► Edited by: https://youtube.com/channel/UCSw7bZnTAxp_YJYxjb0Qn5A ► Follow Thomas on Instagram: https://www.instagram.com/thomasbrushdev/ ► Follow Coder of "Father" Ajay: https://www.youtube.com/c/AJTechTV/videos ► Follow "Father" 3D Weapons Creator, Felipe: https://www.youtube.com/user/Felipecaravelli/videos ► Follow "Father" sound designer, Hector! https://www.youtube.com/channel/UCSXULsAci5W3FIQy-mr0XKg ► Play Neversong: https://store.steampowered.com/app/733210/Neversong_formerly_Once_Upon_A_Coma/ ► Play Pinstripe on Switch or Steam: http://atmosgames.com/ ► Check out my games: http://atmosgames.com/ ► Ask a question on my subreddit: https://www.reddit.com/r/ThomasBrush/ ► My Studio Set-Up: https://www.amazon.com/shop/thomasbrush

In this podcast episode I interview Tony Howard-Arian and Abby Howard of Black Tabby Games, and we discuss how they balance life and work as they create their game Scarlet Hollow full time in their apartment. ► Wishlist Tony and Abby's game Scarlet Hollow on Steam: https://store.steampowered.com/app/1609230/Scarlet_Hollow/ ►Follow Tony and Abby below! Twitter: https://twitter.com/blacktabbygames Abby's Twitter: https://twitter.com/AbbyHoward Devlog where they talk about marketing, game design and keeping your community happy: https://medium.com/@blacktabbygames ► What I believe: https://youtu.be/jQK3LniPMq4► Get my 2D Game Kit Free: https://www.fulltimegamedev.com/free-game-kit ► Learn my secrets to 6 figures as a game dev, year after year! https://www.fulltimegamedev.com/join-webinar-live-stream ► Learn Game Dev (Get 25% off with code LETSGO): https://full-time-game-dev.teachable.com/p/full-time-game-dev/ ► Learn 2D Art (Get 25% off with code LETSGO): https://full-time-game-dev.teachable.com/p/2d-art-pro ► Wishlist "Father": https://store.steampowered.com/app/1575990/Father/ ► Edited by: https://youtube.com/channel/UCSw7bZnTAxp_YJYxjb0Qn5A ► Follow Thomas on Instagram: https://www.instagram.com/thomasbrushdev/ ► Follow Coder of "Father" Ajay: https://www.youtube.com/c/AJTechTV/videos ► Follow "Father" 3D Weapons Creator, Felipe: https://www.youtube.com/user/Felipecaravelli/videos ► Follow "Father" sound designer, Hector! https://www.youtube.com/channel/UCSXULsAci5W3FIQy-mr0XKg ► Play Neversong: https://store.steampowered.com/app/733210/Neversong_formerly_Once_Upon_A_Coma/ ► Play Pinstripe on Switch or Steam: http://atmosgames.com/ ► Check out my games: http://atmosgames.com/► Ask a question on my subreddit: https://www.reddit.com/r/ThomasBrush/ ► My Studio Set-Up: https://www.amazon.com/shop/thomasbrush

Freedom 35ers: Cardano NFT (CNFT) Podcast. This week we discuss our reactions to CNFT Live and stream with JCRYPTO. We give our reactions to the Yummi Universe Litepaper and getting the chance to interview the Dev Team. The Ape Society took off in the CNFT market and we break down why. We also go over our reactions to new mints for the ADA Army NFT, Split World, and Pendulum. We give deeper dive into the Ghostchain Whitepaper 2.0 along with its Freeroam marketplace. Lastly, we take a look at the V3 airdrop for the FAHA10K Tribute and new FAHA1k Discord. And can't forget The Grumpy Bunny's airdrop of the base Build-A-Bun and how you'll be able to customize him. Freedom 35ers

Modern problems require modern solutions, right? The problem is, it's becoming increasingly difficult to understand what solutions are required for a given problem and even harder to task a team with finding them. That's why Bob Ritchie, VP of Software at SAIC, thinks the top-down management model is dead. To replace it, Bob is championing a “team of teams” model that provides his developers with far more autonomy - so much, in fact, that they can even self-elect their leaders. On this week's episode of Dev Interrupted, Bob discusses the challenges of software development in an increasingly dynamic environment, why he believes developers should be no further than 4 steps away from their CEO and the historical challenges of connecting results in Silicon Valley to those in the federal government. Who would've expected a federal government tech integrator (Science Applications International Corporation), to be on the leading edge of developer autonomy?Learn more about our INTERACT conference on April, 7th: https://devinterrupted.com/event/interact/SAIC is hiring: https://jobs.saic.com/Bob's LinkedIn: https://www.linkedin.com/in/bob-ritchie-896a654/ What Bob is reading: Drive: The Surprising Truth About What Motivates Us Join our Discord Community ►► discord.gg/devinterruptedOur Website ►► devinterrupted.com/Want to try LinearB?  Book a LinearB Demo and use the "Dev Interrupted Podcast" discount code.Have 60 seconds? Review the show on Apple Podcasts

Go to http://meundies.com/kindafunny to get 15% off your first order plus free shipping. Get 25% off and zero delivery fees on their first order of $15 or more, when you download the DoorDash app and enter code KINDAFUNNY. SnowBikeMike and Gary unite once again to talk about a big Xbox news story: Perfect Dark's The Initiative studio seeing a wave of departures. Let's talk about this and more! Time Stamps: 00:00:00 - Start 00:06:19 - Housekeeping PSILY is live and it's the GTA Online Starter Guide you've been waiting for! Join Greg, Bless, Janet, and Zack Zwiezen from Kotaku! youtube.com/kindafunnygames and podcast services. A Special episode of MCU In Review is now up on YouTube.com/KindaFunny and on podcast services around the globe, with Tim Gettys joined by Erik Voss of New Rockstars making their 2022 MCU Predictions! 00:09:28 - The Initiative has lost half of its core Dev Team in the last 12 months! 00:36:33 - The Crew 2 Getting 60 FPS Support On PS5! 00:40:18 - Halo The Series New Trailer (Official Trailer #2) + IGN Review Of Premiere 00:45:30 - Xbox Game Pass Update For The Second Half Of March 00:47:48 - Heads Up! Tomorrow Wednesday, March 16, 10 AM PT 00:48:24 - Out today 00:51:37 - Squad Up 00:52:03 - You‘re Wrong Tomorrow's Hosts: Blessing & Andy Epic Creator Code: KindaFunny Follow The Kinda Funny Team On Twitter: Mike Howard: https://twitter.com/SnowBikeMike Gary Whitta: https://twitter.com/garywhitta Barrett Courtney: https://twitter.com/SadBoyBarrett Roger Pokorny: https://twitter.com/rogformer

Hate interruptions? Ever feel like you've lost your ability to focus on coding? Katie Wilde, VP of Engineering at Ambassador Labs, knows your pain and she's on a crusade to help devs everywhere reclaim their focus. Spoiler: She's got a message for managers who can't meet with devs whenever they want: “Don't like it? Well, suck it up.”The thing about productivity is, you can't have it both ways. You can either protect your devs' ability to focus by providing them meaningful time for creativity or you can call them into meetings all day long for constant feedback - but you can't have both. These concepts don't have to be at odds with each other, though. On this week's episode of Dev Interrupted, Katie details exactly what managers can do to foster a harmonious, productive environment between themselves and their devs. She also talks about the importance of “shifting left,” the dangers of doing it too quickly, and why “hiring great people and getting out of their way” may not be a good mantra.Learn more about our INTERACT conference on April, 7th: https://devinterrupted.com/event/interact/Ambassador Labs is hiring: https://www.getambassador.io/ Join our Discord Community ►► discord.gg/devinterruptedOur Website ►► devinterrupted.com/Want to try LinearB?  Book a LinearB Demo and use the "Dev Interrupted Podcast" discount code.Have 60 seconds? Review the show on Apple Podcasts

In this episode, Amy and James talk about their experiences on actual development teams and the different processes and workflows that work best.SponsorsVercelVercel combines the best developer experience with an obsessive focus on end-user performance. Their platform enables frontend teams to do their best work. It is the best place to deploy any frontend app. Start by deploying with zero configuration to their global edge network. Scale dynamically to millions of pages without breaking a sweat.For more information, visit Vercel.comZEAL is hiring!ZEAL is a computer software agency that delivers “the world's most zealous” and custom solutions. The company plans and develops web and mobile applications that consistently help clients draw in customers, foster engagement, scale technologies, and ensure delivery.ZEAL believes that a business is “only as strong as” its team and cares about culture, values, a transparent process, leveling up, giving back, and providing excellent equipment. The company has staffers distributed throughout the United States, and as it continues to grow, ZEAL looks for collaborative, object-oriented, and organized individuals to apply for open roles.For more information visit softwareresidency.com/careersDatoCMSDatoCMS is a complete and performant headless CMS built to offer the best developer experience and user-friendliness in the market. It features a rich, CDN-powered GraphQL API (with realtime updates!), a super-flexible way to handle dynamic layouts and structured content, and best-in-class image/video support, with progressive/LQIP image loading out-of-the-box."For more information, visit datocms.comShow Notes0:00 Introduction2:58 Jobs on a Development Team4:58 What is agile?7:09 Sprints8:32 Deadlines and Milestones10:19 Sponsor: Vercel11:25 Writing Stories15:23 Types of Stories21:26 Version Control and Git within a TeamEpisode 34 - Getting gitUsing Git with a Team on YouTube22:55 Continuous Integration and Continuous DeploymentEverything Svelte26:41 Code ReviewsTweet from James / Compressed.fm Codebase28:27 Sponsor: DatoCMS29:21 Prioritizing and Pointing Stories34:47 Who writes the stories?36:21 Velocity38:26 Pair ProgrammingTupleLiveShare through VS Code45:08 Meetings47:46 How Design Fits into the Process49:12 Sponsor: ZEAL50:05 Grab Bag Questions53:10 Amy's Pick: Rainbow Pirates53:27 Amy's Plug: Everything Svelte53:50 James's Pick: Kreg Pocket Hole Jig Pro 72055:53 James's Plug: James Q Quick on YouTube

 Interview - M17 Dev Team with Scott - N4UPC

Describing main types of problems businesses have before starting to work with software teams, and sharing our experience about three main steps of this process. You are running your business, and now it's time for you to find a software team. How to work with those guys and what to expect from them? Let's try to find out. - Which problems current businesses face - How new or updated software may help them - What your cooperation will probably look like - What are the main stages of starting this work - What kind of hard decision you should make

What's up! Welcome to the Cock Talk Podcast, Make sure you like and SUBSCRIBE!! We break down the most recent dev blog and show off the new video they dropped on us. MOST OF ALL WE GOT A RACING DEMO and we break it down live! Be sure to check out SHOTWELLCANDY.COM and get yourself some caramel. Use CockTalk20 for 20% off! We dropped a website https://coopcollective.io where we plan to drop all sorts of news, articles, and hopefully analytics will come down the road when racing and breeding starts. Follow us on TWITTER @cocktalkderby and be on the watch for the details! Hope you enjoy!! PS beware of scammers! If you need help ask a Discord mod BAWK

In this episode we dive into Nintendo Direct and the news that Perfect Dark Reboot Is getting the "Crystal" Touch! Also, special guest this episode is MasterDebater Brian and he comes with the heat!!! Justin and Brian have an all out battle on several different topics so make sure you check those out! Big Surprise Coming Up Next Week!!!!! Tune into the socials to see who our guest is for episode 50! If you are on Apple Podcasts we would LOVE if you leave a review! Thanks in advance! Let us know what you think about the show and how we can improve by emailing us @ the90sfirstpodcast@gmail.com  Want to connect with The '90s First? Here is everything you need to do so! Patreon link - https://www.patreon.com/the90sfirstpodcast?fan_landing=true Twitter - https://twitter.com/the90sfirst IG - https://www.instagram.com/the90sfirst FB - https://www.facebook.com/the90sfirst   Find Mike here: Twitter: @Mike90sFirst   Find Joe here: Twitter: @joeboarder21    Find Cicero here: Twitter: @StubbyStan   Find Justin here: Twitter: JustinM2500   Music Credit: Codename: Indigo Harris Heller Lone Wolf ℗Senpai Music Group Released on: 2020-07-11   Cold Disco Harris Heller: Dansu ℗Senpai Music Group

In this episode we talk to Justin from the Ultimate Games Master App about the App they have been developing for some time now! The App is designed to give every DM of every Skill Level a great Tool to build their Campaigns, Manage their Notes and create while cutting down on the time needed for prep. It also has a Player Mode with a Character Sheet where Players can manage their Characters and even a Streamer mode for Streamers to engage and immerse their Audience in the Game played on screen! The Ultimate Games Master App is still live on Kickstarter for you to back, go to: https://www.ultimategamesmaster.com/ for that. The Dev Team can also be found on Twitter: https://twitter.com/TheUltimateGM Our Socials: Twitter: https://twitter.com/DoubleDMpod Instagram: https://www.instagram.com/doubledmpod/ --- Send in a voice message: https://anchor.fm/doubledm/message

About the project The munch token dev team is in the hot seat as I interview them about their project. The munch token has only been out for less than a month and I can see this doing really well. Thanks so much for Rodrigo and Mike from the munch token project for hoping on the podcast. You can see the full Youtube version of interview here. Links to this project https://munchtoken.com/ Etherscan

In the first episode of The House of The Dev podcast Warren Spector shares his vision and methods of assembling and managing your first game dev studio.   ⁃ First steps: surround yourself with people who are better than you.   ⁃ Passion vs money: what matters most at the start;  ⁃ If we can scare you away, it's not your dream job;   ⁃ The importance of high level advisors - and when to stop to avoid being annoying;  ⁃ Daily work: eye to eye or distanced. New rules and opportunities of the post-pandemic world.   ⁃ Naked people in the middle of the night and tipped tables: the stress behind the curtains.   ⁃ Why crunching is unavoidable - but also unacceptable. Unreal Engine Dev Contest: https://unrealcontest.ru/2021/ Subscribe to our YouTube channel for video version of this podcast and more content: https://www.youtube.com/channel/UC4veWHR5m7wyk0GNWmQD8VA

Timestamps: - Part 1 - 01. 00:00:19 Special Episode Interview with Grant Davies 02. 00:01:53 What's happening with the Group Matchmaking timeline 03. 00:04:15 Challenges of implementing all the new content and upgrades 04. 00:08:20 How to balance game MMR vs Location for Matchmaking 05. 00:11:22 How does the point system really work 06. 00:13:08 What is involved in picking the ladder map pools 07. 00:18:17 Teasers of upcoming changes, content and updates 08. 00:20:52 Newly found bugs and what's being done about them 09. 00:27:51 How much more popular did SC1 become after SC:R was released 10. 00:29:16 Journey to becoming a programer & What it takes to be a game dev 11. 00:31:27 Thoughts on the state of the Korean scene 12. 00:34:40 Thanks to Grant for joining us - Part 2 - 13. 00:35:18 Welcome back from Intermission 14. 00:36:29 Part 2 Show Road Map 15. 00:33:28 Corrupted Cup Review 16. 00:53:10 Nation Wars Highlights 17. 01:13:34 Time Sensitive SC Announcements 18. 01:15:58 Catz talks about Tespa 19. 01:17:40 The BlizzCon 2019 Groups 20. 01:34:34 Adrian Harris's Departure 21. 01:40:05 Patreon Q & A 22. 02:38:58 What everyone's up to/ Wrap up - Shownotes: http://bit.ly/Ep68TPS - Visit: https://ThePylonShow.com for Podcasts, VODs, Q&A submission link, countdown timer, and more. - Check out our Guests here: - Grant Davies: https://twitter.com/GrantTheAnt - CatZ: https://twitter.com/ROOTCatZ https://www.twitch.tv/rootcatz https://www.root4root.com - RAPiD: https://twitter.com/RAPiDCasting https://www.twitch.tv/RAPiDCasting http://youtube.com/c/rapidcasting http://www.instagram.com/RAPiDCasting - - Power the Pylon - - https://www.patreon.com/ThePylonShow - - Social - - Discord: https://discord.gg/ga5umfc Twitter: https://twitter.com/ThePylonShow Instagram: https://www.instagram.com/thepylonshow/ Facebook: https://www.facebook.com/ThePylonShow/ - Special thanks to the Pylon Show Team - VFX Artist: https://twitter.com/Bodypop_ Producer: https://twitter.com/CobraVe7nom7 Shownotes: Alisaunder - https://twitter.com/Daisemiin WebDevs: Diaxis & NeosteelEnthusiast Timestamps: https://twitter.com/AllelujahTV - Sponsors - https://afktea.com - https://matcherino.com/thepylonshow - This weeks code: "cookie" #ThePylonShow Live Wednesdays @ 5:45pm PT on https://www.twitch.tv/Artosis/