I work part time by choice..

i would like to know how to write good unit tests

agile=no documentation

Real agile hasn't been tried yet.

The Agile manifesto was actually promoting a liberal flat hierarchy work environment, where people spontaneously form meetings and organise themselves without third person interference. It was perverted by capitalist (micro-)management into a form of assembly-line work, where the assembly line stops in regular intervals disrupting the mostly parallel work of the programmers. Standup is for comedy, not for software production.

The 40-hour work week feels outdated, especially when there are tools like Resubot that can help you focus on what truly matters in your job search.

I recently heard about ResuBot, which seems like a helpful tool for job seekers. It’s great to have options that streamline the resume process.

Interesting perspective! If only more companies would consider the benefits of a shorter work week for employee wellness.

I’ve been feeling burnt out working 40 hours a week. It’s refreshing to hear someone challenge the status quo.

This video really makes you think about the traditional work model. I wonder how many companies will actually adapt to a 4-day work week.

I’m 9am-2pm Tuesday - Friday..

Programming was destroyed before agile got there. Agile has good ideas to fix things, but management has a hard time of letting things change

Historically most people worked 4-6 hours average and 8-10 hours during harvest season. (agricultural work)

“I’ve never used python” 10 seconds later…Completely proficient in python

Dude when someone is "too occupied" to read the manifesto, that's total BS. It's literally 16 short sentences with very clear messages. People can't pretend they don't have 5 minutes to read through the manifesto during the retro. When you're on such a team, you know what's up. You can't fix that. Save your energy, don't discuss and just quiet quit that freak show.

The one important thing that most people don't seem to get is that there are a lot of software dev areas. writing code for a game is completely different than writing code for a business software and writing a code for a microchip... When you are making a game, you have to execute your entire logic in less than 20 ms if you want a smooth running game. In that case, you have to write the most smart, near to the hardware code possible. And clean code principles are not suitable that's for sure. On the other hand, if you build enterprise/business applications, which are mostly programs that interact with a database, performance is not an issue, at all. What is an issue for sure is clients requirements changing over time, and in that specific scenario, clean code will save you a ton of head aches if not save the business. Clean code is a must for code bases that change alot, which is not the case for a game for which the code will never change after shipping (very rarely).

You should comment on his prior video where he talks about why performance matters for basically any mature product and why common excuses to justify shipping crap are BS. I'd like to see your opinions clash.

LOL now they are all cutting and outsourcing to San Deep.

You need that much money to live in the San Fransicko area.

Well.....if you are getting paid a full salary and not putting in the hrs expected, hope you get fired for fraud and mischarging ....this is the wrong attitude.....if you reduced your salary to match the hrs, at least then you are being honest....but this guy doesnt seem to have that little thing called integrity...

"I write Kotlin and dont think much about CPU caches", i wonder why

Bernie Sanders has the idea of a 32-hour work week but it's still being discussed in Congress.

At its heart, "Clean Code" is about abstractions on top of abstractions. If you follow the book strictly you will get an unmaintainable application. If it takes more than two hops to find the code that your function is calling, you're probably doing something wrong. Removing abstractions, when it makes sense, improves the speed of code development.

I think you might have missed the core point of the original video. The relationship between hardware capabilities and application performance isn't linear, and clean code plays a role in this disconnect. The shift in focus has moved from understanding the application and its target infrastructure to dealing with the application and the abstraction layers built on top of it. These abstractions, however, lack clear metrics to define what’s “good” or not, making their value subjective. For instance, while isolating functionalities and states in classes/objects may improve modularity, it sacrifices the locality of behavior. On top of that, as the video explains, this approach often underdelivers in terms of performance. It's an important discussion, especially when balancing clarity and efficiency in code.

Sounds like the keyword here is, "management," and that the position just wasn't a good fit for what you want to do with your time. From what I've gathered, engineering management, is about managing engineers, and seeing what's going on from a higher-level vantage point, rather than being involved with the detail work...that's what the engineers are there for.

Please tell me the breakpoint . What is the base ?😊

Any experience having direct reports who aren’t receptive to you being their mentor?

this video is amazing, I like how you were also showing your code and everything!

Thanks for this tutorial. I'm gonna try it. I'm not a coder so I'm not sure of how to do the json thing. maybe explain that a bit more please. Have you heard of the pop pop's strategy using excel?

