"Let's go for the low hanging fruit first" 🤢

"I think we should do some market research" 🤢

"Yeah that is also on my radar" 🤢

OKAY YOU FUCKING CUNT, STOP WITH YOUR PATRONIZING SHIT.

FIRST OF ALL, ARE YOU REALLY SO SMALL MINDED THAT YOU CAN'T REACH ANY HIGHER? THIS TREE IS FUCKING RAW AMD BARE ON THE BOTTOM, WITH YOUR FILTHY CLAWS GRASPING FOR ALL THOSE EASY NARROW FIXES.

SECONDLY, A FUCKING EMAIL SURVEY WITH BIASED QUESTIONS ANSWERED BY 3 HOBOS IS NOT BLOODY MARKET RESEARCH.

THIRDLY, IF THIS NUCLEAR ICBM OF AN INFRASTRUCTURE PROBLEM IS ON YOUR RADAR, MAYBE STOP FONDLING YOUR SWEATY BALLS FOR A MINUTE AND TAKE ACTION.

"Okay lets peel this onion, so we hit the ground running" 😩🤢😞

NO, LET'S NOT "HIT THE GROUND RUNNING", YOU'RE GOING TO FUCKING TRIP AND MESS UP YOUR FACE EVEN MORE. HOW ABOUT GET YOUR PILE OF SHIT IN ORDER FOR ONCE, PREPARE FOR A MEETING? HOW ABOUT THOUGHTFUL ACTION, SOME FEATURE DESIGN?

"No, just implement it quick and dirty" 🤢😡👿

OH YOU WANT IT QUICK AND DIRTY? IS THAT HOW YOU FUCK YOUR DAD AS WELL?

"Let's evaluate the fix in a few weeks. We really had good synergy here team" 🤢😫

YEAH SURE, LET'S EVALUATE THIS.... BUT LET'S EVALUATE IT RIGHT NOW: 😡

"Ahem....

1. You're always late for meetings.
2. After 6 months, you still barely know what we do as a company, you still don't know the teams, and you still don't know the product.
3. You do not listen to engineers flooding you with red flags, requiring time for a redesign to fix serious scaling issues.
4. Everything must be a quickfix, nothing is allowed to require thought, because you CAN ABSOLUTELY NOT think ahead for more than 30 seconds.

OH AND IF YOU EVER AGAIN COVER UP ONE OF YOUR MANY SHORTCOMINGS WITH THAT FUCKING SLIMEY DOUCHEBAG MANAGER VOCABULARY OF YOURS, LET'S SEE HOW MUCH SYNERGY YOU FEEL WHEN YOU'RE DEEPTHROATHING A CACTUS."

This is my most ridiculous meeting in my long career. The crazy thing is I have witnessed this scenario play out many times during my career. Sometimes it sits in waiting for a few years but then BOOM there it is again and again. In each case the person that fell into the insidious trap was smart and savvy but somehow it just happened. The outcomes were really embarrassing and in some cases career damaging. Other times, it was sort of humorous. I could see this happening to me and I never want it to happen to you.

Once upon a time in a land not so far away there was a Kickoff Meeting for an offsite work area recovery exercise being planned for our Oklahoma locations. Eleven Oklahoma high ranking senior executives were on this webinar plus three Enterprise IT Directors (Ellen, Jim and Bob) who would support the business from the systems side throughout the exercise.

The plan was for Sam Otto, our Midwest Director of Business Continuity to host this webinar. Sam had hands-on experience recovering to our third party recovery site vendor and he always did a great job. He motivated people to attend the exercise with the coolest breakfasts and lunches you could imagine. Donuts, bagels, pizza, wings, scrumptious salads, sandwiches, beverages and desserts. He was great with people and made it a lot of fun.

At the last minute Charles 'Don't Call Me Charlie' Ego-Smith, the Global Business Continuity Senior Vice President, decided to grand-stand Sam. He demanded the reins to the webinar. Pulled a last-minute power-play and made himself the host and presenter. You have probably seen the move at some point in your career. I guess the old saying, 'be careful what you wish for' has some truth to it - read on and let me know if you devRanters agree...

