- Hello! Gordon's pizza?
- No sir it's Google's pizza.
- So it's a wrong number?
- No sir, Google bought it.
- OK. Take my order please ..
- Well sir, you want the usual?
- The usual? You know me?
- According to our caller ID, in the last 12 times, you ordered pizza with cheeses, sausage, thick crust
- OK! This is it
- May I suggest to you this time ricotta, arugula with dry tomato?
- No, I hate vegetables
- But your cholesterol is not good
- How do you know?
- Through the subscribers guide. We have the result of your blood tests for the last 7 years
- Okay, but I do not want this pizza, I already take medicine
- You have not taken the medicine regularly, 4 months ago, you only purchased a box with 30 tablets at Drugsale Network
- I bought more from another drugstore
- It's not showing on your credit card
- I paid in cash
- But you did not withdraw that much cash according to your bank statement
- I have other source of cash
- This is not showing as per you last Tax form unless you got it from undeclared income source
-WHAT THE HELL? Enough! I'm sick of Google, Facebook, twitter, WhatsApp. I'm going to an Island without internet,where there is no cell phone line and no one to spy on me
- I understand sir, but you need to renew your passport as it has expired 5 weeks ago..

DRY in command line..

Three male programmers were in the bathroom standing at the urinals.

The first programmer finishes, walks over to the sink to wash his hands. He then proceeds to dry his hands very carefully. He uses paper towel after paper towel and ensures that every single spot of water on his hands is dried.

Turning to the other two, he says, "At Windows, we are trained to be extremely thorough."

The second programmer finishes his task at the urinal and he proceeds to wash his hands. He uses a single paper towel and makes sure that he dries his hands using every available portion of the paper towel.

He turns and says, "At Macintosh not only are we trained to be extremely thorough but we are also trained to be extremely efficient."

The third programmer finished and walks straight for the door, shouting over his shoulder.

"At RedHat, we don`t PISS on our hands."

Do you ever feel coding fatigue?

My dev mana has run dry, I've hit my rate limit.

That moment where your brain thinks "I should finish building this React project, it's good for my portfolio" or "I should really work on fixing this query performance issue, I already know what the problem is" — but your stomach churns at the thought of having to interpret even a single line of code?

The last few days it really does feel like a physical illness, a nauseated feeling whenever I open an IDE. I have written about 12 lines of code since Monday.

It goes beyond writer's block, it's not a lack of focus or inspiration, it's a big knot in my head of everything that's wrong and inconsistent in development, and it causes feelings of dread, desperation and revulsion when trying to wrap my head around the simplest stuff.

Does anyone have good tips to overcome this feeling, something faster and less savings-account-destroying than "take a sabbatical year and travel the world riding an emu"? (seems tempting though)

Every day.

I am a PHP developer.

Yeah, "another PHP is awful" rant... no, not really.

It's just unsuitable for some ambitious projects, just like Ruby and Python are.

First of all, DO NOT EVER use Laravel for large enterprise applications. The same goes for RoR, Django, and other ActiveRecord MVCs.

They are all neat frameworks for writing a todo app, as a better-than-wordpress flexible blogging solution, even as a custom webshop.

Beyond 50k daily users, Active Record becomes hell due to it's lazy fat querying habits. At more than a million users... *depressed sigh*.

PHP is also completely unsuitable for projects beyond 5M lines of code in my opinion. At more than 25M lines... *another depressed sigh*.

You can let your devs read Clean Code and books about architecture patterns, you can teach them about SOLID & DRY, you can write thousands of tests... it doesn't matter.

PHP is scaffolding, it's made of bamboo and rope. It's not brick or concrete. You can build quickly, but it only scales up to a certain point before it breaks in multiple places.

Eventually you run into patterns where even 100% test coverage still doesn't guarantee shit, because the real-life edge cases are just too complex and numerous.

When you're working on a multi-party invoicing system with adapters for various tax codes, or an availability/planning system working across timezones, or systems which implement geographical routefinding coupled to traffic, event & weather prediction...

PHP, Python, Ruby, etc are just missing types.

Every day I run into bugs which could have been prevented if you could use ADTs in a generic way in PHP. PHP7 has pretty good typehints, and they prevent a lot of messy behavior, but they aren't composable. There is no way to tell PHP "this method accepts a Collection of Users", or "this methods returns maybe either an Apple or a Pear, and I want to force the caller to handle both Apple/Pear and null".

Well, you could do that, but it requires a lot of custom classes and trickery, and you have to rewrite the same logic if you want to typehint a "Collection of Departments" instead of "Collection of Users" -- i.e., it's not composable.

Probably the biggest issue is that languages with a (mostly) structural type system (Haskell, Rust, even C#/JVM languages to some degree, etc) are much slower to develop in for the "startup" era of a project, so you grab a weak, quick prototyping language to get started.

Then, when you reach a more grown up phase, you wish you had a better type system at your disposal...

My boss isn't really a developer. He isn't part of the development team and doesn't know any technical details about the product. He doesn't want to code, "too much effort", he just wants to boss. But he wrote some php in the early 2000's and is really, really proud of his codecademy html/css badge...

And that makes him dangerous.

Today I hear him talk from behind his laptop: "Right, we have this page for creating management groups, but we can't edit them yet. I can fix that!"

This task is literally on the current sprint, but he doesn't know that because he doesn't attend scrum meetings and ignores everything people say to him.

Me: This smells like probable cause, let's look with suspicion over his shoulder.

Boss:
"OK, right-click create.blade.php -> copy.
then right-click directory -> paste.
now just rename file to edit.blade.php!"

I start walking to the office kitchen.

Boss mumbling in the background:
"Now all I need to do is just copy the whole method in the controller, change the post url in the form, and modify the <h4> at the top, so it says edit instead of create."

Boss, looking at me now:
"This is so easy... creating and editing is almost the same thing, you can just copy paste all the code from one template to the other! I don't understand what you developers are always complaining about!"

Me: *Hands him a roll of paper towels*

Boss: "What is that for?"

Me: *points at code*

My boss literally spends half an hour finger-fucking his phone on the mobile site to find "bugs", that I can't replicate. A combination like: swipe, pinch, landscape, portrait, back pinch, open new tab, close tab, ash cigarette on phone, dunk in toilet, dry, double tap... Aha I've found a bug, there's 0.5 pixel line of space between the bag header and the browser bar.

Dude, FUCK automated bathrooms.

First of all, what the hell is so complicated about making a motion sensing faucet that works? Why does it *need* to be motion sensing? I stand there for 5-10 seconds with my stupid soapy hands extended, waiting for a squirt of the divine liquid.

And then the immediately following experience isn't much better. Motion sensing paper towel dispenser. The first go works fine, but it always dispenses half of what you need to get your grimy paws dry. So you go in for seconds, and it just flat out ignores you. Leaves you on read. You flap your pathetic noodle arms at it again. It isn't happening. Please wait 3-5 business days.

Oh, and god forbid you forget to cover the automatic toilet with a few wasted squares. Lean into a shit ONCE and you've just been prematurely flushed. Your ass is misted with the cold, unforgiving equivalent of an automatic insult.

Asshole design

I was sleeping.....

May dad was feeding our newly furnished outer walls of our house with water....

I was unaware of what he was doing...

I dont know what exactly he was supposed to do....

But when I opened my eyes....

I saw a stream of water straight way coming from the window entering my cpu which was placed on a table exactly at the window....

I shouted out as loud as possible....

I was so lucky I previous night I turned it off shut off the switches cuz there was nothing to download....

I deassembled whole cpu kept it for 3 days to dry....

And bam it worked like a charm....

Saved my entire life....

Guy from work: "I have a messy coding style ¯\_(ツ)_/¯".

No, you have a bad coding style. Your repetitive uncommented spaghetti code isn't an artistic expression of your quick imaginative mind jumping from thought to thought. It's a horrible mess that shows me that either you can't do any better or you don't care.

I really hate this company.

The code is a disaster. Every single other employee is a salesperson. Nobody has any bloody clue what I do or how difficult it is. They don't care about stability (unless things are crashing), maintenance (until crashing), code quality (until it delays features), or anything apart from shiny new features they can sell. The boss (the king salesman, if ever there was one) doesn't know how to manage, but tries to by acting like his "nice asshole" self -- he's an asshole that gives you passes, makes sure it's bloody obvious that he's doing it begrudgingly, yet everything is still absolutely your fault. If he arbitrarily decides it's too much your fault, he stops being "nice" and flips out on you in front of everyone. That's a "nice asshole": an asshole who can barely even pretend to be nice.

Fuck him.

And you know what? I really hate having to work next to these fucking birds, too.

Today was our weekly conference call, and I was both late and unprepared. I was too focused on my work, and got a ping 4 minutes into the meeting, so I obv didn't have time to prepare. Boss was also pissy today, and I didn't have much to show for my week, thanks to lots of little "OMG NEED ASAP" shit projects that all took too long, pushing back what I was actually supposed to work on. Which didn't get finished, of course, and today that project was "the most important" -- I suspect simply because it wasn't finished. AGADJFSKL. Cue the birds fucking screaming and never fucking shutting up no matter what I did. Blanket? No effect. Spray bottle? SCREAM MORE! Boss was yelling at me, the birds were screaming, and I couldn't think. Goddamn fucking disaster.

and yes, we have a macaw. A macaw and over 20 cockatiels. Said macaw decided today was a lovely day to just fucking SCREAM non-stop, and the tiels were doing their best to keep up. Thinking clearly during this cacophony? Not gonna happen.

Wait, "go elsewhere," you say? Somewhere quieter? Where is this "elsewhere?" We live in a fucking tiny house, and during the call it was (and still is) filled with sleeping people, and surrounded by a fucking desert. Who the fuck thought living in the desert was a good idea, anyway? Like, seriously. What brainless moron thought "You know what? This is a great place! Let's settle down right here," while trudging through the scorching sand and dust, looking at the basically lifeless horizon filled with large, hot, dry, dusty, barren rocks (aka "mountains"), and fucking dying from thirst? Probably someone so delirious from heatstroke they never actually recovered, and continued raving that it's a goddamn paradise to their heat-addled imbecile followers. I really hope they hallucinated a la-z-boy in place of a hedge of teddybear cholla and died an excruciating and prickly death. Fuck that guy/girl, too.

But I digress.

I seriously need an office that isn't a 30 min drive into gang-central. I'd work outside, but I live in the middle of the bloody fucking desert, and get heat exhaustion within about half an hour. Everywhere else in the house people bother me almost incessantly.

just. FUCKING FJASKLDFJGAG.
I HATE THIS PLACE SO SO SO MUCH.

'I've had such Zen lately,' Alex said. Maybe then, but lately? I've just been too exhausted and burned out from putting up with all this shit to get angry. Days like today? I could pour kerosene over everything and laugh as it all just burned to ash.

Me: "DRY (Don't Repeat Yourself) is a good mentality."
Other devs @ company: "I'm so wet rn."

Friend of mine killed his MacBook with some Softdrink.

Just poured it all over his poor a1502.

He let it dry for a few days, it starts to work again.
Except the battery.

Goes on Amazon and buys a new battery.

New battery doesn't work either and so he tells me about it and I as stupid as I am couldn't resist the temptation to finally work on a MacBook like my "hero" Lois Rossmann does.

So turns out the board is good.
Cleaned it up and basically nothing happened to it.

So what's the deal with "los batlerias"?

The first got hit by liquid, the second had a broken connection to a cell.
That could have happened through my friend, installing it without testing it first, or at the seller, so it being a DOA battery.

Now away from the stupidity of my friend and the situation to the actual source for this rant.

Once something happens to a modern Managed battery, the Battery Management System (BMS) disconnects the voltage from the system and goes into an error state, staying there and not powering anything ever again.
For noobs, it's dead. Buy a new one.

But It can be reset, depending you know how to, and which passwords were set at the factory.
Yes, the common Texas instruments BQ20Zxx chips have default passwords, and apple seems to leav them at default.

The Usb to SMBus adaptors arrived a few days ago and I went to prod the BMS.

There is a very nice available for Windows called BE2works, that I used the demo of to go in and figure out stuff. The full version supports password cracking, the demo not.

After some time figuring out how Smart Battery Systems (SBS) "API" works, I got to actually enter the passwords into the battery to try get into manufacturer and full access mode.

Just to realise, they don't unlock the BMS.

So, to conclude, my friend bought a "new" battery that was most likely cut out of a used / dead macbook, which reports 3000mah as fully charged instead of the 6xxx mah that it should have, with 0 cycles and 0hours used.
And non default access.

This screams after those motherfuckers scaming the shit out of people on Amazon, with refurb, reset, and locked fucken batteries.

I could kill those people right now.

Last but not least,
My friend theoretically can't send it back because I opened the battery to fix the broken connection.
Though maybe, it'll get send back anyway, with some suprise in the package.

I fucking hate Internet of Things, I think that it's a ridiculous idea to connect things, that work perfectly fine, to the internet.
The 'convenience' you get is minimalistic and most of the time non existent.
It is also often insanely insecure and expensive. The burdans it brings with it most of the time just outweigh the positive sides of it.

Now today happened something that made me hate it even more. Today was the First Lego Lego (Lego competition with ev3 robots, etc.) and one part of the tournament is to find a solution for a given problem. This year the general topic was hydro-dynamics and so the problem was how you can reduce water usage and 'save' water.

Our idea was to make reusable coffee cups and give them to the local coffee shops. One time use paper cups use take around 400ml water when produced) Basically you buy a cup once for 5 bucks and you get your coffee served in it. After drinking the coffee you return the cup to a local cafe and get a chip as pawn. When you buy your next coffee, you give them your chip and get it served in another reusable cup. The are at the moment already around 1000 cups going around the city.

