To be a good developer, you must thrive in chaos, and have an insatiable desire to turn it into order.

All user input, both work tasks and actual application input, is pure fucking chaos.

The only way to turn that input into anything usable, is to interpret, structure and categorize it, to describe the rules for transformation as adequately as you can.

Sometimes companies create semi-helpful roles to assist you with this process. Often, these people are so unaware of the delicacy of the existing chaos, that any decision they make just ripples out in waves leaving nearly irreparable confusion and destruction in its path.

So applications themselves also slowly wear down into chaos under pressure of chaotic steak-holders which never seem to be able to choose between peppercorn or bernaise sauce for their steaks.

Features are added, data is migrated between formats, rules become unclear. Is ketchup even fucking valid, as a steak sauce?

The only way to preserve an application long term, is refactoring chaos into order.

But... the ocean of chaos will never end.

You must learn to swim in it.

All you can hope to do is create little pools of clarity where new creative ideas can freely spawn.

Ideas which will no doubt end up polluting their own environment, but that's a problem for tomorrow.

So you must learn to deal with the infinite stream of perplexed reactions from those who can't attach screenshots to issue reports.

You must deflect dragging conversations from those who never quite manage to translate gut feeling into rational sentences.

You must learn to deal with the fact that in reality there are no true microservice backends. There are no clean React frontends. There are no normalized databases. Full test coverage, well-executed retrospectives, finished sprints -- they are all as real as spherical cows in a vacuum.

There is no such thing as clean code.

There is only "relatively cleaner code", and even then there are arguments as to why it would be "subjectively relatively cleaner code".

Every repository, every product, every team and every company is an amalgamation of half-implemented ideals, well-intended tug of war games, and brilliantly shattered dreams.

You will encounter fragmented shards of perfect APIs, miles of tangled barbed documentation, beheaded validator classes, bloody mangled corpses of analytical dashboards, crumbled concrete databases.

You must be able to breathe in those thick toxic clouds of rotting technical and procedural debt, look at your reflection in the locker room mirror while you struggle yourself into a hazmat suit, and think:

"Fuck yes, I was born for this job".

My five-year-old daughter asked me to program her Android tablet today.

Daughter: Daddy, can you make my tablet do something?

Me: What do you want to make it do?

Daughter: I want it to get games for me. I want it to pick games I like and get the different games so I can play them after I get home from school.

My daughter asked me to implement:

1. At the least, a predictive algorithm to choose new games for her based on her likes and dislikes.

2. At the most, an adaptive artificial intelligence that will learn what games she likes to play.

Current specifications are unclear. Need revision.

This is dedicated to all Webdevs, especially those WordPress fanboys.

I was reflecting on some things since I do more frequent freelance jobs at the time. And I have to admit: people are fucking crazy.

I had some serious talk with customers and some serious talk for people I work as subsidiary.

The average customer thinks a nice webpage costs I'm 9-50 bucks. They got some shitty Webhosting for 1-5$/month including domain and think they are set.

They have unclear visions about what they actually want, it all boils down to "I like the design". I made a page for someone who just posted images, no text nothing and I told him a trillion times NEEDS some text, even a fucking picture description would be sufficient, else he'll never score anything at google.

Ofc it got denied, now he's bitching how nobody finds the site when they google his name. The other thing is that Wordpress became the solution for everything.

I'm a fucking certified magento developer and I hate magento with a passion. Magento is an overabstracted clusterfuck and believe me, I did the certification I had to learn more than average about the core. But damn, don't slap woocommerce on everything.

Narrowninded fucktards, the cheap out of the box solution isn't always the best.

Don't cry if you got hacked because you were too dumb to upgrade your wordpress. Don't tell me to do some "enhancements" on a server you probably share with 100 other uses. I can't fix your Webserver with your shitty ftp account.

I also hate WordPress with a burning passion. Cum guzzling cavetroll it is. It has it usages, but don't rely on a core So small every kind of extra functionality has to somehow tinkered on it and then expect it to work flawlessly and for 10$ price.

Of course you can buy a theme that, if it would have been special made for you cost 800$ or more, but it wasn't. It just looks like it from the outside. If you want customization you are at the mercy of the option it provides. I can't even tell how many times i spent whole evenings explaining how their shiny template works. Just to do some crazy shit with JavaScript like rearranging domelements because it didn't work as expected.

I still stay to my word. Nothing great has been nor will be created with a Wordpress core. Don't tell me how some great stuff has been achieved. Or wait, please do so. But before you do think about if that wouldn't been faster, cheaper, more reliable , etc... if done with a framework like symphony or laravel... or even zend or cake.

And that brings me back to the point:
Is cheap and "out of the box" really what you need and desire? As customer and as developer?