So, Charlie, I mean Charles, begins hosting the session and greets all of the attendees. Hey, good so far! He starts showing some slides in the PowerPoint presentation and he fields a few questions, comments and requests from the Oklahoma executives. The usual easy to handle requests such as, 'what if we are too busy to do recover all systems', 'what if we recover all of our processes from home', 'what if we have high profile visitors that month?' Hey you can't blame them for trying. You are probably thinking to yourself, 'been there - heard that!' But luckily our experienced team had anticipated the push-back. Fortunately, Senior Management 'had our backs' and committed that all processes and systems must participate and test - so these were just softball requests, 'easy-peasy' to handle. But wait, we are just getting started!

Now the fireworks begin. Bob, one if the Enterprise IT directors started asking a bunch of questions. Well, Charles had somewhat of a history with Bob from previous exercises and did not take kindly to Bob's string of questions. Charles started getting defensive and while Bob was speaking Charles started IM'ing. He's firing off one filthy message after another to me and our teammate Sam.

'This idiot Bob is the biggest pain in the ass that I ever worked with'; 'he doesn't know shit', 'he never shuts the f up', 'I wanna go over to his office and kick his f'in ass...!'

Unfortunately...the idiot Charles had control of the webinar and was sharing his screen so every message he sent was seen by all of the attendees! Yeah, everyone including Bob and the Senior Oklahoma executives! We could not instant message him to stop as everyone would have seen our warnings, so we tried to call Charles' cell phone and text him but he did not pick up. He just kept firing ridiculously embarrassing dirty IM messages and I guess we were all so stunned we just sat there bewildered. We finally bit the bullet and IM'ed him to STOP ALREADY!!! Whoa, talk about an embarrassing silence!

I really felt sorry for Bob. He is a good guy. Deservedly, Charlie 'Yes I am going to call you CHARLIE' got in big time hot water after the webinar with upper management. For one reason or another he only lasted another year or so at our company. Maybe this event played a part in his demise.

So, the morale is, if you use IM - turn it off during a webinar if you are the host. If you must use it, be really careful what you say, who you say it to and pray nothing embarrassing or personal is sent to you for everyone to see.

Quick Update - During the past couple of months I participated on many webinars with enterprise software vendors trying to sell me expensive solutions. Most of the vendors had their IM going while doing webinars and training. Some very embarrassing things came flying across our screens. You learn a lot reading those messages when they pop-up on the presenters' screen, both personal and business related. Some even complaints from customers!

My advice to employees and vendors is to sign-out of IM before hosting a webinar. Otherwise, it just might destroy your credibility and possibly your career.

MD: The client doesn't care how sloppy your code is. They're not paying for the solution, they're paying for the result. If there's a quick and dirty option take it.

"I strive for code quality and maintainability. I actually do. And i will not work for a company that does not care about it and just wants something done as fast as possible.
The only time i will do something quick and dirty is if it's actually urgent. And even then with one condition - my next task will be to fix it properly.

I do not care about your deadlines. I will do my best to meet them, but not at the expense of code quality. I've seen too many projects fall into technical debt, where productivity is so low, that the only way to move forward is hire more people and start working on a project 2.0

And please do not lie about how great your company is, if it's not. These kind of things surface very soon, and you will have wasted both of our time, because as i said - i will not work for a company that does not care about code quality."

you think i'll ever get a job again if i put this on my CV ? :D

Probably the jankiest fan that I've ever built 😂
I just need it to not sweat gallons on the bus and needed it to be done quick and dirty to not miss the bus so meh.. kinda curious about the looks that I'll get for using this thing to cool myself though 🙃

So I watched this video that tries to convince people, that the jQuery library isn't really best practice anymore and showed how you can achieve basic tasks with vanilla JS, aswell as some frameworks (Vue, React, Angualar) and how they handle interactions with the DOM.

It also talked about how nearly every JS question on SO has top answers using jQuery, and how that's a bad thing.