Now this was our idea and we got ranked third. I am not too mad about our rank but what really drives me fucking mad is the team who ranked first.

Their idea was to make a pump (using an arduino) and a humidity sensor which you stick into a plant and the pump pumps water when the plant is too dry.
However (you probably guessed it already) they went a step further and connected it to the internet. They also made a web 'interface' for it so you can control the pump with your smartphone / computer / smartwatch / tv / whatever the fuck is connected to the internet nowadays 'thanks' to the iot 'revolution'.

So it is a pump that waters your plant when it is too dry BUT it is also connected to the internet.

WHY THE FUCK DOES THIS HAVE TO BE CONNECTED TO THE INTERNET.

"Oh look it is connected to the internet, wow awesome, oh it is also 'smart'. oh cooool. Nice I don't have to water my plants anymore"

A funny thing is that one of my friends built basically the same thing without connecting it to the internet. He built a small box with a pump and a humidity sensor that measures if the dirt is too dry and then waters the plant. It checks every few hours and the also is a small 16x2 LCD and a knob that you can turn to control how much water it should give the plant each time it waters it. He built it and I programmed it for him. Works perfectly fine and I don't see any reason why there should be any need to connect something like this to the internet.

Anyway we got ranked third, they first. I guess we should connect our coffee cups to the internet in some way ...

FUCK!!! FUCK IT ALL. FUCK YOU AND YOUR CRAPPY BULLSHT UNDOCUMENTED AND OUTDATED API.

YOUR DATABASE SERVER BACK-END HAS TO BE THE ONE MANAGING THE DISPLAY DATA FOR ITS WEB AND MOBILE CLIENTS. NOT THE OTHER WAY AROUND, DAMN IT.

I'M NOT GONNA SIT HERE ALL DAY HARD-CODING ALL YOUR SERVER'S INADEQUACY.

MAKES ME WONDER DO YOU EVER USE DESIGN PATTERNS OR APPLY DESIGN PRINCIPLES? DRY AT LEAST? DON'T FUCKING REPEAT YOURSELF, DAMN IT.

I CAN'T WAIT TO LEAVE THIS PLACE FOR GOOD.

Why is the ternary operator such a hated thing? I constantly hear people saying it's less readable, confusing, etc.

I think it's a beautiful, useful, and important operator and I use it constantly wherever readability won't be much affected.

How can you justify a repetitive if/else structure over a ternary, given that you're sure you're not going to put anything else in the ifs?

Whatever happened to DRY?
Whatever happened to KISS?

If those guidelines are what you code by, what's the excuse not to use it?

Because you can't read it as well? Familiarity breeds comprehension and legibility, my dudes.

Background: I'm not drunk yet, BUT I'M WORKING ON IT.

okay.

I just finished a second sprint on my React app. The first was to build a merchant onboarding flow. The second was to do substantial cleanup as I learned more about react/redux, and to create a "supply order" flow -- basically purchasing marketing materials and services. I finished that in a week, and I'm pretty proud. api-guy wanted it done in a day. i laughed. he probably could have, but it would have been a copy of the code in a new repo with some lines changed.

ANYWAY. it's all done and It's super pretty and works amazingly well. It has both the onboarding flow and the ordering flow, with a nice pop-out sidebar for navigation, namespaced actions, etc. Everything is pretty clean. I even added a cart to the ordering (despite everyone telling me not to) because wtf, what if someone wants to order TWO items? dumbasses. So I made that. it's sexy.

Anyway, it's all done and shiny and fancy and wonderful and I'd *love* to share screenshots if only it didn't give away where I worked. :<

... but the point of the rant!

After the first sprint, I made a copy of the repo so I could rework it and add more functionality without touching the original. (Hey! That's what a branch is for, right? Why didn't I branch it up?
well, read on)

I knew we were going to have multiple separate flows for this app: onboard, ordering, merchant tools, admin tools, support, etc. So, I wrote its server portion (the webpack builder + http server) so it would serve the same app at whatever url the user hit, and set a cookie containing that host+url. This allows the app to serve different content (basically showing/hiding content) based on the URL and future login roles. If someone hits /order, it would hide everything but the order flow. If they're a merchant, it would show all the merchant views plus ordering, etc.

tl;dr This way I can use the same codebase for multiple sites, drastically simplifying development, branding, and what have you. This new app could obv also be a drop-in replacement for the original onboarding project because of the above.

HOWEVER. this apparently isn't good enough for api-guy. He's terrified that adding/updating future components will affect all the existing content somehow.

so.

now we have three repos for basically the same codebase. 1) onboard aka "surfboard", 2) ordering, 3) merchant tools, aka "ferrari" (the "future" app).

Except.
1) "surfboard" is a very old version of the code. 3) "ferrari" is also old, since 2) "ordering" has newer content in it now.

... and somehow this is better?
fuck if i can figure out how.

His reasoning is "well, you won't be touching surfboard or ordering for 6 months, so now you don't have to worry about it." Sure, except, you know, it'll be a pain in the ass in 6 months now when I have a crapton of code and branding to redo. ffs.

Oh. We also have three Heroku pipelines for these three repos. for the same codebase.

and now you know why i'm drinking.

Gotta keep that code DRY...

"It should be noted that no ethically-trained software engineer would ever consent to write a DestroyBaghdad procedure. Basic professional ethics would instead require him to write a DestroyCity procedure, to which Baghdad could be given as a parameter." -- Nathaniel S. Borenstein, computer scientist

So my localization algorithm actually runs onboard my YouBot :)
My paper was basically torn apart by my professor, so I had to write some new classes and redo the whole experimental section. And all the other sections too. I resubmitted it to him after revisions, and the second iteration was way better - I'm really close to final paper level :)
I told my professor and postdoc that I will appreciate more support and positive feedback, because so far our communication was only very dry criticism. For me it's really devastating, because feeling like I constantly disappoint people just kills me on the inside.
It seems like they took it to heart, they have been nicer to me in the last few days :)

When I asked my brother why he doesn't want me to teach him programming, his answer was: "Because writing code is dry and boring, like math."

Ok then.

How to be super-DRY

My teachers rant: "Who invented whiteboard markers? *trying to write some code on the board, but the marker went dry* What every happened to black boards and chalk. Chalk never gets dry.... I going to have to look that up" LOL, man I love him. He is so old that its funny and cute at the same time

I absolutely hate the way we are taught programming in Indian colleges.

FML #1: I'm pursuing a UG CS course, and this semester, I only had one subject of Computers, that too only 1 credit. The rest with all electronics.

FML #2: In that 1 credit course, we had to make a C++ project which had "data handling". No one cares if you build something cool or not, just that a project should have "extensive use" of data handling.

FML #3: Source code had to be >= 1000 lines. This is the only place where ADDING MORE LINES OF CODES THAN REDUCING IT is appreciated. Had to stuff my code with all kinds of comments and violating the basic principle of DRY.

So, yeah, we're fucked big time. 😥

- Hello! Gordon's pizza?
- No sir it's Google's pizza.
- So it's a wrong number?
- No sir, Google bought it.
- OK. Take my order please ..
- Well sir, you want the usual?
- The usual? You know me?
- According to our caller ID, in the last 12 times, you ordered pizza with cheeses, sausage, thick crust
- OK! This is it
- May I suggest to you this time ricotta, arugula with dry tomato?
- No, I hate vegetables
- But your cholesterol is not good
- How do you know?
- Through the subscribers guide. We have the result of your blood tests for the last 7 years
- Okay, but I do not want this pizza, I already take medicine
- You have not taken the medicine regularly, 4 months ago, you only purchased a box with 30 tablets at Drugsale Network
- I bought more from another drugstore
- It's not showing on your credit card
- I paid in cash
- But you did not withdraw that much cash according to your bank statement
- I have other source of cash
- This is not showing as per you last Tax form unless you got it from undeclared income source
-WHAT THE HELL? Enough! I'm sick of Google, Facebook, twitter, WhatsApp. I'm going to an Island without internet,where there is no cell phone line and no one to spy on me
- I understand sir, but you need to renew your passport as it has expired 5 weeks ago..

"Quality CSS" is much a fucking misnomer. As someone whose been writing this shit at scale for 15+ years I can tell you all CSS code is garbage. The only thing you should do is make sure you don't have name collisions. Classes/components are self contained. And use variables when possible. DRY makes sense usually, but if you're dogmatic about it you shoot yourself in the foot.

Screaming at a coworker?
The INTJ in me has prevented that pretty well in almost every critical devSituation.
BUT one time in the past, I was really close to a level 9001 scream:
This fucker, despite having been told about code formatting guidelines and DRY/KISS multiple times, had the balls to commit such utterly crappy and unreadable code that I almost bursted.
He quickly realized his mistake after I reset the repo to before his push, disabled his Gitlab account and wrote him a simple email containing the text:
"IF YOU EVER COMMIT SUCH SHIT AGAIN, THERE WILL BE UNFORESEEN CONSEQUENCES. GFYS."
After a peaceful coffee and a croissant I decided to re-enable his account. He did good after that.

#Gitlab is currently doing a Dry Run before actual migration on August 11.

In the linked blog-post I found this note:

NOTE to users in Crimea, Cuba, Iran, North Korea, Sudan, and Syria: GitLab.com may not be accessible after the migration to Google. Google has informed us that there are legal restrictions that are imposed for those countries.

WordPress related, get ready for some disgust.

So today early in the morning my boss forwarded me an email from a client, it was about a bug, and asked me if I can have a look at it and fix it.
"Yaay, WordPress!" I thought and opened the page containing the mentioned bug. She wrote that in the italian version of the page, users can select dates in the calendar, which should be disabled, like in the german version.

So yeah, I opened the code. Everything in the function looked perfect. Really. And the Data was also correctly set in the backend of WP.

The function was only 3 lines of code:

- Get the german post ID of the current post (german or italian) by its ID (using a Polylang function)

- Get an Advanced Custom Fields field by name and from a post with the ID from before

- json_encode its content and echo it to a JS var for initialization and later use in some AngularJS.

No fucking missing semicolon, it was fucking perfect like a sunset with your soulmate.

So I tried to find the bug with my personal way of debugging:

"Shitstream Debugging"
When a creek suddenly is full of water mixed with shit, walk upstream through the turds until you reach clear water. This is where the bug is.

=> So I first looked at the HTML source: Turds.
=> Then the ACF field content: Still turds.
=> Then the ID of the german post: Shit stain and turds (var_dump: null)
=> Please god at least $post->ID? Nope, fart smell and turds.
=> Nothing more to check: Clear fucking water and the flowery smell of 99 devVirgins