I will NEVER work more than 32 hours a week. And I LOVE MY JOB. but every other weekend I have off plus two other days. AND.....AND.... I will NEVER WORK TWO JOBS ever again. I was in my late forties doing that. Never again.

I have two interviews tomorrow. Both part time .. Ppl will think I’m crazy but only I know how much mental I can take ..

😂😂😂😂

Im starting to believe there are two kinds of software developers. The first type develops webs that take five seconds to present 2Kb worth of information and apps that take up half a Gb of RAM. The second kind programs real time OS kernels and MRI machines and computer weather simulations. Ideally, they should be kept as far apart from each other as possible and never be allowed to talk to each other about best programming practices.

It’s proven that more hours worked doesn’t necessarily equate to more productivity. The 40-hour workweek is a relic and should be a thing of the past

Hi Cody! Yes, super relatable! It is nice to hear it from someone else because it reflects my experience, especially with big corporate "agile". I work in the Salesforce ecosystem, and a big problem in our ecosystem is technical debt. And because salesforce development is built for speed (platform development), a lot of code and automation can be built easily. There is a lower barrier to entry, design is less than an after thought, and code becomes hard to understand, test, read, maintain. What role does technical debt and/or collapsed design play in your world? I imagine other application stacks as being much more professional and having higher engineering standards, so I wonder if this issues it as big elsewhere in the world.

I hate engineering. Civil engineer. BS

I disagree that story points (or whatever guesstimation number you use) is a good thing. I was told by my "scrum blackbelt grandmaster level 4" that story points for devs were useless because its just an indicator to what we can potentially deliver based on a "story point budget" but it doesnt necessarily outline complexity or allow for discussion, all it does is help the middle management or product "owner" be able to convey what we think we can achieve, but realistically it never is the case. refinements are useless as its just an hour of summary of what we "refined" last time, but then it just turns out to be nothing more than pedantic re-reading of garbage as if the devs are incapable children who cant read a single word.

dude, just don't, don't try it, Casey is out of your league, and it is clear you lack experience and knowledge, all your arguments are just text book definitions that for someone with actual experience would laugh at all of those books, just stay out of this, watch his video and learn.

destroyed the hell out of it

how about Solution Architect? Engineering manager or Solution Architect which line is good and will offer better opportunities? please share you thoughts.

Been there done that and not for me for the same reason. I don't know if there was any salary difference for you? Not in my case. Nonetheless it's a great experience to try. Now I do my best to not be a burden to my boss.

Agile, as it has been implemented over the last 20 years, is no longer agile. Drop scrum and return to the agile manifesto. Scrum's only benefit is to provide jobs for those in the software development industry who cannot develop code.

A great video for people. Stick to what comes naturally!

Some of what you describe seems related to how your processes in the company were setup. It seems odd to me that you felt more disconnected from the things your team were being asked to build from the product team. We do quarterly planning with product, and I and our lead engineers are in that room. We estimate the work at that high level, figure out what resources are needed to do it, make sure we have or can get those resources, and then finalize our quarterly product work. Things that go up a aginst that will be engineering efforts needed (tech debt, new tooling, etc.) and team training. Our quarterly work is based on the roadmap. The work is broken down and assigned to engineers as Tech leads for each big rock. And they then work to break the rock down into the actual stories, drive functional specs with product, and then it goes into the back log and we start working on it. I still code from time to time, generally what I'll be coding is examples of changes I'm looking for in their code, or if I'm looking to inspire them to think differently how they code. I can share that through examples of code that does that.

Everything you described resonated with my experience of agile. The one thing I can’t figure out is how to reconcile the uncertainty of development with the very real need for a business to budget time and money for a product.

Thanks to agile and SCRUM I made the decision to make an exit at 57. No more work in IT and not more agile madness for me.

Cody, set your E-trade to “sell at vest” like I did, and my stock was sold by my employer during the blackout window immediately after my 93 CRM stocks vested, I got the money yesterday after $11,000 of taxes. While the setting is “sell at vest” your employer will sell your RSUs at the price AVERAGE for the day of selling, and there’s no double-tax. I just sent you a LinkedIn connection request. Great video!

Please help me number

You should stop working 40 hours a week and work 80.

Scrap it all and start rewarding / promoting people that can people/schedule manage and are technical too, so they can mentor the weaker members and drive the best solution.... with quality! I promise, it will become a better project.