But what I found in the comment section of this video was pure horror: So-called "Developers" defending jQuery to the death. Of course there were some people who made some viable arguments (legacy code, quick & dirty projects), but the overwhelming majority were people making absurd claims and they seemed quit self-confident.

GOSH!

Want an example?
Look:

How to make loading animation in terminal quick and dirty

Loop through these, print them, and replace them with the next one
\ | / --

> Make a small game.
> Do it in Rust because why not.
> Decide "Hey, why not make the game objects have Lua scripts for their logic because Lua is easier to do quick and dirty code in than Rust?"
> 5 hours later delete all the code related to running the Lua in Rust because AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

The initial version of DOS was called QDOS – Quick and Dirty Operating System. The bullshit they tel you about DiSk oPeRaTinG sYsTeM is a lie. It was renamed when MS acquired it.

How difficult is it to do things and do them properly? Clearly in 2019, very difficult. And why on Earth would you do things properly, when there's get rich quick schemes, shortcuts to be found and taken, and that filthy filthy legal tender. If the shitty implementation makes a profit, why do it properly? Makes no sense.

Except it fucking does. And you know why? Because of the guy that comes after you, that works with your fucking bullshit implementation and probably curses you to the moon and beyond in the process. Just like you probably did with the guy that came before you, with that bullshit you got tasked to work with. Don't be that guy. And don't be that guy to the next guy.

Still with me? Good. Here's the thing. You can do [insert job here] quick and dirty. But you're guaranteed to be checking back on it and fixing the crap later on. Or worse yet, someone else will be cursing you to the moon and beyond while they are fixing / working around your crap. So why not do it right in the first place? Is this why we can't have nice things?

Returned from holiday. Got a Ticket that literally reads: "I commited some stuff to master. Some are quick and dirty fixes. Please Review."
I called him and was told he made some architectural changes without talking to anyone (again) and now the tests are broken and I shall repair them.

Dear colleague. ARE YOU FUCKING SERIOUS?!!!

Rage is beyond imaginable.

Me on the inside whenever I hear the PM say quick and dirty

JavaScript is very similar to duct tape, if it doesn't work, you haven't used enough.

A colleague had to show up for a demo in 10 minutes, and urgently needed to fix some CSS.

I told her the right way would take more than 10 minutes. The quick and dirty way was to add an `!important`.

I made her write a comment:
`// TODO: Fix this hack made for the demo dated blah blah`

TIL if you know the password for a WIFi SSID, you can replicate it with your hardware. All devices that have credentials for that SSID will connect to yours if your signal is stronger. The encryption just needs to be the same (wpa2/wep) The underlying UUID doesn’t matter.

Not bad for a quick and dirty man-in-the-middle attack. The WiFi spec needs a bit more work.
TLS all the things!

If you give the client a choice of:
- Quick and dirty solution which results in tech debt
- Better solution that would be cheaper in long run

They will always choose the first without fail..

Init Mud. (A poem)

A Giant Ball of Mud.
Haphazard in structure.
A sprawling, enthralling, duct-taped warning,
Of things to come.

Tumbling down a well-worn path
Of untamed growth and aftermath.
Into Spaghetti-code Jungle.

Where quick and dirty wins the day
And warnings spoken hold no sway
Or fall on deaf ears in the undergrowth.

Tumbling.
Gaining weight.
Bits stuck on.
Bytes taken out.
Patches,
On top of patches,
On top of obsolescence.

Hacked at, uploaded
All elegance eroded.
Made and remade
Then duplicated
Relocated
Refined and redesigned
Suffocated by expedient repair after expedient repair
The original self no longer there
Replaced by something
Unwieldy.

Design resigned to undefined
An architectural mystery
Whose function can no longer be
Seen or gleaned
From obfuscated in-betweens
Of classes
Made and remade
Duplicated.
Abused.
A squirming library of disused.
Pulled at, prodded, committed
Corners cut and parts omitted.
Bug ridden branches fused to a rotting core.

The structure...
The system...
The content...

Mud.