So it replaced $post->IT with get_the_ID() and it worked like a charm.

Afterwards I feel stupid, but $post->IT worked all the times before...

Conclusion:
FUCK YOU WORDPRESS YOU UGLY PIECE OF HUMAN-CENTIPEDE-PROCESSED-DOGFART.

Thanks for your patience.
Only one beer was sucked dry during the writing of this fucking rant.

It's finally dry enough to apply this. Thanks!!

My boss just asked me for a cheat sheet I have that lists all our app server's paths.

The paths are attached as annotations throughout some Java files.

Anyway I send him the one I have but he asks if he could have an updated one.

Now imagine if I were like most monkeys and had made this cheat sheet by hand....

2 mins easy vs an(other) hour of grunt work

Why is it that I'm the only person on the team that writes utilities to automate boring grunt work while everyone else just does it manually whenever it needed....

Isn't DRY a core principle of being a developer?

I'm the only person that builds utility apps that automate frequent tasks that people keep asking us to do....

In my CS class I turned in some assignments recently. Two of them were extremely similar: one was to test if a number was even or odd, the other to test if the length of a string was even or odd. I completed the first one and then started to work on the second one and decide to just call the isEven method from the previous lab so I can follow DRY (Dont repeat yourself) and not have to write the same code again. I turned it in and she took off points for it. -.-

Boss: We are going live tomorrow, are you ready?
Me: (Goosebumps and dry mouth) Sorry can you repeat that
Boss: Oh sorry not you, it's Sam whose app going live tomorrow
Me: (Inner me) Motherfucker. You dry dick piece of shit

One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.

Can I use a flamethrower to dry my laptop?

Enjoy this ultra⁻DRY piece of React-JSX-Redux-form component

I've caught the efficiency bug.

I recently started a minimum wage job to get my life back in order after a failed 2 year project (post mortem: next time bring more cash for a longer runway)

I've noticed this thing I do at every job, where I see inefficiency and I think "how can I use technology to automate myself out of this job?"

My first ever application was in C++ for college (a BASIC interpreter) and it's been so long I've since forgotten the language.

But after a while every language starts to look like every other language, and you start to wonder if maybe the reason you never seriously went anywhere as a programmer was because you never really were cut out for it.

Code monkey, sure. Programmer? Dunno, maybe I just suffer from imposter syndrome.

So a few years back I worked at a retail chain. Nothing as big as walmart, but they have well over 10k store locations. They had two IBM handscanners per store, old grungy ugly things, and one of these machines would inevitably be broken, lost or in need of upgrade/replacement about once a year, per location. District manager, who I hit it off with, and made a point of building report with, told me they were paying something like $1500 a piece.

After a programming dry spell, I picked up 'coding' with MIT app inventor. Built a 'mostly complete' inventory management app over the course of a month, and waited for the right time.

The day of a big store audit, (and the day before a multi-regional meeting), I made sure I was in-store at the same time as my district manager, so he could 'stumble upon' me working, scanning in and pricing items into the app.

Naturally he asked about it, and I had the numbers, the print outs, and the app itself to show him. He seemed impressed by what amounted to a code monkeys 'non-code' solution for a problem they had.

Long story short, he does what I expected, runs it by the other regionals and middle executives at the meeting, and six months later they had invested in a full blown in house app, cutting IBM out of the mix I presume.

From what I understand they now use the app throughout the entire store chain.

So if you work at IBM, sorry, that contract you lost for handscanners at 10k+ stores? Yeah that was my fault (and MIT app inventor).

They say software is 'eating the world' but it really goes to show, for a lot of 'almost coders' and 'code monkeys' half our problem is dealing with setup and platform boilerplate. I think in the future that a lot of jobs are either going to be created or destroyed thanks to better 'low code' solutions, and it seems to be a big potential future market.

In the mean while I've realized, while working on side projects, that maybe I can do this after all, and taken up Kotlin. I want to do a couple of apps for efficiency and store tracking at my current employer to see if I'm capable and not just an mit app-inventor codemonkey after all.

I'm hoping, by demonstrating what I can do, I can use that as a springboard into an internal programming position at my current gig (which seems to be a company thats moving towards a more tech oriented approach to efficiency and management). Also watching money walk out the door due to inefficiency kinda pisses me off, and the thought of fixing those issues sounds really interesting. At the end of the day I just like learning new technologies, and maybe this is all just an excuse to pick up something new after spending so long on less serious work.

I still have a ways to go, but the prospect of working on B2B, and being able to offer technological solutions to common and recurring business needs excites the hell out of me..as cringy and over-repeated as that may sound.

'Be long-term lazy.'

As in:
Work hard.
DRY.
If it takes more than 20 minutes, then automate it.
Prevent repeated work by testing just enough.

I'm such an idiot.

Spilled water on my MacBook today. Not that much water, but the cup landed right in the middle of my keyboard.

Worst part is I was gaming with my sister and didn't want to stop. So I wiped it off and shook it out a bit and kept playing. A bit later the screen started flickering and eventually went black.

Finally my brain turned on and I switched it off, shook out some more water, and set it up to dry. Just hoping it's not too late.

At least the drying setup recommended by the internet is pretty hilarious looking.

Now we play the waiting game. They say 72 hours before turning it on again. Seems a bit extreme. Will there still be moisture evaporating 3 days later? Not sure I can wait that long to see if it's toast.

Such an idiot.

A few hours ago I decided it was a good idea to to clean up my keyboard. I did so and took a walk leaving the keys to dry.

After I came back I hoovered the -board and decided to put back the keys. I started with the special keys since they were the easiest to find (and some required a metal thing).

Now, I was quickly made aware of something that I had never known nor noticed before. Bear with me here as I'm not a person that cares too much about hardware unless I need to. (Hardware here meaning stuff like mice, keyboards, headsets, and stuff like that). But I learned that

Not all keys are the same size. They look really similar to someone like me. But I manned up and put the keys back.

A little under 1.5 hours later and I now posses a keyboard that is in uncanny valley. It doesn't feel like it though, and it shouldn't be that big of a problem since I never look at my keyboard anyway.

Messaged one of my m8's about and this was his reply

"nope
one kind per row
usually says the row on the underside"

Now fantasize about the elasmobranch fish which is characterized by a cartilaginous skeleton of which I am the proprietor at what he said. I pulled a key out and, sure enough, "C28 R1".

Now I am not sure about the 28th column, but it did fit in the first row.

Fuck me

In january 2023 i was contacted by a recruiter offering me a job position.

I DID NOT ASK FOR A JOB.

I WAS NOT LOOKING FOR A JOB.

THEY contacted ME.

Ok. So i went along with it and see how it goes. They probably wont hire me nor would i give a shit. Chatted with this recruiter for a while. She forgets to answer my message for 5 fucking days. Twice. Once because she was doing God knows what and the second time because she was on paid vacation. Fine i don't give a shit about you at all anyways.

So this recruiter chatting has been stretched out for several days. I think over a WEEK. So she forwarded me to their lead developer.

I applied to work as a full stack java spring boot backend + angular frontend engineer.

So:
- java backend
- angular frontend
- full stack
- shitload of devops
- shitload of projects i built
- worked with clients
- have CS degree, graduated
- worked a job at their rival company

What could go fucking wrong with all of these stats right?

During technical + hr interview (3 of us on google meets) they asked me what salary I'd be comfortable with.

I said $1500/month straight out.

keep in mind:
- In my country $500 or $600 is a salary for engineers per month
- You get a raise of +$150 which is around $750 after working for 1+ year
- You can earn $1000+ after you work for +2 years
- Rent here is $200-300 a month at minimun. And because of inflation its just getting worse especially with food. So this salary is not for living but for survival.

Their lead engineer gave me a WHOLE ASS FUCKING PROJECT TO BUILD and i had to code it within 10 days. Great so at least 17+ days of my fucking life to waste on these fucktards who contacted ME.

The project was about building a web app coffee shop literally what mcdonalds has when you order via those tablets. I had to build this in java spring boot and angular. I had to integrate:
- docker, devops
- barmen, baristas, orders
- people can order at the table or to go
- each barista can take 5 orders at a time
- each coffee has different types of fields and brewing time
- each barman brews each coffee different period of time
- barista cant take more than 5 orders for to go until barman finishes the previous order
- barista can take more than 5 orders but if those orders were ordered from table, and they have to be put in queue
- had to build CRUD admin functionality coffee's
- had to export them all of the postman routes
- had to design a scalable database infrastructure for all of this alone
- shitload of stuff more

And guess what. After 10 painful days I BUILT THE WHOLE THING MYSELF AND I BUILT EVERYTHING THEY ASKED FOR. IT WAS WORKING.

Submitted it. They told me they'll contact me within 7 days to schedule the final Technical interview after they review what i built. Great so another 17+7 days of my fucking time wasted.

OH and they also told me to send them THE WHOLE GITHUB REPOSITORY AND TRANSFER OWNERSHIP TO THEIR COMPANY'S OWNERSHIP. once you do this you cant have your repository back. WTF? WHY CANT YOU JUST REVIEW THE CODE FROM MY PUBLIC REPOSITORY? That was so weird but what can i fucking do argue with these dickheads?

After a week of them not answering i contacted them via email. They forgot and apologized. Smh. Then they scheduled an interview within 3 days. Great more of my time wasted.

During interview i was on a google meets with their lead engineer, 1 backend java spring boot engineer and 1 angular frontend developer. They were milking me dry for 1 whole fucking hour.

They only pointed out the flaws in what i built, which are miniscule and have not once congratulated me on the rest of the good parts. I explained them i had to rush those parts so the code may not be perfect. I had other shit to do in my life and not work for your shitty project for $0/hour for 10 days you fucking dickriders.

So they quickly ran over to theory. They asked me where is jwt token stored. Who generates it. How the backend knows to authenticate user by it. I explained.

What are solid principles. I said i cant explain what is it but i understand how it works, why its needed and how to implement it (they can clearly see in the project i just build that i applied SOLID principles everywhere) - but i do admit i dont know the theory behind it 100% clearly.

Then they asked me about observables and promises in angular. I explained them how they work and how subscribe method is used (as they can clearly see that i used it in the code). Then they asked me to explain them under the hood of how observables work. The fuck? I dont know and dont care? But i can learn it as i work there?

Etc

Final result: after dragging this for 1 fucking month for miserable $1500/month they told me: we can either hire you now but for a much lower salary which you probably wont be happy with, or you can study more these things we discussed "and know why the car leaks oil" and reapply back to us in 2-3 months!

Just remember, the opposite of "Don't Repeat Yourself" is "Constantly Repeat Yourself". And you know what that spells.

Might as well join the fun! Hackintosh with desk that's perfect for dry erase markers!

I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.

I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.

He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.

I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.

I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.

Good riddance.

In the Ruhr area (Germany) we have some very old, very strange words with strange meanings. One of those words is ‚Prutscher‘.
A Prutscher refers to a person who does things but never gets a good result, due to lack of knowledge or simple carelessness. Most of the time, Prutschers are people who are interested in certain subjects and often work in the related jobs, but who lack the motivation to properly train themselves, learn what there is to learn and to always keep up with their technologies .
Here are a few examples I've stumbled upon so far in my career:

- Developers in their 60's who read a book about PHP 25 years ago and decided to become a software developer. Since then haven't read anything about it. Who then now build huge spaghetti monoliths for large companies, in which they prefix every function, every variable and constant with their initials and, of course, use Hungarian notation.

- People who read half a fucking tutorial about <insert any fancy js framework here> and start blogging/tweeting about it

- Senior web developers who need to be told what the fuck CORS is and who can't even recognize CORS related errors in their browser console.

- People who have done nothing else for 18 years than building websites for companies on Wordpress 1.x and writing few lines of PHP and Javascript from time to time. Those who are now applying as a frontend dev due to the difficult economic situation and are surprised that they are not accepted due to a lack of experience.

- Developers who are the only ones working on Windows in the team and ask their Linux colleagues for help when Windows starts bitchin.

- People who have been coding for 30 years, have worked with ~42 languages ​​and don't know the difference between compiled and interpreted languages ​​in the job interview.

- Chief developers at a large newsletter-publisher who think it's a good idea to build your own CMS (due to a lack of good existing ones, of course).

