On my eval, spelling is not listed in the “strengths” section.

@nibor sadly no.

@asgs my IDE does spellcheck. This compiled fine.

@monkeyboy I think any reasonable person would accept that delaying PR testing until after code review is a waste of the most expensive resource, developer time.
No reasonable person would do that.
Now, if you’re one of the ilk who think that testing is optional that’s a different conversation. Professional software developers test their code before submitting a PR.

@monkeyboy I work for a fortune 5 company. I assure you that area makes up a small fraction of our compute footprint. In addition, the products in that area are generally small and loosely coupled. I know. I helped design them originally. :)

@Godisalie negative. You delete flaky tests and make them not flaky anymore, you don’t review them to see if they should have passed. In this case, it was too many tests being run period, not just a single suite. Basically, someone so ignorant of proper software development that they think humans can inspect more efficiently than machines.

You’re paying for that crap?
It’s no wonder most grads come to work needing training.

@bkwilliams Agile is as agile does. This is Scrummerfall; Waterfall done poorly with daily stand ups.

@bkwilliams exactly. Sick of this being seen as acceptable or normal.

@SSDD we also do DevHops.

Happens whenever they buy “Agile” instead of actually learning anything.

@grumpylady01 hey, at least you don’t need to worry about indexes. 😂😂

@billgates I work to pay for hobbies. Don’t believe in the cult of “all good coders do nothing but code”. There’s better out there. Takes looking to find it. Yes, most tech interviews are stupid.

@billgates you have terrible management. Company I work for has pockets like that and pockets like mine. Being a fortune 5 company, we pretty much have everything, really. I’d find someplace that meets your standards. Life is too short to be prevented from reliving something you’re proud of.

It’s advertised correctly. Not sure what you’re worried about. It’s virtually private, just like it says.

I’m 47. Fuck. It’s worse when I write it.
I’m in a senior developer (very senior) position. I code whenever I get the chance. I architect applications. I share my years of pain with young developers, who mostly don’t listen and insist on learning by failing instead of from the fails of others. I hack people quite a bit. Being an introvert who’s happiest away from everyone but except equally introverted developer wife, I come home to bourbon driven development after a day of pretending to care about feelings.
If all you do is code, someone younger and cheaper will replace you. The secret to a long career is to keep finding bigger and hairier problems. Keep pushing. Keep learning new things. Don’t. Ever. Stagnate. Drive or be driven. I love my job. I have fun almost every day because I’m working on the hardest problem I can find. If you’re bored, you’re doing it wrong and falling behind.

Feel your pain. Been there and it takes a push from devs and upper management to fix. On my old team, we focused heavily on application and test design to make sure that we protected ourselves from chaos when timelines compressed. One of my old team members moved to a company on the east coast that’s a startup that doesn’t test shit. He’s now living a nightmare and wishing he hadn’t had to leave. What it sounds like, and correct me if I’m wrong, is there’s no real design. You have a giant entangled monolith with minimal real testing. Processes are pretty manual, and the team is either bigger than 10 people, doesn’t know what “good” is, or just doesn’t give a shit. All of those situations suck. You can try to start changing it. Bring in hygienic coding practices, BDD, TDD, C4 design, etc. keep pushing. Get management support. If that doesn’t work, we’re hiring people who give a shit. :)
Regarding the readme: yes, commit to version control with the source. See every good OS project ever.

You don’t have a “Brent” problem. You have a organizational structure problem. You don’t appear to have functional teams, those teams don’t appear to be responsible for supporting their crappy shit, and no one is testing effectively.

If everyone on multiple teams is responsible for quality for one repository, then no one is.

Agile, or better yet Lean, documentation is minimal. As soon as it’s in the Wiki it’s obsolete unless it’s just focused on principles and practices. Application documentation should be in the repository README.md or, best yet, written as functional tests.

Again, Brent isn’t your problem. You’ve no constraint like that. What you have is chaotic development. That needs to be fixed first.

They need to just stop fucking chasing the icon. It slows me down. Pick one.

@PonySlaystation I’m giving a talk at a conference next week. Now I’m wondering if anyone will comment on my laptop sticker. I’ll let you know how that goes. 😂

@bkwilliams no, that went great. Things are improving. I'm not running from that. New job is a transfer to follow my passion. The escalation was to help the team, not me. I already had a job waiting.

@lewdogg the reason I like working where I do: change started the same day.

Or managers who don't understand how software delivery works.

Yep, that went well. Things are going to change.

@lewdogg no, not this guy. He means it. That's just his short term action plan. His next step is direct feedback to his reports. Him I trust.

@bkwilliams I suggested that middle management needed to work at least a sprint as jr. devs on a team to learn how it works. My SVP wrote that down. 😂😂😂

@bkwilliams if I get my way, I'll burn my VP and Director to the ground. We cannot survive with "leadership" like theirs.

@jhh2450 when my Sr. VP starts using "Fuck" frequently in the conversation and then apologizes to you for what's been going on, I feel pretty lucky.

I am sorry that I can only give you one ++

Time to mentor him on not being organic automation.