You can never really fully comprehend how something is going to work until you bring it into existence and smack it around a bit.

@afuzzybearsyoutubechannel2812

Ай бұрын

such is life

@RickGladwin

Ай бұрын

Dad??

@RickGladwin

Ай бұрын

(entirely a joke btw. My dad is a gentle, dependable dude)

@parnellitube

Ай бұрын

@@RickGladwin And look how good you turned out 😆

You two talking is great. Memories, tactics and family life still there 😂🎉

First time in live i went slow in playback speed! Such passion.

Love listening to Kevlin. And dear god, the amount of headaches we could save by simply taking an honest deep look at the real environment we are delivering to and simply adjusting for reality, even if that means we have to walk back on the "ideal designs" we wanted (but work real bad)... My current one being something that designed to "look like this" without knowing if a) the platform could deliver that and b) if so, AT WHAT COST? Much as i hate Apple, the one thing i like is that, if you don't see a simple and direct way to do something in the UI SDK even though it's doable, that's them silently advising you AGAINST doing it, because 99% of the time you're just trying to be "different for the sake of being different" and shooting yourself straight in the foot...

You must create version 2.0 to fix what you realized that you did wrong in version 1.0

I've always thought of Engineering as Creativity + Applied Science

I had to call my internet provider for more bandwidth to handle two all-time greats in one video.

@RickGladwin

Ай бұрын

I had to overclock my machine in order to deal with all this clout.

I love your reaction to the idea of Kevlin "meditating upon the design"... I wonder if you've gone to a similar visual place as I did... Kevlin, sat in the lotus position on a desk for 3 days with an "Illuminati triangle" slowly materialising above his head. :)

@ContinuousDelivery

Ай бұрын

🤣🤣🧘🏽

Idealogues will never understand this.

One of my previous employers tried to factor "experiments" like these by calling them something else in their "Scrum" process (I already forgot what they called them) and then we've had to estimate these in the team. We really sat there in estimation meetings to talk about how long anyone should invest into looking up solutions to specific problems. So if you picked one of these tasks, you'd have for example 24 hours (equaling three work days with 8 hours each) to look into this issue. If you figured out a solution sooner, you could document these findings and then create a task for the actual implementation. If not, you should then show your progress to the rest of the team and discuss how to continue. I think it is needless to say that nothing got done in that company and I left out of frustration because I got less done there in four full weeks than on one evening in my free time on my own projects (I wish I was exaggerating).

@captainnoyaux

Ай бұрын

In saFe ( scrum at large companies) it's even worse they plan for anti debt sprints after a release cycle (to justify doing a bad job). Then the debt sprint is never done because you never have the time to do it 😂😂😂. I leave quickly jobs like that

@Fanmade1b

Ай бұрын

@@captainnoyaux Ah, yes. They actually wanted to implement saFe there as well. After the manager in charge mentioned it, I remembered the quote "Shitty Agile for enterprise" from Allen Holub and sent him the video about that from this channel here. Apparently they did actually move away from saFe, but they didn't improve their (even worse than standard) modified Scrum and they talked about some other method which looked like saFe with different colors. So I can't say that they didn't listen at all, but it is still bad enough that I wouldn't go back, even though they paid really well.

@johnridout6540

Ай бұрын

Scrum assumes that the only right lifecycle model is an evolutionary prototype. Other lifecycle models are available.

Nobody is picking up on the fact the architect is actually coding. This was the norm late 2000s into early 2010s, and unfortunately we've gone back to architects being useless and causing more problems than they solve by not coding.