Видео

That’s a good point. React isn’t the best way to start your career, as it’s more of an advanced paradigm. I was actually working closely with two bootcamp grads (React), and they were missing the fundamentals of JavaScript and general programming principles. In an environment, in which strong mentoring is present, I can say it's working. But the fundamentals need to be in focus.

@@theSnackableCTO Like you said React is fine IF YOUR good. New developers should start with Vue or something with clear rules. Build some things, freelance maybe land a job. But when they are ready to make the jump for a career then and only then take on React.

Async communication is indeed good. Sometimes it's good to go sync as well. In our teams it's roughly, I would say, 80-20 (Async/Sync). We often rewivew in pairing sessions with great results and plan a feature as a group. But smaller things which don't need presence are all in Teams for us. Regarding the herding example: I don't prefer herding at all. Best results I see happen in fully responsible teams, even without a team lead or manager in place. But if a company does prefer herding, than don't treat them like sheeps =D

Appreciate your feedback, Vladan!

Thanks, Stephan! Glad you like it :)

React is quite simple. When done right, which isn't complex thing, you have your Components and Hooks, which are in the end nothing else then functions. You can have small apps and you can scale them, while keeping complexity stable. We use it even for smaller websites and the performance and DX is great the same time. Maintaining apps, web apps and websites by the same team with the same type of codebase is a valuable thing.

​@@theSnackableCTOThat is the key point.when done correctly. But it's is so open you can be as bad or good. Over engineered or simple as you can code. New developers should stay away until they get more experienced. React code base can turn into a total dumpster fire. Once worse Next.js is sort of taking over.

I will take a look into it! Is it related to agile? Sounds like a story-driven approach of original agile. (Not scrum; don't like it)

Happy to! Stay subscribed, more will follow :)

That is honest and true. I totally agree. I was part of several transformations, in which the culture became good. It's a longer process, but possible. The key to is to remove, what I call, the disconnect between biz and dev. This transformation must start as a vision for the companies culture from above. Appreciate your feedback!

What would you change regarding meetings? Do you think they are totally unnecessary or just a badly used instrument? I have my problems with choreographies like scrum, in which you create the need to meet artifically.

@@theSnackableCTO It really depends on your scenario. I'm in 3 projects, 2.5 scrums, 3 hours of "sprint planning," institutional "check-ins," etc. Any time in-between those meetings is essentially wasted if you consider it takes 15 minutes to get back into working. As a developer by title, I see this as mostly wastage. I've heard of 15 minute scrums that don't go over 30 minutes, maybe I'd like to see these. Encouraging an open door policy to chat or ask for help is also useful. When the content of meetings don't pertain to your task(s) at hand it's challenging for me to be engaged.

Very honest words! I would add stop hire PMs who like to work "above" developers, not amongst them.

@@theSnackableCTO My impression is that the best scrum masters, are developers themselves as well. That's my experience so far. PMs without any coding experience often cause a lot of problems.

Yes, because scrum master can work amongst the team or imperativly. Many just enforce "business" ideas onto devs, instead of working with the devs to improve ideas and make the product even better. I mean the devs are the people who actually build the app. So it makes sense to work with them, instead of being disconnected.

Yes, that's true. There is already a public general (false) notion going on when it comes to the image of a dev.

Thanks, Stephan!

Nah, it isn't that easy; at least not in the next years to come. :) AI right now is an extremly good automatic typewriter hehe

Yes! It sounds funny at first, but it's essential at the end. Our journeys complex and challenging to follow, and it is even easier to lose connection to them. So, narrating in a way people can understand and follow is critical.

Thanks!

Thanks! Appreciate your feedback :)

One step at a time :) it's easy to dream about those great numbers. But in reality they are way lower.

Thanks Stephan! Will do next one is recorded. About Cloud, AWS and Developers. And why this isn't a fit.

Thanks, Vladan. Appreciate your feedback :)

Thanks, Finn! Stay tuned, there will be coming more :)

It's simply the truth that we often put deadlines where we shouldn't do it. Deadlines are miscommunicated milestones; usually unnecessary if we would communicate and collaborate more.

Thanks! :) Glad you like it