Once upon a time there was a dev.
The dev had a resume that said he could dev.
We called the dev, he sounded intelligent.
We hired the dev, who was a bit green, on a three month probationary period.
The dev did very little.
When asked, we said he contributed to discussions, but seemed unclear about what to do, and maybe they could keep him as an intern if they wanted to have him at all.
They hired him. As a full time dev.
6 months later, that dev was shocked to find we could log into the servers with a privileged account.
We (his team mates) were sad.
We asked him to fix a few prod errors.
A little while later he said "Done!"
We then had to walk him through how to actually fix them, not just add a couple pieces of info to the table.
We were sad, again.
We asked him to fix some prod errors again.
We had to walk him through the process again
We expressed concerns to our superiors about his abilities because he was all theory, no hands on ability
They promoted him
We were sad
A few of us said "Fuck you guys, I'm going home"
They said OK
Now that guy is the only one that "knows" that code base
I get calls sometimes asking me questions.
I told them to pay me a consultant fee.
They said no
I said no
They called again
I laughed at them

Listen to the people who know when you ask them questions.
Listen to the people who know when they tell you there is a problem
Don't be like that company

The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.

*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"

Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.

Privacy & security violations piss me off. Not to the point that I'll write on devRant about it, but to the point that coworkers get afraid from the bloodthirsty look in my eyes.

I know all startups proclaim this, but the one I work at is kind of industry-disrupting. Think Uber vs taxi drivers... so we have real, malicious enemies.

Yet there's still this mindset of "it won't happen to us" when it comes to data leaks or corporate spying.

Me: "I noticed we are tracking our end users without their consent, and store not just the color of their balls, but also their favorite soup flavor and how often they've cheated on their partner, as plain text in the system for every employee to read"

Various C-randomletter-Os: "Oh wow indubitably most serious indeed! Let's put 2 scrumbag masters on the issue, we will tackle this in a most agile manner! We shall use AI blockchains in the elastic cloud to encrypt those ball-colors!"

NO WHAT I MEANT WAS WHY THE FUCK DO WE EVEN STORE THAT INFORMATION. IT DOES IN NO WAY RELATE TO OUR BUSINESS!

"No reason, just future requirements for our data scientists"

I'M GRABBING A HARDDRIVE SHREDDER, THE DB SERVER GOES FIRST AND YOUR PENIS RIGHT AFTER THAT!