Client wanted me to implement a "fix" for the site beeing to large on mobile. He had to scroll too long. I implemented a quick fix and turned the biggest list into a carousel with slick slider (awesome 5-minute-fix btw.)

But it depends on jQuery. I feel so dirty now. The sites amount of JavaScript is three times bigger now, too. Please, don't judge me. 😩

!rant
To all the hardcore Vim users:

Why do you prefer Vim over IDEs ?
Are you faster/more efficient using Vim ?
What are it's main benefits/drawbacks in your view ?

I'm familiar with it, but nothing more than that. Usually use it just for quick and dirty edits, but that's all.
I'm seriously considering making the change to Vim and I can't explain why. Read an article once why Vim is still relevant and some features as to why that is, but I'd like to get more opinions on it.

Giving a short talk on technical debt at our monthly meeting tomorrow. I hope it helps people in my organization understand why we need to take care of all the quick and dirty work we do. I'm tired of people saying how long updates take and the reason is because we cause the problems.

My org (of which i'm basically CTO) has this administrative tool that a team uses to combat spam and scams, which is quite the problem for us.. the tool was written like 9 years ago, by my predecessor, very quick & dirty and unaesthetic and without input from those who would use it as far as interface or UX... it got modded a little a few years later by a kind of amateur coder who was at the time on the spam control team, and now there's this new maybe slightly less amateur coder guy on the team who has written this amateur tool that scrapes data off our site and massages it and stores it on his own server and then provides a better interface, or so they say.... this is all because for a couple of years people didnt want to "bother me" with a request to improve our internal tool, they thought I was "too busy" doing other things... so instead this outsider has built this stupid thing that lives on his own personal server and so now we have these problems to do with performance, security, privacy for user info, etc etc... someone please shoot me....

Wonderful experience today

I'm scraping data from an old system, saving that data as json and my next step is transforming the data and pushing it to an api (thank god the new system has an api)

Now I stumbled upon an issue, I found it a bit hard to retrieve a file with the scraper library I'm using, it was also quite difficult to set specific headers to download the file I was looking for instead of navigating to the index of the website. Then I tried a built-in language function to retrieve the files that I needed during the scrape, no luck 'cause I had to login to the website first.

I didn't want to use a different library since I worked so hard and got so far.

My quick solution: Perform a get request to the website, borrow the session ID cookie and then use the built-in function's http headers functionality to retrieve the file.

Luckily this is a throwaway script so being dirty for this once is OK, it works now :)

Mozilla you stinking kangaroo pouches!

When you set an object's CSS translation via JS like so:
obj.style.transform="translate(0px,0px)";
and then read it back, every browser including FF until 66 gives this, with additional space:
"translate(0px, 0px)"

However, bloody FF 67 returns "translate(0px)". Because it's always a good idea to just introduce external changes nilly-willy, right?

That screwed up my crappy string slicing because it relied on the presence of the comma. It was a quick and dirty solution, but with additional future proof if/else logic, it wouldn't even be quick anymore.

Besides, the whole string slicing looked like yo-yo code anyway so that I instead added shadow integer variables to the objects. That solution not only works, but is even faster.

The beginning of my next blog post... at 6am.... Guess who hates his job and why?

<h1>Thinking Before You Code<h1>

The choices you make when you code a part of a program, or even the program itself, impacts everything around it. The importance increases as the size and the scope does.

Quick and dirty simple scripts that get a simple job done and rarely needs changing… fine.

A bunch of quick and dirty hacks all pieced together as part of a giant application... that constantly changes? That's duct tape code that will bite you in the ass later or will give birth to a maniacal raging psychopath that wants to kill you.

<b>SOLID, design patterns: saving yourself and others from you</b>

TBC...

I changed my shirt and now it looks like we're evil rivals.

I remember him telling me he has the dilemma of "clean css solution" and "quick and dirty js solution" and he always takes the second one.
My dilemma is the other way around: "Clean js solution" or "hacky, dirty css solution". I always take the second one if possible..

Quick and dirty job to get some data into a DB wasted my entire evening.