- Developers who have been writing PHP applications for multinational corporations for 25 years and cannot explain how PHP is executed. They don't even know what the fucking OPcache is, let alone fpm. FML

- People who call themselves professional developers but never ever heard of DRY, KISS, boy-scout rule, 12-Factor App, SOLID, Clean Code, Design Patterns, ...

- Senior developers wondering why the bash script won't run on their fucking Windows machine.

- Developers who consider Typescript to be a hindrance and see no value in it.

- Developers using ftp for deployments in 2022

- Senior Javascript Developer applying for a job and for whom Integer is a primitive data type in JS.

- Developers who prefer to code without frameworks and libraries because they are only an unnecessary burden/overhead and you can quickly code everything up yourself.

- Developers who think configuring their server(s) manually is a good idea.

You fucking Prutscher. What you have already cost me in terms of work and nerves. I can't even put it into words how deeply I despise you. I have more respect for the chewing gum that has been stuck in my damn trash can for the past 3 years than I do for you guys. You are the disgrace of our profession. I will haunt you in your dreams and prefix every fucking synapse of your brain with MY initials.

As a well-known german band once sang in a very fitting song: I wouldn't even piss on you if you were on fire.

If you recognized yourself in one of the examples here: FUCK YOU!

People who actually implement DRY: "Don't repeat yourself!"

People who "implement" DRY but are morons: "Don't repeat yourself, never say the same thing twice, and try not to be redundant."

!dev

I think someone needs to turn the weather off and on again here. The dry thunderstorm that woke me up is now a hail storm. And its humid. And warm.

I'm on the West Coast, this is new England/east coast weather. Wtf.

This is why DRY is important...

I fucking hate chained methods. Ok, not all of them. Query things like array.where.first... that stuff is ok.

Specially if it's part of the std lib of a lang, which would be probably written by a very competent coder and under scrutiny.
But if you're not that person, chances are you'll produce VASTLY inferior code.

I'm talking about things like:
expect(n).to.be(x).and.not(y)

And the reason I don't like it is because it's all fine and dandy at first.

But once you get to the corner cases, jesus christ, prepare to read some docpages.

You end up reading their entire fucking docs (which are suboptimal sometimes) trying to figure if this fucking dsl can do what you need.

Then you give up and ask in a github issue. And the dev first condescends you and then tells you that the beautiful eden of code he created doesn't let you do what you want.

The corner cases usually involve nesting or some very specific condition, albeit reasonable.

This kind of design is usually present in testing or validation js libraries. And I hate all of those for it.

If you want a modern js testing lib that doesn't suck ass, check avajs. It's as simple as testing should be.

No magic globals, no chaining, zero config. Fuck globals forced by libs.

But my favorite thing about it that is I can put a breakpoint wherever the fuck I want and the debugger stops right fucking there.

Code is basically lines of statements, that's it, and by overusing chaining, by encouraging the grouping of dozens of statements into one, you are preventing me from controlling these statements on MY code.

As an end dev, I only expect complexity increases to come from the problems themselves rather than from needlessly "beautified" apis.

When people create their own shitty dsl, an image comes to my mind of an incoherent rambling man that likes poetry a lot and creates his own martial art, which looks pretty but will get your ass kicked against the most basic styles of fighting.

I fucking hate esoteric code.

Even if I had to execute a list of functions, I'd rather send them in an array instead of being able to chain them because:
a) tree shaking would spare from all the functions i didn't import
b) that's what fucking arrays are for, to contain several things.

This bad style of coding is a result of how low the barrier to code in higher level langs are.

As a language or library gets easier to use you might think that's a positive thing. But at the same time it breeds laziness.

Js has such a low learning curve that it attacts the wrong kind of devs, the lazy, the uninspired, the medium.com reader, the "i just care about my paycheck" ones.

Someone might think that by bashing bad js devs I'm trying to elevate myself.

That'd be extremely stupid. That's like beating a retarded blind man in a game and then saying "look, I'm way better than this retarded blind man".

I'm not on a risky point of view, just take a stroll down npmjs.com. That place is a landfill. Not really npm's fault, in fact their search algorithm is good.

It's just the community.

Every lang has a ratio of competence. Of competent to incompetent devs.

You have the lang devs and most intelligent lib devs at the top. At the bottom you have the bottom.

Well js has a horrible ratio. I wouldn't be shocked to find out that most js devs still consider using import or await the future.

You could say that js improved a lot, that it was way worse beforr. But I hate chaining now, and i hated back then!

On top of this, you have these blog web companies, sucking the "js tutorial" business tit dry, pumping out the most obscenely unprofessional and bar lowering tutorials you can imagine, further capping the average intelligence of most js devs.

And abusing SEO while they're at it, littering the entire web with copy paste content.

Argh,

Today - you son of a bitch.

It all started with a 2 hour flight out of town for business, and I mean started as in I needed to be at the airport at 4:30am!

Despite 2 coffee's to get me out of bed I proceeded to indulge myself in the magic juice, 3 cups later and it felt like my heart belonged in a Grand Prix.

Now here is the sticky part, we where briefed that we would only be doing 2 site meetings and that was it.

Low and be hold it got worse, turns out that we would be pitching our product to 3 highly regarded CEO's, now bare in mind that my position on this trip is as the lead developer, and don't get me wrong I am well up to date on every aspect of the business, hence why they sent me.

So more coffee down the gullet, and eventually the conversation leads back to a project that I had developed to allow authorization of debit orders online, now usually I'm quite a well presented person in these types of situations, but you don't realize how quick this can change.

A quick jump to the geography of the location I was doing business. Johannesburg, South Africa - its as dry as hell, smoggy and at a very higher altitude "as in above sea level".

Now unfortunately none of the above factors where helping me much at all.

Now back to where I am being asked about my project, and never in my life have I tripped over my own words, I went completely blank, I'm surprised I didn't pass out to be honest.

Now despite the death stare and my colleague kicking me under the table, I am feeling pretty terrible, fortunately I had a kick ass team that was able to cover my ass!

Luckily I was able to recover ( 2 muffins and about 3 bottles of water later). We where able to salvage the meeting and it turned out pretty well, I regained my energy and we made it happen!

Must say the flight back was amazing! Almost empty and we all had a row of seats to ourselves, which resulted in some major comfort stretching!

Thanks for tolerating my essay, I'd love to hear if anyone has had anything of the sorts happen to them.

!dev

I‘m not shitting you, a can of Guinness just fucking exploded in my bed room..

Last weekend i had a few drinks too much and I took a Guinness to my room to „watch a movie and fall asleep“. I fell asleep before even starting a movie. So I didn’t even open the can.

Today I was looking for a cable on my night table and accidentally hit the can with my elbow.
It just fell in the side and FUCKING EXPLODED. The can is split in half.
My whole bed, my good shoes, my mattress, the floor, my bills and EVERYTHING IN A RANGE OF 5 FUCKING METERS IS SOAKED.

How the fuck can that even happen?

Tried to clean everything with water and opened the windows to get my my shit dry again, but now I have to sleep on the couch in the living room until that stuff is try again..😤😤😤

Need a Guinness to calm down.

I know cans can „leak“ if it’s too hot but we had 19C max in the last week..

Happy weekend to you..

Hey! You there!
Are you sick of windows 10 sending you intrusive reminders about updates? Are you tired of random unscheduled restarts? Tired of feeling like you have no control over your own computer?

Take back control!
DO THE FUCKING UPDATE, YOU FUCKING INCOMPETENT, USELESS, LAZY, PIECE OF DRY WANK!

