postfacto

https://github.com/rayfrankenstein/AITOW/blob/master/README....

I’ve seen many agile shops fail to ever get CI/CD working because the effort just couldn’t find a place and a schedule on the backlog.

Far too few developers understand: just because the people writing the checks ask you to do it and you implemented it exact as they ordered you to doesn't mean the people writing the checks will take responsibility for the resulting bad situations that can lead to them not writing you checks anymore. If anything, you'll be used as a scapegoat to prevent them from not getting any more checks written.

  A CTO of an American company, to get a bonus of $7 million, lays off a ton-load of the company’s CRM people who knew how 20 years of architecture duct tape that ran the company was strung together.

  CTO then proceeds to hire a cheap, offshoring body shop to design the company’s new website, which talks to the CRM. However, there’s no more CRM people at the American company because they’ve all gotten laid off and the offshore web contractors also now have to become customized CRM experts, which is insane scope creep.

  The outsourcing company can’t deliver and litigation is sought, while the US company takes zero responsibility for the fact that all the CRM people were let go and there’s no chance in hell that web developers at the outsourcing can ever learn the highly customized domain-specific logic that fast that extensively. Meanwhile, CTO gets fired and a severance of $1 million for all the extreme damage he did to the company.

“Nobody gives a hoot about profit”.

https://github.com/rayfrankenstein/AITOW/blob/master/README....

If simplicity is always the right solution, then why do so many programming languages have dedicated parsing libraries for .csv, which has to be the world’s most simplest data format ever?

What’s for an enterprise exec not to love?

Kinda like how because you ride an escalator people no one ever hears you climbing stairs.

The Career Programmer: Guerilla Tactics for an Imperfect World (Expert's Voice) https://www.amazon.com/dp/1590596242/ref=cm_sw_r_cp_api_glt_...

But the F-35 was already a shitshow, because the aircraft itself was designed using agile, though the Pentagon called it “concurrency” instead of calling it “agile”. Concurrency (agile) was also used for the Littoral Combat Ship (LCS), which produced a similarly disasterous, unreliable four-assed monkey that neither the Chinese nor the Russians would ever take seriously.

I then tried to learn Symbian and I found the IDE hard to setup, the API was hard to learn, and I believe it only ran on windows.

At the time I thought to myself “the NeXT/Cocoa API and utilities are so awesome, so easy, so mature that if Apple ever makes it possible to write mobile apps with them, they are totally going to absolutely destroy everyone else in the mobile development marketplace. Especially Symbian.”

https://github.com/rayfrankenstein/AITOW/blob/master/README....

Dump agile, write the backend first, in a thick juicy horizontal slice, create a decent json schema document for it that you show to important people at the mandatory demo, and then hand the schema document to the front-end person with the understand you may have iterate on your API a bit as you incorporate their feedback.

- Very attuned to their own fashion attire. Very well/trendy dressed.

- Use the words/phrases “value”, “add value”

- Brag about themselves a lot. Talk about very lofty standards about very minor details.

Also, your real job is making your manager look good to his manager, not actually the nominal job of writing reliable, stable, flexible code that you signed up for in your employment agreement.

The reality is that to do Xamarin well you’ll have to wander outside out Xamarin Forms, and to do that well not only do you need native mobile developers but you need far higher caliber native mobile devs who are able to mentally translate swift/objc and android calls into their C# equivalent, and who have an idea of what’s going on the os when there’s a crash at a level lower than the .NET runtime caused by a native part that’s not apparent in the crappy Xamarin stack trace.

Xamarin really only makes sense if your company has a mountain of existing complicated .NET code with priceless business logic that you absolutely have to reuse.

Keep technical debt in separate tasks to make the tech debt visible and to keep management accountable for not making efforts to get rid of it.

I once had a manager who, on the subject of upper management wanting to ship the prototype, would say “the difference between dev and prod is one letter.”