Created table with few columns, tried writing to it from NodeJS app and it kept complaining I wasn't providing values for columns that didn't even exist. After ages pissing about decided that the DB gods had cursed this particular table so created a second one with same DDL. Now it worked first fucking time. Then it finally dawned on me, I'd managed to pick a reserved table name and the RDBMS didn't think to give me a warning when I created it. Not only did it not warn me but it kept going as it nothing was the matter and didn't report the extra columns on a SELECT *.

That feeling when you inherit a script to automate something that takes 10 seconds. Why would they even write this? It's not like the task is hard....

...

And why would they write it this way? I'm sure if I just move this part and ....

That feeling when you spend several hours improving and redesigning a perfectly functional script to automate a 10 second task for zero gain aside from cleaner code. "But the code for this quick-and-dirty script I'm never going to look at again looks so much better now!"

... If only it did a bunch of complicated parsing, regex matching, and error checking just so I can answer one less prompt.... Unless that parsing fails. Then it should still ask me for that prompt... And also validate that the answers I give are valid and correct....

That feeling when you spend a whole nother day starting from scratch to implement error checking and complex parsing logic knowing full well the original task takes 10 seconds to do manually and is needed at most twice a day (for a grand total of 20s a day)

WHY AM I LIKE THIS?!?!?!

I am in no way a senior dev, in skill or compensation. I have completely inherited all rank and responsibility from all the folks who came before me and got canned.

For the last year, I have led and managed a team of juniors working on the only application making my company any money, while everyone else has been building new shit from scratch; every day my only two goals are to impart my team with as much knowledge as I possibly can give them, and to keep production from blowing up.

Until now, I've apparently kept everyone in the dark about the fact that I'm just skating by by "going with it" and able to google the answers just before they can ask the question. But now that the pandemic has hit, all future projects are put on hold indefinitely, and the company is pivoting all other devs under me. Now we have "true" seniors ripping the app apart and injecting code without thinking once to actually read the code base and analyze how the application was designed to work, because they are under orders from our serial entrepreneur of a CEO to "get it done, quick and dirty" and meanwhile as the app further destabilizes, the c-suite team looks to me.

So half the time I have no clue what I'm doing, but I can't let them know that. I mean at least I'm still gainfully employed, I still make way more than I ever did before in my life. I'm *reasonably* happy with what I do for a living. And if they can me, the company will be dead in the water, because I'm the only dev who understands intimately how to change the system and add new features without completely bricking it.

Am I doing it right, or nah?

For those of us OCD Sheldon Cooper types out there, programming can get very annoying.

For example, I want to do everything as efficient as possible but sometimes situations require "live with it" or "quick and dirty" solutions, which grinds my teeth because I'm not applying perfection in everything and a laid back attitude is against my personality, much like Sheldon. It's the same annoyance as when Penny knocks twice but not thrice at the door.

This sure is easier for brogrammers.

sigh, I guess I have to learn javascript.
u know, as a devop/prod/backend engineer, i thought i would be exempt, but world wide web of "one more thing a dev should do" won't let me have it :(
so, any of you have a quick and dirty guide to catch up with the latest essential components of javascript as an experienced dev who absolutely knows nothing about js?

back into some quick and dirty opencv scripting for the afternoon to try to get a report out the door, and boyhave my variable names become, shall we say, gigidy inspiring:

longexposure = np.uint8(cumimage/float(len(ims)))
stacked = np.hstack({cumimage, longexposure})

I'm looking for advice...

Has anyone experience with the AWS cloud?
I'm arguing with my future company partner about it. He's totally old school but is responsible for the server stuff... He does the backend for a urgently needed webapp and it takes so long (he still works in his old company the next months).

The frontend (my part) is nearly ready. I could work on the backend fulltime, but I would choose AWS Appsync with offline sync etc. First it would be quick and dirty, because it's really urgent.. he wants to do all super perfect...

How can I handle that? I talked to him many times about that, but he always says it should be done right and takes time. but for me, it's to much time. The webapp is relatively small and the work now already takes about 2 or 3 months..