Seriously guys: pick a time convenient to you, and take 5 or 10 minutes (when you're likely spending hours at your computer), and do them. Not only will you get rid of the annoying notifications, but you'll also keep your pc safe and secure by keeping up with security patches. C'mon people, it's really not that difficult.

And can we please, for the love of all things holy, stop the circlejerking? You're developers, you are the computer proficient. The only things a PC will do are the things you tell it to do. Dig deep, dig into the registry, dig into the services manager, dig into the fucking settings cos a good number of the most common complaints can be fixed in the basic options menu. Tell your computer to stop doing the things you don't like and it will stop.

It's really not hard!

Having some thoughts as I sit here, trapped in the house by equal parts coronavirus and a layer of smoke drowning out the sun. The smoke is a bit of an annual thing; every year, some irresponsible jerk will go out and put their convenience and enjoyment over everyone else's quality of life.

It's a bit different this year since coronavirus has given people cabin fever. Those same people who lose their minds after weeks of isolation and suffering the indignity of wearing a mask headed out into the wilderness for recreation in record numbers.

The result is record wildfires.

Where I'm at, it's mostly coming from the eastern part of our state. The area is typified by being on the mountain range's dry side, more rural, less densely populated. Towns have burned, people lost their homes, millions of acres of land will likely burn before it's over. It happens every year; people pack up, head out into the wilderness, and cause devastation due to a simple lack of common sense or regard for the consequences of their actions.

On the west side, we see the fallout in the form of days without sunlight and abysmal air quality. We also see it in cost; we will unquestionably and without hesitation contribute to eastern recovery efforts. The western half of the state will cover almost all of the damage in both taxes and recovery aid. Our local ethos demands it.

The mountains form a kind of natural barrier, both cultural and environmental. The fact that few people cross the mountains by choice is symbolic of that divide. Those who enjoy greenery and lakes and thriving vibrant nature prefer the west, as we have them in abundance. People who have a strong appreciation for distance between themselves and other humans prefer the east, as it affords them cheaper land and few urban environments.

Here's to hoping people learn from this in 2021.

Literally whole dev world: DRY - Don't Repeat Yourself
My Company: DRY - Do Repeat Yourself

!Dev

A bit random but I'm just really anrgy

Why the fuck. Why do mosquitoes have to exist. Fucking go outside in certain places for 5 minutes and these spawns of Satan suck me dry.

I swear these things have all come through a portal straight from hell.

And then its gotta itch like fucking mad for the next days, driving me straight up insane.

I'll be glad when I get back to my place. Climate might be cold and raining a large part of the year but fuck that's so much better than fucking getting poked by these fuckers this much again.

Struggling to earn money to pay for medical bills for my dad at a private hospital because he's having some problems with bile in his stomach. He pukes after eating almost anything so he has to eat some dry bread and drink tea. The only solution for this is surgery. He made appointment for august which is the earliest date... I have to find a way to earn money asap so he can go privately Now without waiting...

No i cant use gofundme because its not available for my bullshit 3rd world country just like most services

5 of us working for a larger team were tasked with doing some R&D, we blew everyone away and were given funding to start a new team and hire people to make the project come to life.

One of the high level sales / product managers we were reporting to, secretly had another team work on a similar idea because he needed it quicker (i.e. no time for research, just build it).

After forming new team, we were asked to work on his project instead because it was further along. 4 months later, big knob comes to a meeting and basically says "You know what, this doesn't look like we have enough features, we need more, but I don't know what".

Project blew up 2 months later, head of the unit kicked up a shit storm saying how badly everything was planned and canned everything. Now one of our clients is building nearly the same thing we were originally working on, the team no longer exists and i'm back on the R&D team.

Don't get me wrong, I LOVE the R&D team, actually didn't want to leave in the first place but was told I had to. But the sheer anger and frustration to see that walking cluster fuck strutting around like his shit doesn't stink, derailing entire teams, meanwhile we can't hire new staff due to lack of funding.

Heres an idea, fire the fucktards bleeding us dry ... then we'll have lots of funding.

Don't Repeat Yourself. Don't Repeat Yourself.

3 words you need to keep repeating over and over to colleagues that, well, keep repeating themselves in code.

When you use words like SOLID, DRY and KISS in code review

Raging here, overheating really. One spends thousands on technology that is promoted with the catch phrase "it just works", yet here I am, after updating my fancy new emoji maker (iphone x) to 11.2 and then attempt to carry on working by compiling my code to test some new features. And...

oh, whats this xCode? You have a problem? You can't locate something? You can't locate iOS 11.2 (15C114)... sorry and you think that this "May not" be supported in current version of Xcode?

Let me get this straight you advanced piece of technological wizardy, you know you are missing something, you in fact know what it is, you can actually TELL me what is missing and yet, still, in 2017, you can't go FETCH it?????

Really? All you can do is sit, with that stupid look on your face, and watch the paint dry? Your stuck? That's it?

I hate you for the false pretense of advanced capability. and for your lack of a consistent dark theme so my eyes stop bleeding when reading your "I don't know what to do" messages...

By the way, maybe you can stop randomly crashing, or pinwheeling, I get that your bored as a machine designed to crunch numbers/data/code all day long and that for fun you feel you have to add some color to your subsitance. But stop it. Do what I'm told you can do, "JUST WORK" for once without me having to drag you forward kicking and screaming.

K. that feels better. Now for some whiskey.

After I picked up cooking, I dialed in a classic Russian pancakes recipe of my grandma (the babushka) and made it sugar-free. I cook those pancakes for my wife every Saturday, and she says they taste heavenly.

So, here’s the recipe of kiki’s pancakes:
- 8 eggs, 150g of 82% butter, 300g of flour, baking powder, 800ml of 3.2% fat milk. If you have a blender, it’ll make things easier
- let them sit and make all of them the same temperature
- take 8 eggs, add milk, stir
- liquify the butter in the microwave, add, stir
- sift the flour in while stirring continuously
- let it sit for 30 minutes
- take a pan, add little butter or sunflower seed oil, make it scary hot
- after you pour, flip the pancake when its top gets dry

to flip them easily, spread pastry wide when pouring, overlapping frying pan edges. Then, use those edges (now bone dry) to flip the pancake. After you’re done, those edges (now almost black) will break away, leaving a perfect pancake. This works especially well if you don’t have a good non-stick frying pan.

enjoy!

Anyone here knows the fastest way dry wet pants. I just dropped some water all over my pant and it looks like I've peed myself.

DAMN IT

"How much of a dev are you, if you use other peoples work and just glue it together?" I once asked a friend who really loves npm and everything.

I know about code reuse and maintainability and all that but geez we had a long discussion..😅

I haven't felt joy programming for a while now.

My work is just tasks that can be done by a monkey if they understand how the framework works and at home I can't come up with any ideas that are exciting, challenging or useful.

I feel like all my creativeness is leaking dry having to deal with deadlines about implementing this text change with critical^3 priority and other boring shit

When I realized my job isn't to code, it is to hack for hacks.

As smart developers our job is to be accountable to non-technical product management types who care nothing for elegant system design or DRY code. They expect features get done fast and "technically complete." They use terms like "minimum viable product (MVP)" to imply we'll go back and improve things like refactoring and tech debt later.

They will not. Most likely they won't even be around. Producers and scrumlords have the highest turnover rate of any role on a team. By design they get bored or frustrated easily and are constantly looking for greener pastures. Many people in self-proclaimed "non-technical" roles like this never had the patience and attention span to learn a real vocation, and they've discovered a career path that doesn't require one.

These are our masters. As developers, we will answer to them forever and always.

Hundreds of PHP files with same name and _# at the end to differentiate them - each containing hundreds of
$(document).ready(function() {
$(some_slector).on(some_event, function() {
//one line of code
}
}

Even if you are denied after all your job interviews, don't be sad.
1. you looked promising enough to call you to the interview in the first place
2. you need to work on some gaps in your knowledge/xp. Oh, you didn't know that? Well, now you do! Not even that - you also know what the gaps are!
3. you hear of new technologies, net tricks that are there. Dig in!
4. you become more aware of what positions are there and what requirements could be applied to them in different companies. Makes you build a company profile and make better choices for applications later on.

Now imagine the pressure on your shoulders if they would have hired you while you have so many gaps in your knowledge... It's overtimes every day! It's possibly missed deadlines. It's mishandled tasks. It's bugs all over the place and other devs judging you!

Brush your tears dry, grab candy or a chocolate bar and go improve yourself!

DRY
Enough said

Ughhhhhh. This fucking code is a disaster! The guy says he built it DRY, but it's WET as fuck! So much fucking repeated code!

I'm annoyed most because I know that it'd be a fucking waste of time to try and rebuild what these guys have built over the past 5 years, but goddamn it, it shouldn't be an excuse to keep on making code like this!

I know that I'm not super experienced in C# but pick up a goddamn book on good coding practices. This thing is a disjointed mess and it never had to get this way.

So many fucking interfaces!!!! AAAAAAAAAAAAAAA

http requests

literally the bread and butter of any software engineer building applications, you would ASSUME they know what they are doing...

and you're gonna write a seperate http get and post function for every type you have?

apparently stuff like this that is written by "senior" developers? you don't even have a basic understanding of software...

i'm won't do it that way, becuase i'm an adult, not a child

what i'm going to do is write a HTTP request util function that can be used for any type and HTTP verb. DRY, single responsibility, etc.

imagine making the http request itself a responsibility coupled to the type 😂😂😂😂

get a clue and come back later

i can't tell anymore if my thoughts are so outlandish compared to everyone else that no one understands them, or if i've been doing this so long that i just immediately understand what needs to be done and don't know how to explain it to anyone else anymore (or take the mental effort to)

peace out

oh P.S.: imagine thinking the SOLID principles are only applicable to OOP

stay safe out there folks, its getting more painful every day

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

For the last time, SLOC is not a measure of anything.
Have too many, the code probably isn't DRY.
Have too few, you probably don't follow a style guide and have 120 char lines because you invented "oneliners" which you were so proud of that you had to put it in there.
Have just the right amount, and the code likely suffers from both of these at the same time.

My partner says I'm too much of dry logic and lacking in emotions. The way I want to find logic in everything and ignore illogical spontaneous emotions... Isn't helping me in here.
Just wanted to vent out and ask whether this is the curse of the nature of work... with tech I am in (I fantasise it to be that) or is it just My individual problem?

Warning: BBQ religion discussion

I love living in Seattle, but one thing that really, truly bugs me is the absence of legit bbq. I love all bbq, Carolina, Memphis, Texas, Virginia, Tennessee, Georgie, doesn't matter. Even Kansas City and California if i have to.

There's places people swear by here, but they're mostly just meataterias with meat that is just OK. At least half of BBQ are the sides. Here, very little vinegar in sight, everything dry AF and underseasoned/oversalted. Dry potato salad that is mostly kraft mayo, coleslaw that's also mostly kraft mayo and menu items like "queso mac and cheese." You said cheese twice, I like cheese, but I don't trust you enough to order it. And greens? Don't even try.

Biggest thing though: if you don't serve fried okra, don't you dare call your shit Texas bbq 😠

A few days ago I read an article about an IT company in germany winning in court. They sueed the government for charging them taxes for offering breakfast to their employees. They won because the jury said coffee and dry buns is not a breakfast.

So, my question is is there some guy from called company here on devrant? 🙂

This might not resonate with many ranters here... but FUCK Taylor Otwell & Graham Campbell.

Like, not on a personal level. Maybe they're great to drink a beer with. But as framework devs... fuck everything about them.

Laravel seems so nice, it takes away many annoyances of developing in PHP. Collections are the array object you've always needed. The route bindings, middlewares, request validation objects, it's all sweet.

But eventually your company serves a few million customers, you run into specific performance problems or missing features on a deeper level. You open the issue tracker... and see a few hundred issues about the problems you are encountering, they already exist.

Some just have a short paragraph with a request for a feature, some complete PRs with tests in the style of the framework. All of them closed.

Reasons?

"We don't think anyone will ever need this"
"This seems complicated, you can just do <super non-DRY hacky code>"

FUCK YOU WITH YOUR TODO APP SNIPPETS AND USER-POST-ARTICLE EXAMPLES. I'M NOT BUILDING THE NEXT WORDPRESS. I'M DEALING WITH THE REALITY OF GRAPH DATABASE CLUSTERS, COMPLEX AUDITING LOGS AND A GAZILLION QUERIES PER SECOND.

Sigh... the problem with all these "simple" and "elegant" languages & frameworks is that they don't fucking scale.

Not because the language, server or framework intrinsically can't do it, but because the maintainers are stuck thinking in terms of their retarded non-realistic example apps.

I think I'll go back to my cave and write some Haskell or Rust to calm down.

I have ADHD. If you don't know what that means, for me it makes me a better software engineer. I can't do repetitive, so my code is by definition DRY. If someone needs help, I'll notice and help because my brain can't filter out the emotion of someone struggling. I fixate on problems I don't know how to solve, I literally struggle to stop myself. The list goes on. But, at its heart, who gives a shit?

I'm a software engineer, and I'm good at what I do. Does anything else matter?

I was assigned to maintain the website as full stack dev but the code from backend is horrible previous devs didn't use SOLID principle, DRY, KISS, or Design patterns. I had to adjust from OOP mindset to Procedural its hard to debug in this state.

Soo my dad has a food printer he uses to print edible images on cakes our customers order. The food printer needs to run at least once a week (regularly) to kinda guarantee not to get fucked up with its ink, as that can damage the printer when it's dry. My dad though doesn't have regular orders...
The printer has a standard function to test all colors.
My dad asked me how this task could be managed regularly, as I'm the IT guy 🙄. His idea was to log all the dates on paper.

Now I'm trying to automate this task via Windows so we don't have to care about papers to manually log when the next test must run. On Windows the printer settings can be accessed to run this color check.

... I've got a feeling this will be another one of those tasks that I will overengineer over the top😅. I've already done my research with automated batch jobs (never done batch before) but the normally proposed code for a "Düsentestmuster", so the color check, prints a different overview I was not expecting, which doesn't fit the purpose.
Now I'm here and, as I currently see no way of simplifying it, I have to kinda simulate a person that opens these settings and runs this check. With Python, pyautogui and Tesseract OCR, to prevent the program from clicking anything wrong. Although I'm sure there should be an easier way for this, I haven't found it, so I guess I have to proceed on this path and take the experience I gain as a bonus...

KISS, DRY, Path of Least Resistance, Three Strikes and You Refactor, early returns, no array.map when nothing is returned, only use switch when # cases >= 3.

And using var in javascript instead of let/const to piss off my colleagues (and because I understand function scope well)

Today, for the first time since I've started coding, I had a legitimate use case for the multi-cursor feature of my IDE in reasonably DRY code.

Edit: nvm, I added a version of the function to support arrays on the first argument.

OK Mr CEO/President whatever self aggrandizing title you want to call yourself today, where the fuck is your spine! You want to have support help boost your sales but don't tell sales that you are letting support handle some sales and sales is mad. Now you are quivering under the thumb of the Lead of Sales. What the hell. You are the leader of this company.

Why did you not stand up for your decision to begin with? I'm not going to get into whether or not it was good, but if you are going to make a decision to experiment with new things fucking stand by it and let everyone in the company know.

You've exacerbated the division between departments and ton this company further apart. If you don't start standing up for things, you are going to destroy all that you've helped build! Furthermore, I will not simply be your loyal vassal and watch all the people doing support for my products get fucked over. I will leave you high and dry if needed. I really hope you don't make it needed. You gave me a great shot to be honest, I'd hate to have to turn my back on you in anger. But don't think for a second I won't do it.

Your entire programming department has also been put in the cross fire of a fight you just made so much worse. You are the only one who can clean this up. Are you going to stand up for us? Are you gonna stand up for your self? Or will you just break and show us where the real power lies? We will find out soon.

Cocktail Development #1 - Codename: Devjito

Hello fellow developers! I was enjoing some sweet selfmade cocktails lately. One of the commentators shouted out for me to "don't stop the cocktail rants!".

But, because I didn't wanted to just "Post random cocktails", I tried to develope my own cocktails. Afterwards I will share my experiences while creating these with you, and of course, the recipe!

So first we got my Experiment: Devjito - A Cocktail for all of you fellow programmers!

What we need:
- 4cl Tequila
- 4cl Wodka
- 4cl Dry Gin
- 4cl White Rum

- 2cl "Grenadine" Syrup
- 2 teaspoons of white sugar
- 8cl of Orangejuice
- Sodawater
- Icecubes
- Mintleaves(?dunno if right? Me German don't hate)
- Orange for decorational purposes

Recipe:
First get a tall glass, pour the sugar in it, wash the mint and stick it in there.

Get your favourite cocktail shaker, pour all the liquor in it (the Tequile, Wodka, Gin and Rum) + the orangejuice and icecubes. Shake 20 seconds and dance while shaking, also don't forget to try out eating your devRant Stressball (Leave note in comments who gets this reference).

After shaking pure the "semi cocktail" into the glass with the mint and sugar. Get your masher (I guess this is the right word?) and mash your mintleaves with the sugar and the cocktail. Afterwards, fill the glass mostly up with sodawater.

Now the trickey part: to make it look cool, get your Barspoon and the Grenadine Syrup. Stick the spoon in the glass and let syrup slowly flow in the cocktail, this will make the "red shine" shown in the image attached to this rant.

Finally, stick an orange slice on the glass and enjoy!

My Impression: It's a bit stronger than a normal Tequila Sunrise, but better for the people which don't like sour or "liquor only cocktails".

Thanks to @cafecortado and @CoffeeNcode but also the other commentators!

(An image of the ingredients will be attached as comment)

EDIT: @oudalally mentioned it correctly JES it tastes very sweet!

My tech debt meltdown is happening right now. We are releasing our huge micro service based product next week with no automated testing of any sort. Our front end clients are relatively DRY. No tests and dry = can't change anything = hacks on top of hacks.

Why? Team lead won't listen to me and has beaten me down so I don't care anymore. If it's broken fuck it.

I need this, a dry erase desk for when I don't want to find paper...

all the fun people at my workplace have either been fired or they have left. my workplace is bone dry now

I mean, ONE of these days, the Prod pipeline has GOT to work... doesn't it?? Just basic odds say EVENTUALLY it will, doesn't it??

Of course, I'm sure I could have had it working long ago if not for the fact that we have to use common scripts developed by another team that we can't alter, and just guess where the problem is.

You know, standardization and DRY are good principles generally, but if you just apply them without thinking and without at least SOME flexibility, you only make matters worse.

Please open this rant. Make sure to get a good look at my username. Then go to the comments and call me an idiot because FUCK I JUST POURED A GLASS OF WATER ON MY LAPTOP.

Left it upside down to dry for a bit. Please forgive my for the sudden shower 😭😭😭

Three male programmers were in the bathroom standing at the urinals.

 The first programmer finishes, walks over to the sink to wash his  hands. He then proceeds to dry his hands very carefully. He uses paper  towel after paper towel and ensures that every single spot of water on  his hands is dried.

 Turning to the other two, he says, "At Windows, we are trained to be extremely thorough."

 The second programmer finishes his task at the urinal and he proceeds to wash his  hands. He uses a single paper towel and makes sure that he dries his  hands using every available portion of the paper towel.

 He  turns and says, "At Macintosh not only are we trained to be extremely  thorough but we are also trained to be extremely efficient."

 The third programmer finished and walks straight for the door, shouting over his shoulder.

 "At RedHat, we don`t PISS on our hands."

!rant

What's your dream GSDR/GWDR setup?

(Get shit/work done room)

Spacious desk, three 21" monitors. MacBook Pro laptop and windows/ubuntu desktop.

A nice big dry erase or smart board on the wall.

Hardwood/hard carpet floors.

One empty wall so that I may bounce a tennis ball against it while I contemplate.

Electric piano.

A tough padded bench for naps and laying down to change perspective.

Very good lighting.

Close proximity to a gym.

I guess I'll have to move out of my parents first though 😅

#love for programming dry run comments

Of the rants that have tags, it seems like half of them contain some sort of non-tag that is dry wit, self-aware joke, or humorous comment.

Okay, one after another. They like to piss me off, apparently.

Coleague knows something isn't possible with current state of some api and pushes phone to me so I can maybe figure out what to reply to client. I dry-typed in "Its not possible" gave him phone and said "boom done, you know it aint possible"

Okay, TL;DR she got pissed that I am pissed that this BS is thrown at me and I dont want to participate in promissing something I know is undeliverable.

So she told me to go to PM/PO *kind of guy but not rly* with that problem. He aint technical by any mean. We are small company and for some reason this guy has more bearoucratic approach than I thought is possible to fit in one human.

Anyway. Well, apparently we will have meeting what are our options.
It all beginned that one guy promissed other guy undeliverable feature....

And becouse someone couldn't use his fucking brain it's pushed onto me, or I need to figure out how to do it. You cant without introducing safety flaw, period, it's that fuckin' simple.

But nooo, we will have god-knows-how-long meeting, that will bring exacly 0 value, as fking allways, and all I want now is just fucking focus on my fucking code becouse, ya know, I have timeline to follow, I dont have time to all that BS.

And to give you context, while keeping the stuff I cant share secret, imagine you have an API, that is just 'facade' of backend API, and layer of security. And they want to add authoritative endpoint to the facade API. Kind of endpoint "yes, you got paid".

Bravo, big brain, it will not work without like huge-as-fuck vunrability...

IDIOTS

How to not get pissed? Any protips?

Do you think it’s appropriate to use the phrase "dried" in commit messages to refer to removing duplicate code? (DRY = don’t repeat yourself)

I just used it and I’m not sure if it’s ok because some devs might not understand it and the the original letters from DRY went away and became "dried" so it might be even more cryptic.

On the other hand it’s so much more concise having "dried type X" compared to "refactored the code so that it doesn’t contain duplicates of type X"

Damn this week topic is hard.

I am gonna go with managing a team. I have to use the DRY SOLID YAGNI KISS on daily basis at non-dev tasks too.

Waiting for the floors I just mopped to dry, and I'm still thinking about migrating and if, for example, the swiss give me a good job offer, I would most likely stick around. I don't hate to stick around Europe, but it defo doesn't have any of the elements I like. (megacity, snows, English speaking, multicultural, non-torturous migration laws)

Like, I'm at that point where I'm not making enough money and want to leave (also, gaining the freedom to leave from degree soon enough) but I absolutely hate my home place (personal reasons) but they pay a crapton better, plus I can get social security benefits.

... And I want to do a phd. 😐
Someone beat some sense into me please.

For state management, we use:
React state
Redux state
Local storage
Session storage

That’s it 😊

Some like it WET
Others like it DRY
But I don't care - I just like to KISS it

Most web developers don't seem to care at all about ecological footprint and UX/UI impact on people and society, like they never cared about accessibility either, desperately dreaming to work for the Californian oligopoly companies that shaped our current digital infrastructure.

Meanwhile, rivers run dry, forest are burning, people starving and soldiers killing people.

But politics is taboo, even on devrant. Let's post a funny thank-God(?!)-it's-Friday GIF animation instead!?

What kind of people do we want to be?

Me, doing a large update on a table without backup and dry run.

How many of you use the right data structures for the right situations?

As seasoned programmer and mentor Simon Allardice said: "I've met all sorts of programmers, but where the self-taught programmers fell short was knowing when to use the right data structure for the right situation. There are Arrays, ArrayLists, Sets, HashSets, singly linked Lists, doubly linked Lists, Stacks, Queues, Red-Black trees, Binary trees,.. and what the novice programmer does wrong is only use ArrayList for everything".

Most uni students don't have this problem though, for Data Structures is freshman year material. It's dry, complicated and a difficult to pass course, but it's crucial as a toolset for the programmer.

What's important is knowing what data structures are good in what situations and knowing their strengths and weaknesses. If you use an ArrayList to traverse and work with millions of records, it will be ten-fold as inefficient as using a Set. And so on, and so on.

Apparently, DRY is something my team has never heard of. I wonder how many places they need to repeat the same fuckass long declaration in before they would go "hold on..." - so far it's definitely not 4 files

The railway service in Sydney is called CityRail.

Fuck CityRail!

It's so unreliable that service disruption is to be expected when the weather is too hot, too cold, too wet, or too dry. If it rains, some services will be cancelled while the rest face delays.

Fuck CityRail!

The rail network is so dilapidated it costs the government millions of dollars each year for maintenance, despite charging a fare that is one of the most expensive.

Fuck CityRail!

Now I'm typing this because I've be stuck on this train for the last hour and there little hope for me to reach home before fucking MIDNIGHT!

FUCK CITYRAIL!

They initially offered replacement service but later retracted.

Fuck CityRail!

Few weeks back, I have subscribed /r/battlestations and drooling everyday. Now with this latest devRant news, it's time to save money or sell my ass on street to

1) buy a wide monitor or monitors
2) buy backlit keyboard and mouse
3) buy a good desk
4) buy a good chair
5) buy/rent a room with enough space

