@ars1 Possibly. I find some QAs believe their best contributions are as seat warmers, and therefore are in a fixed position. A quick jury rig (ie. Like most CI) and you're cooking.

@SortOfTested we do have such a team, and they do write automated tests.

The problems start with "why do your tests take 4 hours when 20 minutes will do", "why does it take you a full week to change your mocks", "why did you change gitignore to exclude the apps code but not yours" and "eating crayons is bad, here's why".

@alexbrooklyn unfortunately that would reduce the entertainment value.

If you're referring to mocked web apps like Sandbox, there's a huge difference between deep mocks (cumbersome, costly, rock headed stupid... the sort of thing contract QAs do to justify their existance) and broad mocks, where some condition (such as particular input, rather than latent state) gives rise to a wide variety of behaviour. Above all, they are and must be individually shallow. Mocks must be economical, easily groked and easily modified, which deep mocks will never be.

FSharp.Core.

In all C# projects

It should be almost scientific: arrive at a theory, experiment, measure, report, repeat. Sometimes even sadistic: deliberately break something, anything, just to test quality. Either way, get figures through cunning and hard work like any decent engineer.

Sadly, few could get past Excel 101: a reflection of the market rather than the ideal.

Not so much tattooed but branded with the words "written by an incorrigle fuxkwit": the poorly performing unscalable unreadable stinking shit I've inherited

@Ma30h of course. But "no SSD=no work" works well around here

@heyheni because their boss leads by example namely degree of drunkenness

@ViktorZin lol no unfortunately not. Very much a repeated pattern

Ever met a Haskell/ lisp programmer? They're notorious for it, and as programming can induce OCD it's a widespread phenomenon.

That being said, aiming for near perfection is a good thing. It just needs tempering... eventually perfecting becomes second nature and no longer takes so much time.

@TheCapeGreek aha.. but I omitted the bit about "keeping the code short", especially conditional logic as in this case.

My bad. I am an imbecile.

@ViktorZin nope. Standard issue dell tower desktop pc with the button decorated with the internationally recognised sign for power.

@zshh infinitely better 😁

@freeme just give yourself time and practice.

Remember that CS has nothing to do with coding and everything to do with computation... of anything. So a hash table works the same as mail pigeon holes (from the old days), binary search the same as flipping through book indexes, b trees roughly the same as a mind map of post it notes.
At least that's how I started - putting these concepts into RL contexts.

Big o/theta is just a way to measure relative proportionate costs of algorithms.

It takes time, practice and patience, just don't give up.

@filthyranter excellent :) just give yourself plenty of time to understand it. Data structures in functional programming are hard.

@freeme

To understand the basics:
https://amazon.co.uk/Introduction-A...

How to apply IRL:
https://amazon.co.uk/Pragmatic-Prog...

And where things are heading (lazy evaluation costs) + how to ace the "Compare an array to a linked list" interview question:
https://amazon.co.uk/Purely-Functio...

"Uuurmmm free money!"

A pet peeve are those who insist on..

{
..
} // end of if

Where does one start?

IT'S A LANGUAGE WITH BRACE BLOCK DELIMITATION. OF COURSE IT'S THE FUCKING END. ITS IN THE FUCKING SPEC IF YOU'RE ARSED TO READ. THE FUCKING IDE EVEN PUTS IT IN FOR YOU, FUCKWAD. IF THIS WAS FOR YOUR OWN BENEFIT BOIL YOUR HEAD IN RAT'S PISS. IF IT WASN'T GO FUCK YOURSELF. AND WHEN YOU'VE FUCKED OFF FUCK OFF SOME MORE.

Thanks

@zshh needless to say his big ratio was quite large. This irredeemable fuckwit (with apologies) introduced 5 extras for every one he addressed. On. Fucking. Average.

It regularly took 4 hrs to drum the simplest concepts into his skull. Such as "must do" does not mean "must not do", and "pay attention to detail" does not mean "go to the bathroom and masturbate like a chimpanzee for 2 hours".

The clueless spastic (again apologies, disabled people are not to blame) thought he'd get a pay rise by shouting "I'm a highly skilled wpf dev" at recruitment agents all within 2 metres of the CTOs office.

Put notice in calendar "WFH on <most valuable client> ) project"

Leave the office.

Put notice on slack "Just heard of major broadband works in my area... connections will be unreliable"

Work like a demon.

Yes. Otherwise known as last years release.

Waking up wasn't pleasant.

@italyguy7 Make sure you reap the glory ;) If anything, this situation makes standups and sprint reviews bearable. I find that if you present a "before I fixed" and "after I did your job for you" measurements at a review it tends to shower laurels on me and shame on the predecessor. They really should know better.

Problem then becomes "Can you fix my code for me?"

Very common lazy, sloppy code.

When you see them thinking "Oh! it makes things faster!" and the same cockwombles proceeding to create multiple dictionaries on every-single-damn-iteration-with-the-same-source you know it's time to leave.

+1 to the guy who owned up to his ignorance.

Eternal torture in every circle of hell for the "recruitment experts" who think it's a good idea to ask me "would you consider moving to the back end of no where with a 50% salary cut?"