Nicholas Lemay

Break down barriers Work as a team Drive out fear Build quality into the product Train on the job Improve constantly and forever Good ideas never grow old. #deming

@SamiZayn Felt that 🧡

Finally made it and it was biblical.

@AndrewStellman @jitterted That being said, I'd be curious to hear your takes on this, and how they may differ from my own experience. Learning opportunity :-)

@AndrewStellman @jitterted (Taken from the testing google blog) I'd much rather see a test a bit closer to this, where the test is much less coupled to the implementation of the interactions with the collaborating object.

If you write tests first, then there's no way the test can be testing implementation details. Isn't that what lots of folks seem to be arguing about? When you write code first, you have an implementation, which can make it easier to write tests coupled to that implementation.

“La maintenance” by CodingPartner «Codez comme si les personnes qui effectueront la continuité de ce code sont des personnes chères à vos yeux» link.medium.com/Tup8CsAfazb

"Most conversations about problems (and causes) are negotiations—negotiations about identity, reputation, controlling the narrative, and spheres of influence and control. People look for the "definition" they can live with and process." cutlefish.substack.com/p/tbm-212-a-pr…

@johncutlefish Owning it. Meaning: doing it without negotiating/delegating the authority to do it with management.

@DamianEdwards Curious: What is your current work week and why?

If the AI revolution doesn't bring about productivity changes that lead us to a 4-day or even 3-day work week, then I have to wonder WTF the point of all this tech is. #capitalism

@davidfowl Hated webforms implementation with a passion, but loved everything I’ve tried my hands on with Blazor so far. Feels like what Webform could have been.

Webforms was ahead of its time….

@alexbunardzic @KentBeck Same could be said for services as a corollary ?🤔 « An awkwardly large service is easier to manage than two awkwardly connected services »?

"An awkwardly large team is easier to manage than 2 angry teams." @KentBeck

@EskoLuontola @jasongorman In what cases couldn’t this be resolved by the usage of feature/release flags?

@jasongorman You need to wait for another team’s approval before deploying your changes to production.

@thdxr @skamille This take is targeted towards software engineers specifically or all engineers?

engineers are really good at being technically correct and practically completely missing the point

@jasongorman Can't blame me for trying! Sure thing. Thanks for rallying all the troops. We even lost x good men/women along the way.... Anyhow, here is your bonus. About that new project....

@jasongorman In scenario B, if they do not meet targets, they fear for their reputation, being blamed, etc. We now go into the(to paraphrase DeMarco) "at least we tried". "We threw everything at the problem: more people, forced overtime, bonuses, tiger teams, etc. and still did not make it.

@jasongorman I've seen this with even with devs with 10-15 years experience. Unfortunately, sometimes, they've just yet to meet/pair with anyone who will show them better.

@guaq @jessitron I’ll lift that one!

@jessitron We have a running joke about the chairs belonging into a chair room and tables belonging into a table room. 😅

“The Controllers belong in the ‘controllers’ directory. The Views belong in the ‘views’ directory.” Oh, do you name all your variables “integer” or “string”? Use the directory structure to communicate some relations between parts in the program!