Forget about buying and setting up a good unit, I can just use my potato laptop for one photo taking. *dry-laugh*

(∩︵∩)

New in my job
Start to work on a abandoned project for one of our client not very happy cause the lack of update
Go for a critical issue which exists since 2 months where everyone was telling me that they passed a huge time working on it with no answer
*check error*
*check code*
The code is so fucking much not DRY so I was able to see the same 4-5 incriminated lines elsewhere
*see that the request is lacking of one parameters just has the error suggests*
*copy paste the missing line*
*it works*

I’m now a hero for them but they become fucking peasants for me

(In addition, when code reviewing, some one had the nerve to tell me that “haha it was nothing much finally, it was easy”
To him : fuck you, eat my 💩)

What is the leading cause of dry skin? Towels

Watching a build servers log output is as boring as watching paint dry.

i was about to talk about golang - but it can wait.

snapchat's discover section is TERRIBLE. the amount of BULLSHIT, INCORRECT INFORMATION, AND PURE IDIOCY IS MAKING IT TERRIBLE.

now, usually, i rant about mashable when i say it's terrible. AT LEAST WHEN MASHABLE WROTE ABOUT THIS THEY WERE CORRECT. but no, alas, my faith in humanity is put to an all time end. a new evil has arose, by the name of "wired."

of course, and incredibly late to the party, a "tech" outlet wrote about bitcoin. the headline was "is bitcoin killing the planet?" IT HAS BEEN POSSIBLY THE STUPIDEST ARTICLE IVE READ OF ALL TIME. THEY CLEARLY HAVE NO IDEA ABOUT ANY SHIT THEYRE TALKING ABOUT.

let's take a look at the TWO facts they got wrong, and displayed to over a MILLION people.

now, instead of just GOOGLING TWO SIMPLE FACTS, THEY DECIDED TO JUST WRITE RANDOM SHIT.

ENOUGH WAITING - HERE THE THE TWO FACTS THEY GOT WRONG

picture 1: bitcoin up $900 in the last year? THE LAST MOTHER FUCKING, COCK SUCKING

.
.
.

YEAR?!?

WHY DO SUCH DUMBASSES HAVE ACCESS TO SOMETHING MILLIONS VIEW?

IT MAKES NO FUCKING SENSE

picture two: the actual fuck????

did i just read that?

b- bi- bitcoin will "run dry" BY 2032.

i think i finally figured it out.

these facts, they're literally just random number.

<thoughtBubble>
i can see it now:

wired employee 1: hey, guess what number im thinking of?

wired employee 2: 14?

wired employee 1: *screaming* BITCOIN WILL RUN DRY IN 14 YEARS

</thoughtBubble>

how do these people get hired. do they hire only hire 12 year old interns? im genuinely asking. does anyone know?

okay, end of rant. plz continue complaining about dumbasses who have power thru the media in tech

I had contact with the BenQ support recently.
On my small GV1 beamer, the auto switch off timer cannot be canceled by pressing a button. So I wrote them, that this is maybe a bug.

That was the answer:

"Thank you very much for your inquiry.

Insects entering the monitor through vents are a common problem that is not covered by the manufacturer's warranty as it is not a manufacturing problem.

This problem is known to all monitor manufacturers.
The cause of the problem is usually that the monitor is used in a dark environment without a secondary light source being activated.

If the insect is still alive, you can lure it out with a light source (the monitor should be turned off and cooled down).
If the insect is dead in the monitor panel, wait until it is completely dry. Then you can carefully press on the screen, next to the insects (avoid crushing them) and it should fall into the panel and leave the visible area.

Nevertheless, please send us a picture where we see the problem you are telling us, I inform you that the picture must be less than 2 MB in size."

MSG for dfox and trogus
Hey guys, have you seen my bug reports?
For all the others.. Do you have a bug where your app crashes when uploading a IMG from Android or is it just me?