(if it's unclear, ball color was an optimistic euphemism for what boiled down to an analytics value which might as well have been "nigger: yes/no")

I need a break.

A break from stress of endless expectations
From school
From work
From being made fun of
From criticism
From criticizing myself
From not being able to do fun things
From vague instructions
From a lack of sleep
from inconsistency.
From unclear objectives
From financial/medical/emotional stress
From life
From hatred
From destruction of my emotional stability
From a lack of confidence
From unfulfilled decisions
From trying to hide under a mask
From jealousy
From lists
From repetitive obliteration of any hope I have
From me crap talking myself
From pleasing people

Oh well, at least after tomorrow, I’m on full-time break...

I see many people being irritated when it comes to StackOverflow and If I were to be honest I thought the same a while ago. But I noticed that I was misjudging the main point of Stackoverflow. It's not a forum to help people with their programming problems. It's a huge self writing document to gather every programming related questions and answers under a single platform if possible. That's why they won't down vote you even if you ask a question that was obvious in a language's official document as long as it wasn't in Stackoverflow. That's why questions should also be formatted accordingly which is clear and also informative in itself. I understand why stackoverflow is such a harsh place to ask questions and most of the time I prefer looking things for my self instead of asking a question. And I edit and review most questions on stackoverflow because I enjoy it. That also made me realize that stackoverflow needs to be elitist to preserve it's current quality. Who would want to see unclear duplicate questions that veteran stackoverflow users need to answer over and over again right ?

Asking the right question is hard because we humans most of the time don't know what we don't know. And it makes it really tiring to format your question the way that is fitting for a document. In those times I prefer to ask my questions on a more relaxed and chat focused platform before writing my main question on stackoverflow.

So that was my opinion on stackoverflow and it's harsh environment. It's definetly a hard to get into community which I can't even say I'm really a part of it. But looking at stackoverflow as a document that's being written by ut's users, it's easier to understand it's elitist approach. I hope you had some enjoyment from reading it.

You can't keep wasting your time on people who do not know what the fuck they want. You could be way more time efficient with serious clients.

*After I have finally deployed the requested features*

Client: Why did it take you two weeks in the end? You said it would take you a couple days.

Me: Because you told me to use my imagination on half of the tasks and you kept wanting me to change what I had created, thus unnecessarily doubling the time it should have taken. Besides that probably the unclear communication and the fact that you rarely called me back after you told me to call you.

Client: So if I tell you, exactly, how I want it next time you'll be able to do it in a couple days?

Me: I'm not sure, that depends on what you want. Tell me, exactly, what you want.

Client: Oh it's not much, I'll let you do your thing for the most.

Me: I can't handle another request, sorry. *Ends call*

doNotMessWithITTeamInAFuckingProject();

Last night me with my team have a discussion with my project team. Currently we have a project for our insurance client building a Learning Management System. The project condition already messed up since the first day i join a meeting. Because since its a consortium project with multiple company involved, one of company had a bad experience with another company. It happened few years back when both of company were somehow break up badly because miss communication (i heard this from one of my team).

Skip..skip... And then day to day like another stereotype IT projects when client and business analyst doing requirements gathering, the specs seems unclear and keep changing day by day even when I type this rant I'm sure it will change again.

Then something happened last night when my team leader force our business analyst to re index the use case number (imho) this is no need to be done, and i know the field conditions its so tough for all team members.

So many problems occured, actually this is a boring problem like lack of dev resource, lack of project management and all other stereotype IT projects had. Its sucks why this things is happening again.

Finally my fellow business analyst type a quite long message in our group and said that he maybe quit because its too tired and he felt that the leader only know about push push pushhhhhy fcking pussy, he never go to the client site and look what we've done and what we struggle so far.

I just don't know why, i know this guy earlier was an IT geek also, but when he leading a team he act like he never done IT project before, just know about pushing people without knowing what the context and sound to me like just rage push!

Damnit, i maybe quit also, you know we IT guy never affraid to quit anytime from the messed up condition like this. Even though we were at the bottom level in a project, but we hold the most main key for development.

Hope he (my leader) read this rant. And can realize what happened and fix this broken situation. I don't know what to say again, im in steady mode to quit anytime if something chaos happen nearly in the future.

doNotMessWithITTeamInAFuckingProject();

Rant about social media in general, including devRant.

I enjoy interacting with like minded people. What I do not enjoy is the whole degradation of the conversation at hand. Sooner or later, someone takes something the wrong way, addresses something this social network was not meant to address (it's devRant not Facebook), and the audience has a multitude of English as a #(rd/th/whatever) language human beings.

Accept that as the premise, and I think we could get along a lot better.

However commonly this fact is ignored. Understand the sentiment behind statements, not the statement itself. If any part of it is unclear, then request clarification.

Agree, disagree, civil debates one thing, but degrading the conversation to name calling or similar emotions only results in poor communication, useless emotions running high, and nothing gained.

</rant>

Yesterday I had an interesting interaction

- I complain about not having tickets for something, as it makes it unclear who needs to do what
- manager tries to call out on me for “not giving precise infos”
- A frustrating argument starts, ends up with manager defending himself telling we need a meeting with [other team] to sync on infos that are not clear
- meeting starts, manager starts to make a buffoon about himself
- other dev out of nowhere tells that the manager is not giving the task to him for some reason
- other manager is speechless at our manager’s incompetence

Managers.😎

Question everything!

Comments lie.. sometimes code does too.. Customers..they lie the most..and are sloppy..

Don't be like customers, don't be sloppy. If you were sloppy own it & don't lie about it!

Pick your fights (trying to fix vs rewrite the shit out of it)..you will know what to do more with experience..

RTFM & docs.. If things still unclear, ask before your dick gets stuck in a toaster!

Ask away, learn about the customers & how they use your product.. you'll be surprised how something intuitive to you might be a rocket science for them..meaning more room to fuck things up when using it..more ways you can adapt & prevent things..

Most of all, don't fuckin lie.. ever!!
If you lie on you're CV, we will find out.. If you fuck up something & lie about it, we will find out.. but it will cost us precious time when solving it from scratch.. People fuck up..that's a fact..how you go about it is what makes/breaks it for me. So don't ever fuckin lie to me!!

And don't be arogant.. if you complain about fixing bugs, this is not a job for you.. if you can't even fix the obvious ones you've put there in the first place..twice as bad..

So think before you code..what do you want to do, how you want to accomplish this, is it reusable, can it be extended, does it introduce new technology into the project, will it fuck up current setup.. once you have this shit figured out, code will write itself..

Did I mention already you're not to lie to me, ever?!

And don't try talking about me behind my back either..I've seen it backfire before, results were not good..

I'm gonna decline the next time someone asks me "hop in chat with them" to discuss their stackoverflow problem.

I'd already given my two cents about the problem in question and I thought something was unclear about that so I say okay what the hell, made a chat room and invited him in.

Him: So I have this OTHER problem with [insert JS plugin]
Me: ... I don't know enough about it. I've used that specific plugin maybe once. The question I offered you my help with was PHP.
Him: Yeah but can you take a look really quick?
Me: I'd have to reread the documentation. I literally don't remember how to use it.
Him: No problem, here's the documentation. I want to do X, Y and Z.
Me: I don't think you can X without doing A and B first.
Him: I was told not to do A, so how can I do X, Y and Z?

Fucking hell I'm not gonna do your job for you. You know english. There is documentation available. Just read it and at least try things.

Instruction unclear

Fucking people, why the hell are you reading into things instead of asking for clarification if something is unclear?

So much time, sweat and tears wasted on miscommunication.

When I said, "there might be a problem in the way component X method Y was implemented", i didnt mean go refactor the entire code of the component. Why waste 2 days of work on unnecessary refactor that nobody wanted and breaks changes + the bug is not fully fixed 😤

Raised a support ticket with an api provider about unclear error messages. They were as confused as I was and as the thread continued I essentially ended up debugging thier application for them!

2021: What is Metaverse?
Google: I "think" it means...

2022: What is Metaverse?
Google: Seems "maybe" it is a ...

2050: What is Metaverse?
Google: Mate to be honest It's unclear to me also.

Client: we need a report that <unclear requirements>
Me: alright, here's what you requested.
Client: that's not what I asked for.
Inner me: THAT'S EXACTLY WHAT YOU ASKED FOR!! WHAT THE FUCKING FUCK REEEEEEEEEEE!!!!

I just found out last Friday that my team collegues (all of them are team leads) are suffering from depression or the so called burn out syndrom. I guess it's my boss' fault. He never gives clear jobs, changes his mind from day to day, we have to manage unclear responsibilities and the baddest thing is that we think that our boss is too stressed out himself.

Do you have any advice for me how we as team could solve that besides changing employer? One thing to mention is, that my boss likes to hear himself talking. That makes it even harder for a guy like myself who is more or less introverted to come up with good arguments which are not overheard or overtalked immediately. What are your feedback strategies to your own boss, how do you bring such stuff on the table?

I fear that when nothing happens, my company will suffer very hard when the whole product engineering departement will fall apart (¼ of the whole company and is responsible for engineering and maintaining of internal services and managed services for our customers).

Well at least it was worth writing about it, maybe my subconcious mind will come up with a brilliant idea itself in the near future in some asynchronous way. But you might be the one with that valuable input, then don't hesitate to share, it will be welcome.

Rust: Unclear error output is seen as a compiler bug.
Me: 👏

SSIS & SQL Server: Unclear or absent error output is seen as an enterprise feature. It's so mature!
Me: 😩

Been bughunting the last week or so on this import job that is suddenly running so slowly that it takes more than 24h and is restarting on top of itself.

It used to run in anywhere from 4 to 8 hours, which was bad enough. You see, it ran on timer scheduled by our main site. So our deployment window was determined by when this job finished, and if it didn't finish during work hours, then no deployment that day.

So we got the idea to move it to a separate service to eliminate that deployment window bottleneck. And now, seemingly unrelated, it is just running slow as shit.

There is a lot of bad design in the code, and we know we want to build a completely new solution. But we also absolutely need this import to run every day until a better solution can take over.

We've taken care of some of the most obvious problems that could cause the poor performance, but it's unclear whether it's going to be enough. And with a runtime of about a day and wild variations of the most atomic partial imports, it's extremely tedious to test as well...

I'll post a rant (will be long) soon-ish on the root of the asinine problem...

TL;DR
Anyone got a better suggestion of killing a WLAN router signal than a Faraday Cage?
-----------------------
As to the point as I can manage atm...
My ISP forces a proprietary router/modem for them to script my static IPv4 block (/28, aka 13 usable). Modifying this equipment in any way or using the vast majority of tactics to modify its behaviour = Federal Felony... with my history, it couldn't be construed as mistake/ignorance of this fact, so I'd likely end up working for some branch of the gov to mitigate the costs of standard prison (on both ends... handicapped af = expensive af to comply with base human rights laws... plus I'd be a dangerous prisoner from what I've been told).

I NEED the ipv6 functionality TOTALLY off... I've written this into every kernel and every container config at kernel level.

The issue is, I don't trust their shit device (which "should" also be set to no ipv6 via gui... non-GUI = fed felony).

This horrid device, they apparently made them for home use initially (to be fair it has decent specs and tolerable RAM), so included WiFi... that comes on by itself.
Disable the WiFi!... except I cant (at least not without 'tampering').
Why? Well acc to the GUI it's not enabled in the first place. Acc to the 'tech support' it's apparently a paid feature (yes, nonsense) that I have not paid for (nor would I), meaning on their end's GUI and DBs I also don't have WiFi ability from that dev.

So... Not trusting the other settings and the dev, being something im not allowed to directly config outside of their GUI that doesn't realise it's putting out a usable signal despite registering DHCP on behalf of that non-existent signal. I NEED to kill those signals.

I realise it likely sounds extreme to make and use a Faraday Cage for a router/modem (secondary modem, it parses the initial modem's output, via script, to allow the static block to be accessed). I really dont know any other way that's legal to restrict it.

Oh, in case unclear, I have tried so many ways to get them to just allow me to use any device (pref. mine, but even their's) that i can simply script myself... it's a no-go.

"Please move the logo left. The text goes a bit under."

Do you guys think people realize how unclear they are, and are just too fucking lazy to write the full spec? Or are they just so fucking stupid they don't realize I literally have no fucking clue what to do exactly with comments like these?

I guess Hanlon's razor applies here, but some days I just don't know...

Happy Friday! ☠️

After 2 days of trying to understand unclear requirements I got for a new project... I discover my boss wrote them....

From the description, it read like he flipped it around from what he actually wanted (there's a difference between parent-children and child-parent)

And he always gave me the feeling that he had gotten it from some business team so I spent 2 days trying to figure out who wrote these requirements so I could ask them.

FML....

The pain of using third-party library with unclear documentation.

"Oh just read the code"

well it would've helped IF THE CODECLIMATE RATING ISN'T 0.4. D:

Just JIRA things:

We've got a very descriptive ticket with the title: "API Interface"

Can't wait for the rest of this Friday to play out, I'm already joyful and in the holiday spirit.

School's principle: *is being unclear of what is asked*
Me: *asks lots of questions to try to understand*
SP: *keeps being unclear*
Me: *think I understand, I'll do something that will match with what I'm supposed to do*
-- 2 days before due date --
SP: omg stop it's not that at all
Me: wait wtf you told me that 3 months ago
SP: yOu uNdersdtoOd wHat yOu WaNtEd, tHat'S a ProBlEm yOu rEaLLy nEed To fiX

HOW ABOUT YOU GO AND DIE SOMEWHERE YOU SON OF A BITCH
Now I have until monday to write 30 fucking pages of something that keeps making no fucking sense. FUCK !

I'm trapped in a sea of one line work requests. How fucking difficult is it to actually write down your requirements. If you can't be arsed, even after I have asked for clarifications several times, don't act all upset when what I implement doesn't match your expectations.

Me: Ok, we'll implement that message tech. But since the clients are servers in that architecture and can't speak IPv6 we've to use a dedicated VPN so the endpoint is able to connect to the servers (clients). Since we have limited network resources we should use VPN cert-encryption and send the actual data plain to save at least some overhead.

Boss: Ok! Let's do it!

Next day.

Boss: Hey! I talked to a guy from that message tech. Their encryption is certified. We should use that instead and get rid of the VPN to save the overhead!

Me: *unable to say a word*

What in "VPN in that architecture is mandatory" is unclear?

Well, I assume we'll kill the architecture then... Fun Time!

Sometimes, when the documentation of libraries of software is unclear, instead of asking the author and waiting for a reply, I browse through the source code to find out what the exact behavior is. It sometimes feels like I'm the only who does that.

There's something super broken about the interview process in our industry. I spent 30 minutes chatting with a hr recruiter. 2 hours on a coding screen. 1 hour for a technical interview. 1 hour talking with the head of engineering. But then they decided to pass on me. Well if things went well then, then I spend an entire fucking day on an onsite.

Wow. Since when did the industry get so bloated until we have to do so much to get a job? Is signal really that unclear so candidates have to jump through hoop after hoop?

BS.

"learning" html and css

So, there are these courses in my school, "ÜK" ("Überbetriebliche Kurse") we call them.
It's 5 days, a Tuesday to Thursday, next week Tuesday and Wednesday, last day in the afternoon we have a test.

Today is that Wednesday

I know html and css pretty well, so if was pretty easy, I didn't even bother to do some of the tasks we had
I did look through the book over the weekend to make sure I knew my stuff right

Now, the theoretical part of the test had stuff like "colspan" witch was nowhere to be seen in the book and PowerPoints, and some stuff was just unclear as fuck, seriously...

*looks up colspan*

Apparently it's a table cell that spans two columns, or more, if you want to

I never needed something like that, and we never looked at it, that's why I didn't know about it.

There where other unclear questions as well, so I went to the teacher after the test and told him.

He gave me an empty test where I made an X for stuff that wasn't in the book or the PowerPoints and wrote a bit for the stuff that was unclear.

I did know some more then some in the class, so I generally xed the stuff that we didn't learn
The teacher will correct it accordingly, and cut out the questions that we couldn't have known.
So that's at least something
For the next class, he's going to have some "theoretical learning" or whatever he called it

I mean, in the end it's fair, but it annoys me that these courses aren't as well thought out as they should be...

So after this course I can say:
I DIDN'T LEARN A FUCKING THING

Btw, the second part was changing a website up the way its telling you to, that was easier the the theoretical part, witch was ticking the right fucking box...

When...
- you start the day with good intentions.
- you want to fix some long-due issue
- you think: I'll google it and I'll solve it. What can it be? I just want to track correctly my subdomains with all-mighty Google Analytics

and the first answer you find is:
"Unfortunately, Google Analytics has a few hoops to jump ...blablabla More unfortunately, the Google Analytics documentation is unclear ...blabla"
and 20 more pages of blog.

Fuck.
Let's skip to the next good intention before the day turns bad

Unclear variables. It hurts.

==============
Getting Feedback Rant!
=============

When "this is simpler" feedback results in a function of 500 lines of code.

When I get "don't do X" in the feedback. Thank you very much. What do you want me to do instead?

Unclear feedback.

When the feedback giver changes his mind after I applied the changes!

When applying the feedback introduces a bug.

Simply opinionated feedback that is not enforced by any tool or backed up by any facts.
Please find something better to do in life.

Unactionable feedback.

"Consider X"
I will not consider thank you very much.

"Verify this works"
Duh..

When the feedback giver knows something that you don't.
I know this is a legit case.. still annoying.

"I disagree with the feature"
Go argue with the PM, not relevant to me, thanks!

=====================
GIVING FEEDBACK RANT
=====================

I rewrote the system. Please review it.

No need to review, just approve.

I will change this as part of the next ticket.

I would like to keep it the way it is.
lazy ass..

You can't test this.
It's impossible to test this.

No need to test this.

There's no point to test this.

I'll test this on production.

Not sure why this is working..

Please document this..
Because documentation is like a thing, you know.

Oh, this code is not related to this PR, I just don't want to open a new branch for such a small change. ignore it.

Ignore this.

This will be meaningful in my next change.

Screw Facebook SDK Docs.

TL:DR: Unclear requirements led to a complete code rework

Background: We (2 friends, both already work as developers beside studying, and myself) are in a course about multi core programming for Java. We got an simple assignment which we were about to finish today.

An other friend of us is also in this course and asked if he could use some special method which is far above the taught material. He got a email with the following answer: "You are free to use any features of java 8 apart from lambdas and concurrents as we use them for our next assignment." He told us as he couldn't believe that we weren't allowed to use lambdas an we sat in front of our codebase and the only thing we could think of was "fuck".

Our entire code base was filled with lambda expressions as the requirement paper didn't mention any restrictions apart from using java 8.

FUCKING FUCKTARDS GET YOUR REQUIREMENTS RIGHT AND SAY WHAT YOU DON'T WANT TO SEE.

And here I am, sitting in front of intellij and merging my lambda filled fixing branch with our now lambda free working branch.

Not commenting unclear code

Not the worst, but deserves a mention due to how common it is.

Say your whatever object has a method called Configure. You can infer a lot from the configuration parameters or type that it takes, but for whatever reason something is unclear or doesn't work.

Tooltip from xml comments: Sets the configuration.
Official guide: Sets the configuration <br />.
Technical API reference: Sets the configuration.

I would create a support ticket explaining how this is unclear if I wasn't half expecting the suggested solution to be "you know what I mean".

Can we normalize NOT using giant acronyms in GitHub issue threads? Nobody understands what you are saying.

The same goes for you, HackerNews users, we can't psychically jump into your ASCII LOL DDD ABC XYZ brain and automatically know what you mean.

Terrible project with unclear requirement, lots of legacy and a client that doesn't know what he wants. Quite a bit of procrastination because of this situation, then crunch day & night to hold the deadline.

Then the project was scrapped.

Over the course of a few months I have concluded that the newly hired _experienced_ developer is… not so experienced. In fact, it is very unclear what he/she actually brings to the table at all.

How this individual actually got hired is proof that middle management has no clue of what they are doing. And it is poison to the organization. Bad management (middle/semi-upper in this case) is such a waste. More so than the newly hired incompetent developer. I am beginning to think she/he actually lied during the interviews. And I am not alone in my suspicions.

"Just start ahead"

I am supposed to transform calls from one api to another one. Yet there's no documentation, ambiguous code statements, no examples of what values are contained -- but sure, let me just start assuming how the whole thing is supposed to work. That won't lead us more into a murky waters at all.

Even more frustrating: We own the api. We should be able to tell by the access logs how we are queried. Yet for some reason, access logs cannot be accessed and I shall "just work from the swagger defintion".

Well, that swagger definition is broken, its example are shit (somebody liked to use undefined in optional fields, making me wonder even more what the heck is going on here), and I have no idea of what I am doing. Fun times.

Man, I enjoy the work I do and my boss is a great guy, but being rushed is never fun. And it's hard to say "it'll be done soon" if there's still some major features missing and the implementation is still unclear.

Can't a junior just take his time to make some decent code that won't end as spaghetti? I have enough PTSD of the first project I did here, which I still have to bugfix at least once a month 😂

rant !dev

The other day I signed up for a 12 months gym membership. Things have gone wrong.

First, they managed to trick me into signing up at all because in the shitty handwriting I have mistaken a 9 for a 1, so the actual price was a bit higher than I thought it was (+15%).
Second, a day after signing up I get a medical diagnosis with unclear prognosis. I write them a nice letter with an added note from the Dr, explaining that I will not be able to go to the gym for an unforeseen time and asking to nullify the contract. Of course they respond me with an email saying "we need details about the illness, the one you sent us is not enough" or in short "fuck you, you're trapped".

I hate gyms (the business side). They have no ethics whatsoever.

Now I feel just as angry at myself for not double checking the price on the contract and for signing up at all.

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

Why is tech management so f-ing distant? Very often NOT in meetings which they created and very not interested in anything the team/teams do. It is really a large offset between the work actually being done, the day-to-day operations that we do and the competence of management to acknowledge the fact that we actually do those things.

A lot of times they just stay silent in meetings and in the end they say something to try and make some conclusion and perhaps something ”funny” to try and lighten up the atmosphere. They fail on both of their tasks. They have no clue and are not interested in learning.

I feel like many of them don’t actually do anything. They are often ”away” but it is really unclear what that means.

I think it is symptom of a truly dysfunctional tech process. Bad leaders tend to hire more bad leaders and it is a toxic circle ending in good competent people leaving wanting more in the leadership.

went to client presentation yesterday. client wasted 2 hours on discussing non technical matters like what data goes on the field when we were asked and did develop as per their data. just looked at a page and kept on saying it's their mistake for the unclear term. didn't even reach the part that we went to to show

First rant;

First of all I am an applied computer science student in the second semester.

We've got a few assignments and the first set went fine but this last week boy ohh boy - first of all today I got noticed by one of my two teammates that the other one won't get stuff done in this assignment (he also did next to nothing in the first)
Also the the assignment is unclear and the given methods and parameters don't care about naming conventions (for one method I don't even know what it should do). Also we have to use new liberies (java.io etc.) and learn them on our own so far it would be okay, the time limit is two weeks, also doable
BUT the same chair also made one assignment for web development with the same deadline and also no explanation how to do stuff.

I don't say I am perfect but the expectations are too high, while also studying for other modules

im really tired of people who just happen to have been around for 10+ years being put into management roles despite not knowing how to manage, especially for software projects. really feel like im in the wrong field even though i love programming and am good at what i do. past few jobs have been similar in poor management, unclear roadmaps, etc., but this is the first time ive been directly insulted by someone above me. the pay isnt even that great here. i could just leave but why bother if every other company is pretty much the same

one thing that's unclear to me about GDPR; if you have no servers in the EU, how do they have any jurisdiction over you anyway??

So, I have been working for a company XYZ for about 2 years now and for this 2 years, we are just two engineers handling everything. The job is becoming super stressful and time consuming, the founders dictates how the engineering team operate, ranging from choosing a third party service we are to integrate into the platform without letting us know and also study the api to see if it will be the most viable one to use.

Imagine using a third party service that you can't get through to when something is unclear?

I and my team mate has asked the founders to hire engineers so the work load on us will reduce, they said it's on their mind ( this request was made months ago), fast forward last week, we were told to start interviewing interns ( I don't have problem with interns working with us ), but what we asked for was experience engineers working with us but the founders did entire 180 degree of what we asked.

We have been asking for a QA Engineer for months and months now, all we get is we will hire one, and till now nothing is been done.

Following good software practice has been a problem in company XYZ, we have been finding it difficult to write test and documentation (this shit makes me seriously sick and hate myt po self).

On top of all this, the salary is shitty, there are no benefits, we are coerced into working during weekends (most times), and we are also told to work during our holiday, no single health insurance.

I think I have come to that point where I will have to say good bye ( but I am finding it difficult to do this).

Any suggestions ? Should I wait until I get another job and then I resign from company XYZ or just resign.

Holy fucking shit bois. This is gonna be a long one.

So, its my last studying year for me. I found a nice apprenticeship in a dev company for which i'll have to make apps and stuff, so, I'll work at the company and at school.

Now it's good innit? Well here's the catch. I have to sign a contract for this. And the CUNT who is filling this shit is retarded enough to fuck up.

This bitch, a 40 yo accountant, surely filled many goddamn contracts before mine, but nooo, this wanker fucked this, the contract was missing important infos and some of them were incorrect, in short, it's not valid, 0/10, will never sign this.

Now here's the fun part, this cunt asked me for my infos, i gave them to him so that he could fill the document : he misinterpreted them, filling the paper with junk.

Today, I heard that he is unhappy of my behaviour towards him, and that I shouldn't insult his work with these accusations, saying that if I gave them more info (for which they didn't ask), there would be no problems.

He then called me, while I was in class, he acted smugly, said I was unclear and that I should gather more info for them, in other terms, "lmao do this yourself cunt"

"Fuck you, you cumstain, if you would've asked me, I would've been able to give you these infos right away, but you didn't, it's your fault for this, you're breaking mah balls yadda yadda"
(Roughly what I said, especially the insults)

I'm now forced to fill the contract myself because this bitch isn't able to google shit for 5 minutes to find everything he needed.

I have had so many problems with people of his kind, that I can't stand them now. Are they like animals? Do they feel my hate for them?

Sorry for dat long post, but fuck this, if the contract isn't filled, signed, and validated before the end of the month, I'm fucked, since i won't be able to sign up for the school.

Does anyone have had any problems like this? Like, a very egocentric cunt that isn't able to do something good because he is too proud to ask, so he prefers doing things his own way?

After a week of designing an API to our system for another team followed by redesigning it because they 'know what they need when they see it' I think I understand the pains all of you guys who work directly with customers go through what leads to exactly one question : How did you manage to never kill anyone?

I'm trying to improve my email setup once again and need your advice. My idea is as follows:
- 2-5 users
- 1 (sub)domain per user with a catchall
- users need to be able to also send from <any>@<subdomain>.<domain>
- costs up to 1€ per user (without domain)
- provider & server not hosted in five eyes and reasonably privacy friendly
- supports standard protocols (IMAP, SMTP)
- reliable
- does not depend on me to manage it daily/weekly
- Billing/Payment for all accounts/domains at once would be nice-to-have, but not necessary

I registered a domain with wint.global the other day and I actually managed to get this to work, but unfortunately their hosting has been very underwhelming.. the server was unreachable for a few minutes yesterday not only once, but roughly once an hour, and I'd really rather be able to actually receive (and retrieve) my mail. Also their Plesk is quite slow. To be fair for their price it's more like I pay for the domain and get the hosting for free, but I digress..

I am also considering self hosting, but realistically that means running it on a VPS and keeping at secure and patched, which I'd rather outsource to a company who can afford someone to regularly read CVEs and keep things running. I don't really want to worry about maintaining servers when I'm on holiday for example and while an unpatched game server is an acceptable risk, I'd rather keep my email server on good shape.

So in the end the question is: Which provider can fulfill my email dreams?

My research so far:
1. Tutanota doesn't offer standard protocols. I get their reasons but that also makes me depended on their service/software, which I wouldn't like. Multiple domains only on the business plans.
2.With Migadu I could easily hit their limits of incoming mails if someone signs up for too many newsletters and I can't (and don't want to) micromanage that.
3. Strato: Unclear whether I can create mails for subdomains. Also I don't like the company for multiple reasons. However I can access a domains hosted there and could try...
4. united-domains: Unclear whether I can create mails for subdomains.
5. posteo: No custom domains allowed.

I'm getting tired.. *sigh*

I hate it when clients send documents that aren't properly formatted.
I hate it even more when it's unclear what the content of the document is about. :/

Working with unclear requirements + changes related to that

I'm so fed up with Codecademy. I payed for the pro, and I admit I haven't been able to consistently use it everyday as I would like. But every fucking time I would be on a lecture of some sort, I swear to fucking to christ it's the most buggy, uninformative piece of shit! And everytime you're in deep into subjects, the information is beyond unclear!

AND GOD FORBID YOU NEED A FUCKING HINT! they leave you to dry saying in the hint that "Look back at the previous sections" or "try to remember the steps you've learned"

No you stupid fucking bitch for a site. I clicked on the hint because I needed an answer as to what I'm doing wrong, and to something that can stir me in the right path. My god....I feel so stupid for giving PRO a chance. I thought maybe it would be nice to have some sort of professional site would be useful.

I swear this early afternoon I was spending fucking forever on the first few lectures of HTML trying to figure out what the actual fuck is wrong with the system fucking up not letting me change directories. And the community was no help whatsoever to the issues at hand.

Again, why the fuck is Codecademy so goddamn buggy!? Sure it may be a fun site to fuck around with to get your feet wet on the free version. But is it too much to ask for some good actual lessons that are being payed for!?

Idk anymore. I'm sticking to just YouTube and other free help. This is the last time I spend a fucking penny to any site that's supposed to teach something valuable.

I feel so upset because I feel like I wasted my money and time on something that I thought could've helped a lot.

If anyone was asking if PRO is worth it....definitely not! Please don't waste money with it! Don't make my mistakes, stick to YouTube and other free sources! The least I can do is warn people about spending money on this site. Trust me it's not worth it. It may not seem bad in the beginning, but once you go deeper it becomes clear the issues.

If anything stick to only free!!

Has anyone had issues with the Docker Go Client (moby) and using containers with pointers? It would seem that the client swaps pointers or something, so I'd have to use the value instead. Might be very unclear, but if someone's had similar problems, I think you'd understand 😅

Bad (or at least uninformed due to unclear requirements) design decisions lead to somewhat perplexing (and above all, frustrating) problems down the line...

Here I am, wrote a cli client for event bus subscription, and since EC2 is eqv to Docker, had to fix the main function to keep it alive - now the deploy stage on the ci/cd pipeline fails due to startup script timing out. But why tho?

I’m not really sure whether I should’ve designed this differently from the get-go or whether my build and deploy configs don’t match anymore due to recent changes and I should figure out what’s wrong with them... or both.

Bottom line is: I have no idea what I’m doing.

Question.

Yesterday, I watched movie Moneyball yet again.

One particular dialogue caught my attention and I am kind of unclear on this. Can somebody explain?

"You get on base, we win. You don't, we lose. And I hate losing, Chavy. I hate it. I hate losing more than I even wanna win. There is a difference"

What is the difference?

Its annoying. Spent again hour trying to make run my symfony app with docker - and fucking does not work and is not clear why. Why this fucking docker is so unclear? Like does not see autoload.php file but I see it installed. Idiot docker.