This stupid computer is in clamshell mode connected to my screen and mech %99.999999 of the time. I take it with me on a trip and the down arrow key breaks off (little plastic shit-thing snapped off)..WTF? 2013 Macbook that has about 5 hours of total keyboard-use, at best.

Walk into the Apple shop in Varna, 3 Euros and I'm back in action.

ahhhh fuck..it was probably my fault clacking too hard.

Good sushi here and my dry February has happily turned into large pints of Kamenitza...

Cheers from Bulgaria, you fucks..

I can't stand Swift's initializers. No other languages have the problem with constructors/initializers that Swift does. It's a complete failure of a feature and to hell with safety if it comes with this cost.

Just to illustrate how ridiculous it gets, I want to have a class where my initialization logic can be split among reusable parts. That is, the logic that initializes the class with no parameters has logic that I want to reuse in my other initializers. Simple DRY stuff. Well, the only way I can do that in Swift is if I use a convenience initializer that calls another one. But convenience initializers have completely different rules from designated initializers (again, something only Swift does).

For example, you can't access "self" until you call a designated initializer. You can't chain designated initializers, and if you want to chain anything in the same class you have to handcuff yourself by using a "convenience" initializer (there's nothing convenient about them, I might add).

So now I want to subclass my class and initialize myself using one of my superclass initializers. Oh but the one I want to call is a *convenience* initializer so I can't, unless I turn my new initializer into a convenience initializer. Except wait, a convenience initializer must delegate with self.init(), so it can't even call a superclass initializer!

And it just goes round and round and round. I don't know if I should try to convert all of my initializers to convenience initializers or the other way around.

Why all this nonsensical madness? Get rid of the distinction and go back to nice clean powerful initializers like Objective-C. I mean what does it have to take? This is a complete nightmare.

So here's how the story goes.

I was in my academic writing class the other day and we were learning about APA formatting for our argumentative essays. We have a blackboard, whiteboard, projector connected to a pc and even a lovely projector screen to present with in the classroom.

I sit at the front right of the room. Closest to the window(it's behind me as all the desks face inwards)

Professor walks up to front of class and says we are going to learn how to format our typed essays properly.

Awesome, I thought. Pulled out my XPS laptop and fired it up. As I was making a new Word document, I hear scratching. I look up and the professor is writing with CHALK on the BLACKBOARD. I was astonished. Making matters worse, she started from the far left of the board from which the glare from the window was the greatest. I could not see anything. And from that point on I knew this class was going to be abysmal.

What was so depressing was my professor never once touched the projector. Scraping and erasing. Over and over. Couldn't see if it was a period or a comma after the first initial.

My eyes were never so dry from squinting, rolling my eyes and face-palming over and over. After an hour and 15 minute class, I was not far away from drowning my XPS in my tears.

!rant, story

Wonder if I’m alone on this:
I have habits.
Always use the same cup, with very same amount of coffee grounds. Same four presses with the same fingers on the coffee machine.
Same way I place the cups in my desk. Same way I carry my notebook, same way I dry my hands. Same exact spot I place my card on the rfid reader. Use same elevator, same locker. God.
You name it, I do it on my own particular way.

Thing is, that I think about it. I do it consciously. I am just happier if things stay the way they are. It not just muscle memory thing.

Not judging here, just wonder if there’s people who can relate as much 🧐

I hate the process of trying to get hydrated when I’ve gone through a period of apparently thinking I’m a cactus.

When I don’t drink water at all, I feel fine. No dry mouth, no symptoms of dehydration.

I *start* trying to hydrate and it’s like my body thinks this is the best time to start giving me all those dehydration symptoms it doesn’t even bother with when I’m not drinking water because it’s just given up on me listening to them.

I drank 64 oz of water yesterday and woke up with my tongue stuck to the roof of my mouth and my throat scratchy.

I know that I need to keep drinking water in large quantities for a period of time for my body to chill the fuck out again, but words can’t describe how tempting it is to just go back to being a cactus.

Hydrating sucks.

OH MY FUCKING GOD IT'S BOOTING! Yesterday I spilled liquid on my desktop computer stopping it immediately, and today after letting it dry and rubbing it with some isopropyl alcohol it starts up as if nothing ever happened! 😊

However, I didn't try the graphics card under heavy load yet, maybe it can get unstable as the spillage affected it's power circuit area.

Conspiracy theory:
There is no parent CSS selector because Google effectively controls web standards, and if that existed then it would be extremely easy to hide ads, ruining their business model. Do you a-- help help they've got me hehgxh dry jvcgk cc d

Apparently they knew how to program in bible (partial translation of a traditional passover song below):

If He had brought us out from Egypt,
and had not carried out judgments against them
— Dayenu, it would have sufficed!
If He had carried out judgments against them,
and not against their idols
— Dayenu, it would have sufficed!
If He had destroyed their idols,
and had not smitten their first-born
— Dayenu, it would have sufficed!
If He had smitten their first-born,
and had not given us their wealth
— Dayenu, it would have sufficed!
If He had given us their wealth,
and had not split the sea for us
— Dayenu, it would have sufficed!
If He had split the sea for us,
and had not taken us through it on dry land
— Dayenu, it would have sufficed!

Note to self: Always do a dry run first when you have --delete-before using rsync.

Long story short I wanted to restore some folders from my external HDD to the home directory on my laptop XD I should have specified the exact folders 😹

About half an year ago, I literally fought with my DS teacher for half an hour in front of whole class,

REASON:
That dude couldn't saw the infinite while loop on his BINARY SEARCH algo hand written on board...

I mean come on dude, binary search is one of the simplest algo, and he didn't agreed with me until he dry run his written code(PS: the only thing I liked about him...HE KNOWS HOW TO DRY RUN)....

Scariest part: He was supposed to teach us trees and graphs in about a month
And it was my first day in that class

I always design my UIs to be cold, dead, sterile, and painstakingly perfect. It should be dry, so dry that if you were to drop my UI into the ocean, it would absorb all the water down to the last drop and remain dry still. I want people looking at it to feel dehydrated, short of breath and mesmerized. It should be so extreme that you have no choice but to stare in fascination. Fun fact: I once forgot to close a parenthesis, and the code that spilled out became the Sahara desert. It’s dryer than her vagina when you explain your Vim config.

Just got inspired/pissed off enough to write another app... For work....

Guess my dry periods end either tonight or this weekend

I'm starting to think that DRY is overrated.

When programmers try too hard to reuse everything that already exists on their code.

I use Linkedin but I wonder why people still asks me my resume. It sure feels not DRY to have 2 places to keep your career history. 🙄

#developerfeels

At the airport with the missus going back home, making time in the duty free. One of the people working on it asked a very dry "what are you looking for?" with no salutation whatsoever. I was this👉👈close to answer "a new job!"

Today I woke up 🌅 wanting to write code that is more art 🎨🖌️ than just the usual dry technical stuff...

I want to look at my commits this afternoon and feel proud about mastery and craft!

Watching any device update, is like looking at paint dry

The year was 2006. During the first half of my career, I use to work in the NOC. This was before I made my transition to software engineer. I worked on the third shift for a bank services company. The company was on a down turn. Just years earlier they just went public, and secured a deal with a huge well known bank. Eventually they entered a really bad contract with the bank and was put into a deal they couldn't deliver on. The partnership collapse and their stock plummeted. The CEO was dismissed, and a new CEO came in who wanted to "clean things up".

Anyway I entered the company about a year after this whole thing went down. The NOC was a good stepping stone for my career. They let me work as many hours as I liked. And I took advantage of it, clocking in 80 hours a week on average. They gave me the nick name "Iron Man".

Things started to turn around for the company when we were able to secure a support contract with a huge bank in the Alabama area. As the NOC we were told to handle the migration and facilitate the onboarding.

The onboarding was a mess with terrible instructions that didn't work. A bunch of software packages that crashed. And the network engineers were tips off, as they tunnel between our network and the banks was too narrow, creating an unstable connection between us and them. Oh, and there were all sorts of database corruption issues.

There was also another bank that was using an old version of our software. The sells team had been trying to get them off our old software for over a year. They refuse to move. This bank was the last one using this version, and our organization wanted to completely cut support.

One of the issue we would have is that they had an overnight batch job that had an ETA to be done by 7 AM. The job would often get stuck because this version of the software didn't know how to fail when it was caught in an undesired state. So the job hung, and since the job didn't have logging, no one could tell if it failed unless the logs stopped moving for an hour. It was a heavily manually process that was annoying to deal with. So we would kill the JVM to "speed" the job up. One day I killed the JVM but the job was still late. They told me that they appreciated the effort, but that my job was only to report the problem and not fix it.

This got me caught up in a major scandal. Basically they wanted the job to always have issues everyday. Since this was critical for them, all we needed to do was keep reporting it, and then eventually this would cause the client to have to upgrade to our new software. It was our sales team trying to play dirty. It immediately made me a menace in the company.

For the next 6 months I was constantly harassed and bullied by management. My work was nitpicked. They asked me to come into work nearly everyday, and there was a point I worked 7 days with no off days. They were trying to run me so dry that I would quit. But I never did.

On my last day at the company, I was on a critical call with a customer, and my supervisor was also on the line. My supervisor made a request that made no sense, and was impossible. I told her it wasn't possible. She then scalded me on the call in front of customers. She said "I'm your supervisor, you're just a NOC technician, you do what I say and don't talk back". It was embarrassing to be reprimanded on a call with customers. I never quite recovered from that. I could fill myself steaming with anger. It was one of the first times in my adult life that I felt I really wanted to be violent towards someone. It was such a negative feeling I quit that day at the end of my shift with no job lined up.

I walked away from the job feeling very uncertain about my future, but VERY relieved. I paid the price, basically unable to find a job until a year and a half later. And even was forced to move back in with my mother. After I left, the company still gave my a severance. Probably because of the supervisor's unprofessional conduct in front of customers, and the company probably needed to save face. The 2008 crash kept me out of work until 2009. It did give me time to work on myself, and I swore to never let a job stress me out to that degree. That job was also my last NOC job and the last job where did shift work. My next few jobs was Application Support and I eventually moved into development full time, which is what I always wanted to do.

Anyway sorry if it's a bit long, but that's my burnout story.

Am I the only one that cringes when I see software developer consistently ranked as one of the best jobs to have? Are other jobs that horrible that this is as good as it gets? I’m probably too cynical I suppose.

I feel like I was seduced by the fun of programming only to have the corporate enterprise suck my soul dry.

so I did dry january...

conclusions:

- perhaps a slight amount of more energy, but then I just work way more than i would anyway, since there is nothing else to do
- anxiety / stress not really affected or reduced
- sleep not noticably improved either

so overall I don't think I really get any of the so called "benefits" that the health gurus claim 🤡

needless to say I will be enjoying some scotch tonight

When someone asks to borrow your brand new, unused, dry erase marker, and then they use it to write all over a cardboard box

Heres a rant you dont see everyday, the lazy gits in my office who dont clean up after themselves. Go to the kitchen to make coffee only to be confronted by a mountain of dishes, the peak of which may have been level with High Hrothgar. Had to dry them and put them away before I could really even move. Like just wash something after you use it, then take the extra 20 seconds to dry it and put it away, dont just rinse it and then leave it sitting there. AAARRRGGGHHHH

So this past few days of a mix bag of emotions. Friday's weekly deliverables on our first dry run at launch, I squeeze across the line in an embarrassing finish. Decision to proceed with the live run to be delayed, not going to happen if I've got something to say about it.

Next day, vendor on the house my wife has purchased (our first!!) and says we can move the settlement date ahead 4 weeks! Winning!

Monday, meeting with all stakeholders on the fuck up that was my deliverables I'm responsible for, granted a conditional pass. "Don't worry, I got this."

Tuesday, received the results of a technical challenge I've given one of the developer candidates - he smashed it. Keen to give him the job!

Thank goodness for Dry Runs!

Being victim of an arbitrary worplace's culture on dev experience and documentation makes me a very frustrated dev.

Often I do want to document, and by that, I don't mean laying an inline comment that is exactly the function's name, I mean going full technical writer on steroids. I can and WILL get very verbose, yes, explaining every single way you can use a service - no matter how self explanatory the code might look.
I know developers (and me included) can, and sometimes will, write the best variable and function names at the time, wondering if they reached the peak of clean, DRY code that would make Robert Martin have a seizure and piss himself, only to find weeks later after working on something else that their work is unreadable. Of course.
I know the doc's public, it's me, and I've done this.

But then again explain for the people in the back how the FUUUUCK are we meant to suggest improvements, when we are not the ones who are prioritising features and shit WITH the business?

Just email me when the fucking team recycles, and no new team member knows how to even setup the IDEs because this huge piece of monumental shit called CompanyTM is also run by VPN. Fuck, no one wants to access that garbage, you have no docs.

I once tried setting up a culture for documentation. I did an herculean amount of work studying what solutions were internally homologated, how steep the learning curve would be from what we had at the moment (NOTHING, WE HAD FUCKING NOTHING, jesus christ, I even interviewed SEVENTEEN other squads to PROVE they FUCKING NEED
DOCS
TO WORK

You know what happened to that effort?
It had a few "clap" reactions on a Teams meeting and it never reached the kanban.
It didn't even made it to backlog.

I honestly hope that, someday, an alien fenomenon affects the whole company, making their memories completely reset, only to have the first one - after the whole public ordeal on why our brains became milkshake -, to say: "oh, boy, I wish we had documented this".
Then I will bring them to the back and shoot them.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

I don't know if this is a joke or a miracle.
I was pooping myself on a toilet, and beside me was a bucket of water, then there was a mosquito in my palm where I held my phone. after I snap it, I accidentally threw my phone at the bucket of water.

First and foremost. It's not a water-proof phone, so don't expect that I'm rich. I immediately grab it and it's so wet.

After a while, it gets a lot of touch bug and plugged in headset which is full of water in it.

tried to wash it after I'm done pooping. shut the phone and wait until it's all dry.

After that, my phone went to teamwip(bootloader) telling me that the custom OS is missing.

After some coding, I checked my phone and it's all normal now.

Lesson Learned: never shit when you have a phone with you.

The „UI-God“ in our team has never heard of dry or clean code.
Clashing classnames for modules in global namespace, gives a f* about patterns, naming conventions, structure and everytime I rebase it breaks my code.
I need the same amount of time fixing his work as he spends on it.

Say after me: DRY, DRY, DRY, DRY...

Unemployed Game Dev & Co.

Im trying dry January.. so far or was easy but now I’m watching terminator and I really want a whiskey..

Trying to talk about development principles in a place with shitty code and suddenly realise half the group is laughing. When asked why they replied those abbreviations are so funny (DRY, YAGNI, KiSS). And one of them is supposedly a senior Dev. fml

I just had a Rumpsteak.
Tasted like dry, raw meat with some sawdust on it.
Hell if I printed out my code and ate the paper it'd been better than that.

When you got to get through the swarm of elective classes to get to the meat of the bones in a Software Development degree 😤

How many times do we need to take Math in order to get across that we only use like 1/4 of what is actually thought and apply it to IRL scenarios?!

My FASFA is gonna run dry at this rate and I just wanna start these Software Development classes already 🙄😭🙏

Debugging a task, that's sending emails to too many customers.
Supervisor: "Never mind, just test in production, there is a dry run flag for the tasks."
Just in case I test locally...
Flags tried:
--dryrun="TRUE" => Error, failed to send mail.
--dryrun=TRUE => Error, failed to send mail.
--dryrun="true" => Not trying to send mail.

If it's THIS PICKY a little more documentation would be nice.
And by a little more I mean: more than the task base class in a giant php monstrosity without phpdocs expecting its code to be self-documenting.

Stay DRY!

Corporate developers... Is your job exciting? Do you enjoy the work place environment you are in? I ask because corporate work environments I've heard are very dry and boring.

Facebook _royally_ fucked us. I work in publishing and when Fuckbook pulled and refocused their resources elsewhere, we're left high and dry. And to think, these companies (including Google) would wine and dine you, give you tours and food at their regional and local HQs to make you feel "important", and how important the "partnership" will be for both. In my country, social media penetration is above 80% and Fuckbook is king. Thanks to these assholes, we lost half of our traffic and dipping due to readers avoiding news altogether. Google, doing it's usual thing, pushing AMP then abandoning it. Fuck these assholes.

(a slide acoustic guitar plays on the background and the cowboy starts speaking)
It was a dry october day, back in good old 2017. I had this job from a client that I never met and was doing some coding for money.

After days of no sleep, no food and no rest, I finally decided to take a nap so I paused my music.

It was at this moment I found out my machine was making funny noises. Like a dingo makin' a run from it's enemies with a whelping noise.

Clicked on my computer and tried to find an ol' file from the archive drive but the machine won't let me, sayin' the disk ain't ready yet.

I tried disk manager, disk scanner, whatever the tools at my disposal all in vain. Then I said what the hell, I'll just restart my machine and it'll be alright.

The machine rebooted but the disk was gone. It was dead like a deer I ran over. I was upset, but not aware of the calamity headin' my way.

In just a few days my other 2 disks died suddenly. The loss of data, all the effort, none of them mattered. I felt numb and decided it was time for a fresh start.

Plugged in a Windows install disk, started the sequence, a screen came up askin' me which damned and alive disk I wanna install the fresh OS. I had two same make and model SSD disks, chose the one thinkin' it was the Windows drive, hell it wasnt... It was with all "my documents", "downloads", "pictures" folders and now I had two SSD drives with two Windows installations and nothing else.

The folks in town took a dab at me for months, even the bartender of the salloon refused to give me a drink. Sayin' it was a matter of reputation...

Turned out the bastard who fried my disks was the Madde Dog PSU Tannen who had a bad temper so here I am, tellin' my story to milk breathers and cherishing old days of data...

How do you tell people in your team their code is poorly written?

I am not an amazing developer, I lack experience of real world and don't have many finished products under my belt.

But I feel/think my code is well separated into separate classes, follows DRY well and is generally considered as following good practises.

However, the main Dev in this new small team which has been put together and I have been appointed to manage sees things differently.

He writes good functional code(it completes it main purpose) however it's all in the one program.cs file, lacks good comments and is just generally untidy :(

I kinda fell into this whole management thing and it's kinda new to me..

Maybe he just needs a bit of direction? I am going to be putting in a code styling guide

Any tips on managing a Dev team would be very much appreciated.

PS. Iv been around for a while, and did previously have an account which was quite active, however I decided to delete and create this new more anonymous account :P

The downside of writing reusable, abstracted, DRY code for multiple applications to use: you have to remember to test changes in all the contexts... my org has to hire contractors project by project as we dont have the budget to have more devs than just 1 (me) on permanently. the contractors tho often don't know about all the places our code gets used. And sometimes I even forget - last week in the rush to finish some project, we forgot to think about how a library change made for benefit of a new project a few weeks ago might effect an older (in production) project. Until shit started breaking. Annoying. very annoying. luckily i fixed it (rolled back) before the weekend, but thursday and friday were quite stressful... now tomorrow, a bunch of sleuthing time to figure out exactly what recent change caused it... argh....

I am just student looking for job, and got this pre interview test:
Develop an Android or iOS app with login and password input field, download button, place for image we prvided.

... reading further:
What we are looking for in the code ?
internal quality:
-consistent formatting of the source code
-clean, robust code without smells
-consistent abstractions and logical overall structure
-no cyclic dependencies
-code organized in meaningful layers
-low coupling and high cohesion
-descriptive and intention-revealing names of packages, classes, methods etc.
-single small functions that do one thing
-truly object-oriented design with proper encapsulation, sticking to DRY and SOLID principles, without procedural anti-patterns
-lots of bonus points for advanced techniques like design patterns, dependency injection, design by contract and especially unit (or even functional or integration) tests

external quality:
-the app should be fully functional, with every state, user input, boundary condition etc. taken care of (although this app is indeed very small, treat it as a part of big production-ready project)
-the app should correctly handle screen orientation changes, device resources and permissions, incoming calls, network connection issues, being pushed to the background, signing deal with the devil :D and other platform intricacies and should recover from these events gracefully
-lowest API level is not defined - use what you think is reasonable in these days
-bonus points if the app interacts with the user in an informative and helpful way
-bonus points for nice looks - use a clean, simple yet effective layout and design

... I mean really ? and they give me like 2 days ?

Story, !rant.

So after previously telling the story of my laptop in the rain, I thought I should follow up with this one. (this is couple months later)

My laptop was bought second hand by my father (who doesn't know anything about computers) and the poor thing had a tendency to overheat. It worked fine, but under heavy load it would only last a couple minutes before it shut down.

So once I was cleaning out the fan (as dust accumulated in there) and I ran it under the tap, to get everything off. Sure, you might cringe at the idea but I thought some water wouldn't hurt it, especially after surviving en evening in the rain. So I cleaned it and let it dry.

A while later, when it finished drying I started to reassemble my laptop. After about 30 mins of fiddling with it, it was back together and ready for a fresh start! So I powered it on.

Sparks flew. Smoke started coming off the motherboard. More sparks.

😯

I pulled the cord. "Fuck, glad I caught it on time..."

I waited a while longer. Turn it back on. "Fan is not functioning properly or is missing". FML. After all it had survived, a bit of water in the circuit that made the fan spin is what took it down 😑

Fast forward two years (without a fan, shitty days), and I bought a second hand Lenovo laptop that I adore. So I thought I'd sell the laptop on Ebay, but first I should fix the fan so that I wouldn't have to sell it for next to nothing. Part number was hard to find, and bought it from somewhere in Europe. Four weeks later, the fan arrived at my doorstep.

Took the laptop apart (have I mentioned how hard that was?) and replaced the fan. Felt good to fix what I had ruined two years back. Put it back together (after applying thermal paste, I'm not a monster) and powered it on.

"Fan is not functioning properly or is missing"

😑

After checking the connection a couple times, I realized that what had given out was the motherboard connector for the fan, after the water incident. Wasted 40 dollars and several hours of my time for nothing.

The laptop that survived hours in the rain was taken down by a wee bit of water. So sad.

I’ve been working at my company for about 3 years now and under 2 managers. In my time I’ve grown to be a technical anchor and SME in multiple facets of our architecture. First manager was cool and I could really see my development under him. Then he gets promoted and I get a new manager. New manager just rides me and bleeds me dry, all while telling me “you’re just a couple months away from Senior” for like 2 years. Every time I meet with him he still says I’m not ready even though I step up and do more and more and more. He’s never satisfied. Then we recently had a shift in the roles in the company where there’s a new intermediate role in between my role and Senior which I was gunning for. After a few more months he says to me “Congratulations, we finally opened up a position to promote you… to this other role that you didn’t want”.

Naturally, I’m pissed. So I start looking at open reqs for the Senior role I’m looking for. I applied for a job and interviewed for it. I “aced” the Senior interview. The new team wants to bring me on. They tell HR that they want to hire me. Now HR is pushing back saying “hey now, you can’t just SKIP roles like that” even though it was an open requisition that I applied to, not even an in-line promotion and also they just opened this intermediate position I’m skipping like 3 months ago and again I’ve been here for 3 years. So even after crushing the interview and the other team loving me I still won’t get the job because of stupid corporate bureaucratic bullshit.

I've run dry of coding inspiration / will to code. What are your suggestions?

I hate Matlab.

It's slow.

It's full of propriety nonsense.

It's costs money, which automatically makes it the worst thing to ever mar the beautiful face of the programming world.

Just so you know where I'm coming from, I own a 1980 Fiat X1/9. Needless to say I like to be under the hood and need to feel connected to what I'm working with.

The feeling I get when I want to pop the hood and maybe optimize something only to remember that this is a corrupt proprietary money machine built on the dry bones and scattered dreams of CS students whose sheltered coding experience won't give them a chance in the real world-- is a feeling I can not tolerate.

I quit.

What is the leading cause of dry skin? Towels

Was supposed to be studying for a test today at 1am (it's in a few hours). Instead starts writing the date in binary, hexadecimal and octal (and then decimal). Go me, watch me fail that test LoL

PS: those dry erase pens were the best thing I could ever buy. I love writing on my windows

what is DRY?
-the previous dev (probably)