Under settings, we made a checkbox labeled “Run Program Faster”. The state was saved but it didn’t do anything.

We turned it “on” when people said things were slow. Usually they were happy and no one complained the “run faster” option wasn’t working.

This is more just a note for younger and less experienced devs out there...

I've been doing this for around 25 years professionally, and about 15 years more generally beyond that. I've seen a lot and done a lot, many things most developers never will: built my own OS (nothing especially amazing, but still), created my own language and compiler for it, created multiple web frameworks and UI toolkits from scratch before those things were common like they are today. I've had eleven technical books published, along with some articles. I've done interviews and speaking engagements at various user groups, meetups and conferences. I've taught classes on programming. On the job, I'm the guy that others often come to when they have a difficult problem they are having trouble solving because I seem to them to usually have the answer, or at least a gut feel that gets them on the right track. To be blunt, I've probably forgotten more about CS than a lot of devs will ever know and it's all just a natural consequence of doing this for so long.

I don't say any of this to try and impress anyone, I really don't... I say it only so that there's some weight behind what I say next:

Almost every day I feel like I'm not good enough. Sometimes, I face a challenge that feels like it might be the one that finally breaks me. I often feel like I don't have a clue what to do next. My head bangs against the wall as much as anyone and I do my fair share of yelling and screaming out of frustration. I beat myself up for every little mistake, and I make plenty.

Imposter syndrome is very real and it never truly goes away no matter what successes you've had and you have to fight the urge to feel shame when things aren't going well because you're not alone in those feelings and they can destroy even the best of us. I suppose the Torvald's and Carmack's of the world possibly don't experience it, but us mere mortals do and we probably always will - at least, I'm still waiting for it to go away!

Remember that what we do is intrinsically hard. What we do is something not everyone can do, contrary to all the "anyone can code" things people do. In some ways, it's unnatural even! Therefore, we shouldn't expect to not face tough days, and being human, the stress of those days gets to us all and causes us to doubt ourselves in a very insidious way.

But, it's okay. You're not alone. Hang in there and go easy on yourself! You'll only ever truly fail if you give up.

Design team: "Is it okay if I put this here?"

Me: "No, it's not okay if you put that there."

Design team: "Are you sure? It'd be really cool if I could put that there."

Me: "No, I will need to fuck with a lot of things if you put that there, just put it in the bootstrap columns."

Design team: "Hold on, lemme see if it's okay to put that there."

Lead-dev: "He's right, you shouldn't put that there."

Company: "We should have a meeting to discuss where the design team can and can't put things."

Lead-dev: "Just put the things in the middle and devide them in these twelve columns on seperate rows, 'kay?"

Company: "Okay, the design team will now put the thing in those things, right design team?"

Design team: "Yes, we agree to putting the thing where we should put the thing."

Me: "So where do you want the thing now?"

Design team: "I want it all the way to the right, outside of the container, that'd look cool."

Me: "Fuck you."

Manager: The thing you working on. We need this now! Like end of the week.

Me: Desirability is not do-ability.

Manager: く( ・◇・)ヾ？

Me: I am still in the middle of figuring out how to do things in the first place, so there are some technologies to research and some problems I yet need to solve. I am in no state to just write down my solution. I don't even have enough information to even estimate how long it is going to take. I am getting there. And yes, I can rush things, but need I remind you that you want solid data as a result that actually means something? As this is *why* this whole project was started. We have some old project doing the exact same thing, but whose output we don't trust. I wonder how that came to be. Additionally, this whole project was on hold for months until I took over. So I neither understand nor accept this sudden sense of urgency. And by the way, you recently added manpower to this project. And adding manpower almost always decreases the productivity in the beginning due to on-boarding and communication overhead. Last Monday, I didn't write a single line of code due to that. So no, this week will not do, as I am also on vacation starting on Thursday that was requested and was approved by you at the beginning of the year. See you in January.

User: We have been dealing with this bug for a month now! How come nobody has fixed it?

Dev: Who did notify about this issue?

User: You’re not listening we have been dealing with this for a MONTH!

Dev: When this issue first occurred did you tell anyone?

User: Yes!

Dev: Who?

User: …. Ok I don’t remember but I know I said something to someone. Anyway it doesn’t matter, your job is IT so how come this isn’t fixed?

Dev: Did you have an email? Ticket number? Teams message? Any record of where this was dropped?

User: I think you’re missing the point. We haven’t been able to do out jobs for A MONTH. We’ve just been sitting around completely helpless. We’ve been trying to figure a system using paper and pencil to replace the electronic one but it’s too complicated. How come this wasn’t fixed the second it happened?

Dev: It’s hard to respond to an issue if it’s not brought to out attention.

User: Ok but we are too busy to create a ticket! We have a million things to do and we can’t do any of them because your app doesn’t work! We’ve been sitting here telling each other how terrible this system is AND IT HAS BEEN A MONTH.

Dev: …. Yeah I got that

A guy is standing on the corner of the street smoking one cigarette after another.

A lady walking by notices him and says
"Hey, don't you know that those things can kill you? I mean, didn't you see the giant warning on the box?"

"That's OK" says the guy, puffing casually "I'm a computer programmer."

"So? What's that got to do with anything?"

"We don't care about warnings. We only care about errors".

Holy fucking shit.

Why do people always expect you to know absolutely everything the second they ask?!

PM: "Yes yes of course we can do that!!! We've done it a million times, we do it for breakfast HAHAHAHAHA"

ME: "Well not really, we've never implemented a solution like that one, its gonna take some time to figure it out"

PM: "HAAAAHAHAHA HE'S SOO FUNNYY LMAOFUDKSJ DONT WORRY WELL HAVE IT READY FOR TOMMORROW :P".

Holy fuuuck I understand you wanna make the sell but you need to give the costumer a realistic look at things, at least give a reasonable deadline for what he's asking! FFS ASK ME HOW COMPLICATED ARE THE THINGS HES ASKING FOR BEFORE TELLING HIM WHEN THEY'RE GONNA BE READY! MAKE A FUCKING ESTIMATE, WE'RE SUPPOSED TO BE A TEAM!

Oh and this rant is gonna happen, dont care if I get fired.This needs to change.

Boss asks me to prefer deadlines over good engineering practice. Says meeting a deadline is always more important than building things the right way.

Son, when the company goes out of business due to hundreds of millions of dollars in losses due to shoddy engineering, do you want to be the one to go to the spouses of everyone who lost their job and say "your spouse lost his job because we didn't take a few more days to build the product right"?

Son, when the company's product blows up in a child's face like a Note 7 because of your shoddy engineering, do you want to go to the funeral and tell the parents "your child died because we didn't take a few more days to build the product right"?

Fuck your arbitrary deadlines. I prefer not allowing for so much grief and suffering to be on my soul.

At my old company one of my colleagues introduced async / await into our csharp code. He created interfaces and showed us a great structuring of his code. Sadly a few weeks later he left the company, because of personal reasons and a bug appeared in his written service. Our senior developer took the issue and complained for like 1 week. That you can't find anything, that interfaces are useless, that async / await is slow and sucks and that we should stop trying to bring new structures into the code base and do things the old way. In the end he deleted all the great things that my colleague introduced and wrote bad and smelly code.

Just discovered that one of my coworkers(well...my boss really) has the uncanny ability to detect fonts and sizes with extreme accuracy.

For some of you that may be not impressive at all and some can probably do it too. But its like...not only on websites man...she can do it on things that we see printed, menus and stuff.

That to me at least is very impressive.

Interviewer: Do you have created any android application before?

Dev: I just built an application to increase, farming production to help farmers earn some more money. It's less profitable but makes farmers better.

Interviewer: That's so stupid. Do you know Jeff Bezos?

Dev: yes

Interviewer: we need someone like that level of visionary to make money for our company. Sorry, we don't think you can make apps that makes people do stupid things for fame.

Dev: Do you know Nicola Tesla

Interviewer : yes

Dev: Well he should have pulled the plug long ago.

Getting annoyed by the framework made by school which we had to use. We werent allowed to use Laravel or other frameworks.

What did I do with a classmate, we expanded on the schools framework. Added a templating engine, improved routing, made a query builder and a few other things before startimg the real project. 4 weeks of building the framework to build the application in a day.
Where others were still using the schools framework were strugglimg and not able to make it.

why in 2019, are browsers so fucking inconsistant.
im not even doing anything stupidly complicated.

simple UL List conataining links and background colors on the LI's....

and yet, every single browser is different, or in IE's case completly lost the plot.

I was recently hired as a lead devops to a giant shit show. The CTO said he needs someone to do things correctly instead of quickly. This is a conversation I just had this morning

HR: We want you to interview a potential new DevOps engineer
ME: okay, when?
HR: Tomorrow
ME: I won't be able to create interview tests and materials for tomorrow. How's next week
HR: This hire is urgent! It has to be tomorrow
ME: Then you'll have to do the interview without me
HR: We need you to interview them because we've had a few bad hires in the past that we don't want to repeat
ME: The best way to filter out bad hires is with technical tests, which will take time to develop. I can be ready by next week.
HR: We can't give you a weeks notice for each hire, we are in urgent need for more devops.
ME: ...

One of my best mentors was my father!

When i was very, very young (like 8 years old), he brought a new computer from his work! The first thing he did was play Doom (lol) but later, he always tried to show me all the things that could be done, coding in VB6.

He always told me: "You can use this to make the computer do what you want to do! You can do many things!". Even if at that time I did not understand much, he always tried to explain me how to develop a calculator or even a "Hello World" but with the name of my mother.

I will never forget his face of happiness, when I simulated a face that blinked with a counter. I do not even remember how I did it, but he hugged me so hard lol.

A couple of years ago, he was the first to try my first application on Android: An application that screamed when you shook the phone lol. He laughed a lot with that application.

He helped me in my university and we even developed several solutions together for different companies. Now we work separately, but he was an important part of what I am now.

PS: My english is kinda rusty, so forgive me ><.

Do you have a spare usb phone cable?
I have but I'm using it to charge my phone

Do you have a spare laser pointer for my presentation?
Sorry, I don't

Do you have a spare mouse?
No :)

Sometimes things become a little weird

Do you have a spare keyboard?
No sorry. :/

Do you have a spare monitor?
:/

Do you have a spare computer?
what?

Do you have a spare mac?
>:(

Do you have two spare computers and one printer for each? Would be nice for the conference that we are going to hold tomorrow if someone need to print.
What's wrong with you people. I'm just a developer, not a fucking warehouse

Just last month we finished a big project for a client. The company had their lawyers make a contract to transfer ownership for the website to them.

One of the requirements was to deliver all code in a word file. And just that. In the whole contract was not a word about transfering the production environment to their servers. Or supplying a working version. The files and database. No just the word file.

As of today still wondering what they where planning to do with a word file with hunderds of pages of code.

Offcourse we deliverd a working version to their servers. But why are there people making decisions about things they understand nothing at all.

My team are the best coworkers I've had. Admittedly I'm only 4 years into my professional career, but my team makes me stay with my current job.

My team do a lot of silly things to keep everyone in a good mood, and stress free. This week we've had a game where in a quote moment you just yell the name of a primitive type (like BOOL). Why? No idea, but we're enjoying it.

We also have a chicken hat that we named Barry. He sits with people on their desk to do code reviews and such. When people leave they get their own Barry to take with them to their new job. We introduce people to him as a regular member of the team.

Sometimes work sucks. Being a developer can be hard, and can be stressful. Working with this team makes it worth it.

So i've been put in charge of bringing the devs together to form a small dev team, instead of having 3 separate devs (including me) sitting apart on separate projects. The idea was to have us talk more, work together more, learn more about the other projects, reuse more code etc.

(I've been arguing to let us do this for a while)

So I asked my manager could we move to the 4 desks in the corner, so we can have our own space, talk without having to book a meeting room each time etc. Its also a bit quieter over there and we all really need that in our noisy office.

Manager sent me an IM today while I was working from home to tell me we can have the desks. Was super happy, messaged the devs to tell them they can start moving.

Just got a message from one of them to say our manager has started moving his stuff over too. Seems he agreed with me that it is quieter over there and he doesn't like the noise either ... so he's joining us.

A huge part of the move was us wanting to work on side projects to automate and speed up various things in the team, that he has been against. We know we can make huge improvements but he doesn't see it. He's only interested in Word, Excel and Powerpoint.

So now we have our space, and anytime we try to work on something we are actually interested in, we'll have a little voice in the corner to pop up and point out what other things he deems more important and tell us to stop wasting our time.

Pretty fucking annoyed to be so happy and then get shot down like that. Happy weekend everyone!!

Manager: Why are we missing our deadlines?

Me: Cause we don't own any of the codebase that we work on and have to literally beg to other team for code reviews and deployments, for which it takes long mail chains and meetings. An even before that we(devs) have to explain to them what/why are we doing things, because our Product managers are a bunch of NoGood AHoles. And after all that we finally do some development, in whatever measly time we have left.

Manager: I know all that, tell me why are we missing our deadlines?

Already existing website, I was asked to do a few things to redo. Code is a mess, 0 comments, oldschool technology. Completely static html site of a small company, nothing extreme.

Client: okay, could you please add 2 more items to the navbar for the 2 new pages?
Me: yes, here they are. Since it was already full, font size had to shrink.
Client: it's okay

>> Fast forward 2 weeks, full of similarly easy modifications.

Client: could you make the font size of the navbar larger?
Me: not really, we will lose responsivity
Client: do it anyway!

>> Fast forward to next day
Client calls me that it is urgent to 'do something immediately' with the navbar because it is broken and I am a 'horrible webdesigner' for making a mess of her website. I was told that it is not her job to make it good look and that I should 'use my eyes better'.

After 2 minutes of a lecture on webdesign she let me tell her how a responsive website should look like and to achieve that we should better restart the whole website. At that point I was the idiot who just wants to get more money and that I won't be able to do that since I am already unable to finish these few tiny things she asked for.

I get really tired of people shitting on php and getting greated with immediate laughter when I say I work as a full stack LEMP/LAMP dev. I work just as hard as you (ruby/python/node devs) do and feel like I make some pretty cool shit.

Why can't we all just agree we do great things with our tools and while I may use a different hammer than you, we still use the same nails!!!

Start-up: hires 3 junior devs to save money.

Start-up: expects things to get done faster-- BUT-- Start-up keeps adding things to the TO-DO list and backlog-- i.e. it's all relative!!

Start-up: gets angry at 3 junior devs why they can't deliver when they keep adding tasks and ask we fall behind.

Dev team: "Seriously? You hire more devs to finish tasks faster, but you keep adding more than are being finiahed-- obviously it's gonna take longer now regardless"

Git --pull life together

Apparently, part of being a software engineer means knowing how to read minds and do other people's jobs.

While implementing a user story for marketing, we found some associated features that, according to the database, have not been used for years. We tell them this. We do the courtesy of asking, "Hey, is there anything on the site that is utilizing these features? We'd like to clean up the DB."

"We don't know."

Engineering suggests, "Ok, lets turn the feature off, then, and see if anyone complains. It's been years according to the DB."

Marketing gets angry and hostile and says, "That's not the way to do things!"

I don't vocalize, "Well, not knowing how to do your own damned job is not the way to do things."
-
Marketing asks us to integrate a third party feature to the site. We ask, "Ok, what page do you want it on, and what information do you want to collect, and what should it look like?"

"I don't know. You're engineering. You tell us."

We implement it as best we can.

Marketing says, "HEY! This isn't done right! It's missing this and this and this!"

"Did you ask us to implement that? According to the user story, it passes acceptance criteria."

Marketing says, "I thought you would just know that! I didn't know it was a separate thing. Just put it on all the pages, then. You guys really should know the site better."

Engineering gets angry and hostile
-
Marketing says, "We need this removed from the site."

Engineering replies, "We have a GUI for that. Just go to this URL and you can do it yourself."

Marketing replies, "Well, if that's a really complicated thing, can you just run a script against the DB?"

Engineering says, "If we've built a UI for you, we really shouldn't be executing SQL scripts directly against the DB."

Marketing gets angry and hostile.
-
Engineering tries asking nicely.

"Marketing, if you want us to add new stuff to the site, or change stuff, please tell us what it is and where it should go and what the customer experience should be like."

Marketing replies, "We don't know the site that well. We are leaning on you to tell us."

I do not vocalize, all while trying to keep my eyes from bulging out of my head, my face red with rage, "YOU ARE IN CHARGE OF SELLING SHIT ON A WEBSITE THAT YOU KNOW NOTHING ABOUT. YOU ARE ASKING FOR CHANGES TO SOMETHING YOU DON'T EVEN UNDERSTAND. WHAT IS WRONG WITH THIS PICTURE?"

Engineering is angry and hostile.

!rant

I complained during a dev team review about the too many dev calls/meetings we have that are supposed to improve our productivity but instead feel like interrupting our work and line of thoughts when focusing on something.

I expected the team lead to bash me or say "Nooo, these meetings are important bla bla bla" but he received it quite positively and already changed how we do things.

@dfox can we please add an optional 'vote' option in rants? :D It would be fun to check the preferences of people for different things.

e.g. How do you pronounce 'git'?
1. Git
2. Jit

These anti AI type news articles are ridiculous. We are decades away from anything like skynet. People have seen too much fiction. Everyone used to dream of flying cars, did that happen? No. Do not be fooled, machines can do clever things but they are no where near becoming sentient beings. You try and build something that has the same IQ of a dog and it will still require a shit ton of power and hardware. Plus as far as I'm aware dogs haven't taken over the planet with their level of intelligence.

At the end of the day machines need power to run and we control the source. If anything futuramas more realistic in how AI/robots will integrate with society than these shit piece newspapers.

"Can you do this?"
Sure, give me the information I need...

"We don't have all of it yet"
So I can't do it then

"Well when can you do it"
When you get the information

"Do you need *all* of it"
Well, it's either I do half a job and waste my time, or get it all done in one shot

"The client wants it tomorrow"
When will we have the information?
"We don't know"
Well they aren't having it tomorrow then, are they...

Sales people... don't care *how* things work, as long as they get a tick against their name to show they've sold something...

Client: "Dear Mr. I still have not received the final version yet. I had planned to send it out to my customers at the end of the week."
-------

Me (1st answer I did not give):
"Ok. I accept your statement as true, since I did not send you anything. Furthermore I respect your wish."

Me (2nd answer I did not give):
"Well I am sorry. Before today you did not once mention that there was a deadline. ASAP is not how I do things. Please do your project management."

Me (answer I gave): "Dear Client, due to a huge demand for our services we are forced to prioritise. We are doing our best to complete the project as fast as possible. Please understand however that we can not reschedule with 3 days notice. Because of technical requirements the product can be send on Friday next week. Please let us know if this works out for you. - Kind regards. Me. "

-__-""""

Client: We are tired of having to go only to specific users to get things actioned, we need everyone to be given admin access so that we can get work done efficiently

Dev: Highly do not recommend that *outlines the likely consequences*.

Client: We don’t care, we DEMAND you do this. We’ll make sure everyone is careful.

Dev: Ok but I warned you. Please submit this request in writing.

Client: Ok, not sure why you would need that. I told you everything would be fine.

*Not even two days later*

Client: HELP!!! OUR DATA IS NOW COMPLETELY MESSED UP. WE HAVE NO IDEA WHAT WOULD HAVE CAUSED THIS IT’S AS IF EVERYONE IS RANDOMLY DOING WHATEVER THEY WANT HOWEVER THEY WANT IN ORDER TO SUITE THEIR OWN NEEDS. IT MAKES NO SENSE HOW THIS HAS OCCURRED. I TOLD EVERYONE SPECIFICALLY TO NOT CAUSE ISSUES!!! WE NEED THIS FIXED A.S.A.P!!!!!!

Dev: …

As devs we like to complain about our jobs. But I just want to take a moment and acknowledge how truly amazing writing software is. Nothing else has given me so much joy and happiness. The endless stream of new things to learn, the elusive art of clean code, and deep understanding of systems required for architecture. There is so much depth to this career we have all chosen and I hope you guys love it just as much as I do.

Me: "We should do X!"
Client: "I think Y would be better."
Me: "If you're sure..."
Client: "I'm the one paying you!"

*much development time passes*

Client: "We should do X. Isn't it your job to think of these things?"
Me: "..."

I can get absolutely dead pissed by the fact that a FUCKING 1800 euro laptop can't do a fucking basic thing like connecting to a bloody WiFi ap?

so why, you wonder? oh no, the problem isn't the fucking hardware. IT'S THIS DEAD BEAT PIECE OF SHIT CALLED WINDOWS. mfw when it runs fine under Linux, BUT WE CANT HAVE NICE THINGS CAN WE ADOBE?!?

Hey junior... when I'm asking a question it's not the answer I'm looking for.... It's your thought process! Just tell me the things you will not do and we can take it from there!

Dev: (Watches user print out screenshot of maintenance app to do list, walk across facility to printer. walk across facility to equipment and check things off on paper, then walk across facility back to their terminal and copy the findings over.)

Dev: We made the app responsive so they could do that on a mobile device. Why are they printing?

Manager: Printers are cheaper than getting more tablets.

Dev: …

Dev: Can we at least get a printer at each terminal so they don’t waste so much time walking across the facility?

Manager: That’s too many printers to maintain. It’s easier to just have one.

Dev: …

* Initial Interview*

HR: We do offer remote job, lots of benefits and annual increase of salary.

Supervisor: "Oh... Those things HR mentioned? That's just a lie. We're just complying on the government requirements"

Boss: do you remember the other team? we need to fix one of their bugs

Me: amm, okey np

Boss: do it when you have time, but don’t forget to finish your things first.. and we need that fix by the end of the day.

Me: //what a beautiful monday <3

I honestly don't get too mad when people aks me to do things like install programs for them. This is not my dayjob, but when you think of it, they're right when they say "you are a programmer so you must know how to do that". We do know how to do that. When you have a question about plants and you know a farmer, you are going to ask the farmer, even though he is not a gardener. He will know. Just as we know how to use computers very well.

Every year my team have an award ceremony for stupid things we do throughout the year. There is only really one worth highlighting this year
Alzheimer’s award- given to one of our DBAs for this svn commit message: “updated the comment block but forgot to make the code change”

Easy. Was creating a website for a client and they asked if we could add "those, what do you call them? Yeah cliparts" to the website.

Cliparts? Really? Those silly cartoon things from MS Office?

pm: why this things are getting late in development.
me: no, I'm not late, on track, this will be done by end of the next week.
pm: but my estimation was for today EOD.
me: you never asked me for the estimation..
pm: we are here for that.
me: then do this yourself..*asshole*

"I have nothing to hide."

I admit, I did utter these disgraceful words once. But I now take privacy seriously.

What is really sad and potentially dangerous is the fact that younger people do not give a fuck about privacy. Snapchat, Facebook, Instagram - these people use these apps and do not pay ANY attention to what might be the consequences of their actions.

The more data they own, the more they own you. We should start a privacy basics course in high school. Things could get out of hand in the future, as if they already aren't.

A guy is standing on the corner of the street smoking one cigarette after another.

 A lady walking by notices him and says

"Hey, don't you know that those things can kill you? I mean, didn't you see the giant warning on the box?!"
"That's OK" says the guy, puffing casually "I'm a computer programmer"
"So? What's that got to do with anything?"
"We don't care about warnings. We only care about errors."

Manager: We have a new equity survey from HR that is ABSOLUTELY MANDATORY. Anyone who doesn’t fill it out will be severely reprimanded for being against diversity in the workplace. We need this data in order to ensure we have the ABSOLUTELY EXACT ratio of EVERY minority so that we can show the people that we do not discriminate against ANYBODY for ANYTHING. One of the problems with hiring new people is that most people we want to hire turn out to be white and we are absolutely not allowed to hire any more white people because we are over the quota for white people. Now there’s a loophole to this, if that white person belongs to some sub-minority like they are muslim or gay or something like that it’s totally cool and we can show people we don’t discriminate on these things when making employment decisions!

Dev: That’s…not wh—

Mandatory Survey: Please select your sexual preferences and/or religion from the dropdown below.

Dev: jesus christ.

Our boss has a camera in the office to "monitor" us, the developers.
He tries to monitor our movements and record the things we say.

I'm curious, do other people do this?
I find it annoying.

When you spend a few days getting a monolithic LAMP app working in Docker so we don’t have to follow a 12 page install procedure... only to have your senior say “that’s not the way we do things around here”

Is the software at your company so bad that it's a miracle that anything works?

Does it feel like this colossal pile of broken electronics from the past 30 years duct taped together and patched with multiple tiers of adapters, wires spliced together with scotch tape, and someone on stand by with a fire extinguisher?

Do you feel like getting your product to work is like how we used to get things to work back in the eighties? Not just turning things off and on again, but things like hitting the tv to make it work again, blowing into cartridges, and the feeling of pulling on the starting cord on a gas powered mower over and over again to no avail?

That is exactly what my company's codebase is. A huge amorphous, heterogenous pile of shit that somehow works and occasionally has to be massaged to make it work again. Fuck my life.

PersonX: Dude, I hate coding in Java. Wish we could do things in python for this project.
Me: welcome to the inner circle my friend.

*After taking a look at his python skills*

Me: I'm going to freaking kill this idiot using his own company provided laptop.

during code review...
peer: "you should pass this variable, and extract the logger from it"
me: "why? it is a 3 line logging function. why not pass the logger instance?"
peer: "because that is our best practice. It is the way we do things"
me: "why is it a best practice?"
peer: "because it is. We use it everywhere!"
me: "No we don't. And I still don't understand why is this a best practice. can you explain?"
peer: gives ups, did not look at the mr, and was not going to.

mr stays open. probably forever.

First time in years that I've hugged my best friend. Felt weird and we got really confused looks from the others (class full of boys n shit), but we were so happy because we both got a really good grade on an important test!

Why isn't this a common things men do!? We should all hug more 🤗

boss: we should map all the possible ways to do things in the system so we can test them and make sure we fix the bugs.

Me: yeah, well, that is exactly what automated tests are for, every time we find a non-mapped way that breaks this we make a test out of it and fix, this ways we end up mapping the majority of ways.

Boss: yeah,yeah ... Let's sit down latter and map everything on a document.

I bet my ass we are never gonna have tests as a part of our workflow.

Coolest thing I’ve built solo?

Damn, there’s been a lot of things over the years, but I guess the most used one I’ve made would be my voice activated tv remote - yes it’s real.

So in essence it’s a google home... yea I know spyware and all, but look it was free so I’m going to make use of it... err where was I, oh yea.

An IFTTT account which taps into the google assistant API and creates a webhook, although the authentication side of things is 0 to none, so had to put a api-key into the requests to at least have some layer of auth.

This webhook then hits a raspberry pi containing a PHP API to accept and authenticate the request in, digest this into KEY commands for the TV, and drops this into a Python script to connect to the TV over a web socket connection ( I found python more stable for this ) and sends the pre made key requests, it can even do multiple keys at a time... that was a pain.

So after all that, the end game becomes about a second from saying “hey google, change the tv channel to xxx”

This sick and twisted contraption is finished and the tv is my little bitch.

This has been built out to handle channels by name, number, volume up/down, sources switching to hdmi, tv, vga and a bunch of other things.

The things we do when we can’t find a tv remote for days....

Next up, getting it to launch Netflix app and going to a specified show / episode.. but may be to adventurous.

System design meeting with the client.

Client: We need feature X in the design document
Me: But feature X was not a requirement, so it's not in the document and we will not add it.
Client: But feature X should be a common feature today.
Me: That doesn't matter, it wasn't a requirement. And besides that you don't even need it today, the planned system doesn't even support feature X, so we couldn't implement it, even if it was mentioned in the design document.
Client: But we may need it some day, and what do you do, when we decide to enhance the system in a few years and we need that feature then?
Me: Then we make you an offer for feature X.
Inner me: You ordered a bicyle and now you want it converted into a delivery truck next year without charge. That's not how things work.

It's my first 'rant' so be kind :P

When I started my studies a already knew some very basic programming stuff. I went to the exercises with another dude I met. We always joked about the tasks we had to do and did other things while the others tried to fix bugs in their code. After the semester ended he asked me whether I want to work part time at his mother's office. I went to the interview which was weird because I have never been to one before but got the job straight away. I'm in my fourth year of working there because the team is awesome.

I’ve been programming for 20 years now. My friends and family never really understood what I did back in the days. And they still don’t.
All they saw was a kid who was good with computers. Your friendly neighborhood tech guy who would take a look at your computer for free.
I’m sure most of you have been in the same situation.

When people ask me what I do for a living. I’d just say “something with computers”. Because most of the time they will ask me to look at their computers and I’d reply with “oh that’s not what I do”.

When I was younger, I’d try to explain what I actually do for a living. To really tell people the problems we as a programmer solves on a daily basis or the things we create. That’s really hard to explain to “common” people.

So whenever someone asks me what I do for a living? It’s always something with computers ;)

Client: Too many of our business processes take place on excel and paper! We need to modernize our business processes. Build an app that can do the main things we do with excel and paper in app form.

Dev (4 months later): Here it is

Client: Ok some of our users want to still use excel and paper so build the ability to print the app and export/import to excel so they can continue working the way they always have alongside our new app.

Dev: …

My coworker doesn't know how to use a terminal. He talked himself into his position and instead of taking the time to learn about the basic commands he keeps asking someone else (including the teammanager, who's actually a software engineer) to do things for him.
For reference; we need the terminal to tail log files, keep track of processes, cron jobs, manipulate file structures, use scp (I use sshfs) to move things between other workstations and servers etc. Being able to use a terminal is one of the basic requirements for our job.

What.
Why.
How.

Why do people do this?

Me: okay brain! We had our morning coffee. We're ready to work. Lots of things to do today.

Brain: yay! I feel unstoppable! Can't wait for logic problems and amazing things we're going to build! What's the plan?

Me: great! Today we're going to work on the ios implementation of our app. Where should we start?

Brain: ...

Me: brain?

So, my boss was angry at me today because...
1. "Why are we taking so long to finish the software?". We started coding in March, and during that time I kept asking for requirements, design and his answer was, "You build it and we'll see." . During that time, after creating the system with only three type of user modes, he was like "Oh, I want customized user permissions." Took me 1 month to come up with a design, implementation for everything. Also during these months, nearly 2 months was wasted because he kept giving me other things to do, and I was not focusing in my current project.

Today he was mad because he expect me not only to build the infrastructure, setup servers, write backend code, do QA etc, He wants me to be a product designer. A fucking product designer. My answer to him was "If you refuse to help with designing the UX, either hire someone or I will just copy/paste things for internet. If the UI works, there's where my job is done."

Fucking hell. Not only I am being under payed, but he expects do to the job of 5 other people. Fuck this shit.

Hope this is not a repost

A guy is standing on the corner of the street smoking one cigarette after another. A lady walking by notices him and says
"Hey, don't you know that those things can kill you? I mean, didn't you see the giant warning on the box?!"
"That's OK" says the guy, puffing casually "I'm a computer programmer"
"So? What's that got to do with anything?"
"We don't care about warnings. We only care about errors."

😂😂😂😂😂

Is it done yet?

Stop micromanaging! We are providing updates every morning, what difference does it make to ask for the update in the evening?!? Don't think no one can see that all you are asking is "is it done yet?"

Like a small child who does not understand the concepts of travel yet, you won't understand why "such a small change" takes so long. It's because we are scooping all the crap, patched by assholes who cared only to please you and did not had the courage to say no to your pressure and do things smart way.

If you think it is necessary to keep reminding everyone to do their job - then you you do not belong in IT.

So lets see if i can get this devrant stuff right.

So a couple of years ago i worked for this company, where i worked in datawarehousing and business intelligence. I was in my 3rd year of working as a software engineer and was full of ideas, motivation and just wanted to do cool stuff.

Anyway, after the first couple of months of working where i learned what they actually wanted to achieve, i got some ideas on how to improve the workflow. They were just simple things, like updating our IDE (we were working with a very old Visual Studio version), getting useful editors, using some more modern ideoms like unittests, continous integration, etc. Simple stuff really.

So in my endless naiveness i went to my supervisor and told him my ideas. He was not particularly interested in my ideas and cut me off somewhere in the middle and said that he would talk to his boss.

So a couple of weeks after that (nothing happened), i went to him again and asked about it.
M:" Hey Bossman, have you thought about my ideas?"
B:"Yes."
M:"And?"
B:"We won't do them."
M:"None of them?"
B:"No."

So at this point i was a bit bummed out, but surely he has a good reason right? So i asked why.

M:"Why?"
B:"Well, because we always have done it the way we do it now."

I think i had a bit of a blank stare at that point, because he looked at me funny. If we would do things like we always have done them, we would be still in the stone age you moron.

God i hate it when people say stuff like that.

Worst things about being a dev? Boy, this will be a long one!
- Whatever I do, be it hard work or smart work, I feel I am always underpaid.

- Most people who don't know tech feel my job shouldn't take that long. "Oh, a website that should be easy." "Oh, REST services, that's cute!"

- Most people who know a little tech will be like, "Here is the code for this on Google, then why are you charging this much"

- Companies like Microsoft and Apple who are too cool to follow standards.

- Always underpaid!

- The friggin compilers and random environment vars. Sometimes you make no change and the code works on a restart. I mean wtf!

- Having to give/meet deadlines, when we know most of the times things get out of control.

- Having to work for jerks mostly who don't know squat, and can't tell the difference between a CPU and a Wooden box.

- Sometimes I wanna take a break from my laptop(traveling and stuff) , those are the times I get the maximum work load!

- Did I mention we are always underpaid?

- Because of the kind of work I do, finding a girl has been challenging. Where the heck are they!

- We have to stay always updated. Often we deploy something using a framework and the next day we see an update.

- Speaking of updates, I hate having to support for OSes like Microsoft.

- Speaking of OSes, I hate Apple!

- Speaking of Apple, I feel we are underpaid, de javu?
...
How much would you hate me if I wrote "just kidding" ?

Boyfriend just got rejected after spending 45 minutes annotating a video using a company's shitty product they asked him to learn and utilize for the interview itself.

He did a fine job, if I do say so myself.

He was rejected today, with no reason other than a list of "common things that might have triggered a rejection".

Oh and the classic "we're sorry, we can't tell you why we rejected you - but we look forward to you re-applying in 45 days!"

Why the fuck not? If you're a recruiter and you do this shit, go royally fuck yourself. It's so beyond unprofessional and there's zero reason for it.

If he fucked up and failed, fine. At least tell him why. Be fucking adults. Your shit fucking stinks just like everyone else's, this isn't American Idol or the Hunger Games; you're not President Snow, and even Simon will tell you why you suck.

Fucking aggravating.

A discussion about writing tests for frontend applications.

Context: my frontend coworkers don't write tests, at all. Yeah, really. Our testing process is very manual. We test manually when developing. We test manually when reviewing code. After merging, the application is deployed to a staging server and the design team does a QA Sprint. Lots of manual testing and some bugs still crawl by.

So I decided to start pushing my coworkers to start writing tests. One of the reasons I constantly hear them say to not write tests in the frontend is: "It's not worth the time, because design keeps changing, which means we have to take time to fix the tests. Time that we usually don't have."

I've been thinking about this a lot and it seems to me that this is more related to bad tests than to tests in general.

Tests should not break with design changes (small changes at least). They should test funcionality, not how things look. A form should not break if the submit button's style changes, so why should its tests fail? I also think that tests help save time, as they prevent some back and forth because of bugs.

Writing good tests is the hard part. Tests that cover what's really important and aren't frail and break with things that shouldn't break them. What (and how) should we test? And what shouldn't be tested?

Writing them fast is another hard thing. Are you doing it right if they take more time to write than the actual code?

What do you think about this? Do you write tests for your frontend applications? What do you test? How much time do you spend writing tests? What are your testing tools/frameworks?

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

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

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

Manager in December: Things will pick up soon!
January: I know things are slow, but they’ll pick up!
February: Just give it a couple months!
March: Things are about to pick up, trust me!

All the while I have been twiddling my fucking thumbs with probably half a day’s work to do, either working on my own studies/projects or just wasting time.

And the reason? Because Manager hasn’t been able to decide the budget for the project, so we haven’t been allowed to begin.

We are asked to waste time rather than use it effectively because of a spreadsheet that Manager has been putting off for four months.

Dissatisfaction is the understatement of the year. Some say I complain about a good thing, meaning less work, same pay, but that’s not why I applied to this company.

A fucking year and a half of project that could have been 2 months if properly planned...

But every 1 month deadline is a rush to "just do it and we plan latter when stablished"... I wait 2 weeks for things to be approved so they can be changed after I fucking implement it.

Now everything is a mess that I just introduce more mess to move on and go home by the end of the day.

TL;DR you suck, I suck and everybody sucks, deal with it....

------------------------------------

Let me let off some steam, since I've had enough of people hating on languages "just because"

Every language has it's drawbacks and quirks, BUT they have their strengths also. Saying "I hate {language}" is just you being and ignorant prick and probably your head is so far up your ass that you look like an ass hat. With that being said, every language is either good or bad depending on the developer writing in it. Let's give you an example:

If I ware to give you a brick and ask you to put a nail in a plank, can you do it? Yes, it will be easier if you do it with a hammer, but you have a brick, so hammer is out of the question. If you hit your thumb while doing it... well... sorry, but it is not the bricks fault - it is YOU!

JavaScript, yes it has a whole lot of problems, but it works, you can do a ton of stuff and does a good job at that, it is evolving through node and typescript (and others, just a personal pref), BUT if you used js when you ware debugging that jquery (1.0) plugin written in the free time of a 13 yo, who copy pasted a bunch from SO, well, it is not js' problem - deal with it. Same goes for PHP, i've been there where you had a single `index.php` with bazillion lines of code, did a bunch of eval and it was called MVC, but it also is evolving.. thing is all languages allow you to do some dumb stuff so YOU have to be responsible to not fuck it up (which you always DO btw, we all do). Difference is PHP/JS roll with it because the assumption is that you know what you are doing, which again - newsflash - you don't.

More or less I would blame that shit on businesses which decided to go with undergrads to save money instead of investing in their product, hell, I am in a major company that does not invest that doesn't care a whole lot about dev /tech stuff and now everybody's mother is an engineer - they care about money, because investors care about money (ROI) and because clean code does not pay the bills, but money does.

If we get all of the good practices and apply them to each language every one of them has it's place, that is why there is no "The Language", even if there was, we STILL ware going to fuck it up and probably it was going to be even worse than where we are now.

Study, improve, rinse and repeat... There are SENIORS and LEADS out there that are about 25-30 and have no fucking clue about the language, because they have stuck up their heads up the ass of frameworks and refuse to take a breath of clean air and consider something different than their dogmatic framework "way" of doing things.. That is the result you are seeing. Let me give you a fresh example to illustrate where I am at atm:

Le me works with ZendFramework 2.3-2.5 (why not, which is PHP5+ running on PHP7 [fancy, eh]), and little me writes a module for said project, and tries to contain it in its own space, i.e not touching anything outside of the folder of the module so it is SELF-CONTAINED (see, practices), during 2-3-4 iterations of code review, I've had to modify 4 different modules with `if (somthing === self::SOMETHING_TYPE)` as requested by my TL, which resulted in me not covering 3 use-cases after the changes and not adding a new event (the fw is event-driven, cuz.. reasons) so I have to use a bunch of ifs in the code, to check a config value and do shit. That is the way of I am asked to do things I hate what I've done and the fact that because of CR I have lost case-coverage, a week of work and the same TL will be on my ass on monday that things are now "perfect".

The biggest things is "we care about convention and code style"... right.... That is not because of the language, not because of me, not because of the framework - it is some dude's opinion that you hate, not the language.

New stuff are better, reinventing the wheel is also good, if it wasn't you would've had a few stone circular things on your car and things ware going to be like that - we need to try and try, that is the only way we actually learn shit.

Until things change in the trade, we will be on the same boat, complaining about the same shit over and over, you and me won't be alive probably but things will not change a bit.

We live in a place where state is considered good, god objects necessary (can you believe it, I've got kudos for using the term 'God Object'... yep, let that sink in). If you really hate something, please, oh god I beg you, show me how you will do it better and I will shake your hand and buy you a beer, but until then, please keep your ass-hurt fanboy opinion to your self, no one gives a shit about what you think, we will die and the world will not notice...

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!

So we have Oncall system. Every month I get one working weekend.

Now senior engineers and lead are assholes. They think they can bully us. They are putting their Oncall work on our heads.

I refused to do it. But my partner in Oncall agreed to take up their weekend Oncall and in return they would do our weekday. I don't see how that is fair enough.

I refused to do it still. My partner apparently ended up doing it alone this weekend.

I don't FUCKING need to lick anyone's ass here! I don't FUCKING need to do these things to be in their good books! Waiting for the time when I saw GOODBYE TO THESE FUCKING ASSHOLEZZZZ

We have a 45year old junior that is left to his own devices. He simultaneously wants help all the time and won't listen to the answers. He also wants help but doesn't want to redo things he's fucked. He wants to finish tasks but not write tests in case it shows problems and he has to do more work.

The worst thing is he wants to get work done but cba to learn the framework, language, tools he's using, or just the feature of the framework he is literally using for his task. He just fumbles about like a blind man in a strip joint until things 'work'.

A project I'm working on uses Elastic for internal monitoring and logs. The customer asked to access those logs - not something we'd normally do, but it's isolated from other things we use and there's no critical data there, so what the heck, let them have it.

Ever since, we're getting tons of questions like "There are tons of [insert random info message] all the time, do you have any plans to resolve them?" and it gets to the point where I'm just about ready to scream back "NO, SUZAN, BOOKING NOT COMPLETED MANS THE USER F###ING CANCELLED IT, IT'S NOT SOMETHING I CAN FIX IN THE CODE"

Edit: the customer's name isn't actually Suzan

I can't even deal with this. We just deployed a new update to our system, and everything was going smoothly. And then, out of nowhere, we started getting a bunch of error messages and user complaints.

Why do these things always happen? We spent hours trying to figure out the source of the problem, and it turns out it was because we didn't do enough testing before the deployment. Are you kidding me?

I know that testing can be time-consuming, but seriously, this is ridiculous. It's frustrating when something like this happens, especially when we're under a tight deadline. And to make matters worse, we had to roll back the deployment and start all over again. I just want to throw my computer out the window.

Uuuugghhh!

I've been a part of this industry for over two decades, found myself scraping and clawing my way up, recently leaving a high paying position to create my own company; in an attempt to fix the things I feel are severely broken within the ones I've worked for in the past.

Sometimes, we are challenged in ways we never thought we would be. And, it should always result in the improvement of something we never thought would be possible to improve.

There's a certain beauty of hitting a personal impasse. Because it allows you to choose a better path for yourself - which is a key element in accepting and conquering any one of life's many challenges.

So, just remember, we are - by nature - problem solvers. So what the fuck would we do, without a problem to solve?

We work in an office where we must lock our computer screens because our screens may have confidential information on them, plus you could do things as the person without taking any blame (ie sending an email).
Anyways anytime someone forgets to lock their screen we always prank them pretty hard. The greatest thing we ever did was in our latest release we had our managers buy us drinks at the pub. Well our managers left to go to the pub and one of them forgot to lock their computers. So we downloaded an image of the blue screen of death and made it full screen, unplugged his mouse and keyboard for added effect, and locked his computer. He came in the next Monday and couldn't log in because his keyboard wouldn't work. He actually called IT to bring him a new keyboard and mouse... then he unlocked his computer and freaked out with the IT guy because there was the blue screen of death. Needless to say he got a brand new computer as well as a new mouse and keyboard.

I'd call it a win win?

> worst coding procrastination story

worst and best at the same time:

If you wait long enough things might resolve themselves.

My team inherited an ancient site. Hosted on an old host that the org wanted to kill, using an old log service the org wanted to kill.

A ticket was written in 2021 to migrate that site's hosting and logging to the new services our org started using.

My team kept avoiding it since it was a cheap unimportant site.

in 2023 we were about to finally take action - then we hear "Turns out the new hosting platform and logging platform are way too expensive - I know all of you have migrated to these new services but you gotta revert and go back the old ones til we figure this out"

We didn't have to do squat.

Problem solved by procrastinating ✅

Start-ups and corporations trying new things be like:
"Why should we pay a developer or a company to develop this and this for us when we can just:
- start a competition.
- get free design mockups and code.
- decide which is better.
- reward a small prize and maybe some freebies to the competitors.
- profit. FREE CHEAP CODE AND DESIGNS!!!"

It might be the reasonable and logical thing to do from a business standpoint if its about code you need to rarely maintain..

But from an independent developer viewpoint - FUCK YOU AND THE SLOW ENSLAVEMENT OF MY SPECIE!!!

Biggest thing that pisses me off about windows 10 is the fact that they do not give two shits about wasting your internet, and they try to hide everything in obscure split settings, set updates to happen at a specific time sure but did your dumb ass remember to disable downloading app updates in the store? Probably not.

Heck how about we preload apps for you because you are on mobile aren't you, we know it is a desktop but we would really love to be the next android so here you go have apps all the apps.

Instead of being the foundation for things you actually intend to install we want to also give you a sample fucking 200 level tower that will take forever to demolish so you can start building the cozy cottage you do want.

I am digressing , but final thought is just that Windows can be a 1gb install since the rest of the shit is what fucktards that use a Samsung S8 just to facebook want.

Plebs.

WK289 Playing automation games like factorio, heavily modded Minecraft, satisfactory, etc, let's me do all the things that I want to do in my job but we simply don't have the time or resources for. It makes me a better engineer because I'm less frustrated during my day job.

Simple there are four other developers on my team. Yet, I do all of the work.

I'm picky about spesific tasks, so I would rather do THOSE by myself, by we have a Trello board where I've marked the tasks I want to do myself, and everything else is open for grabs.

Some tasks I will asign others (one developer specifically) and days will pass and no code gets touched. So I end up having to take it over. :|

Like, guys, I get it. You have other things to do. But could you atleast *try* and help me without me having to ask? If not, then why did you even sign up? I want to get this out the door so our project doesn't go under and we can make some money. I have other things I would like to do as well, you know. Like take a day off, or spend time with my girlfriend.

Senior developer just showed me a "competitor" that seems to do things waaaaaaaaaaaaay better than us on his web site and was telling me:

Senior: damn, I wish I could figure out how they do this. I've been trying for so long...

I write the URL on chrome with dev tools open and literally the first thing that comes on the console is a nice greeting from their devs with links to they github repositories, ends up they are open source...

And now I'm here thinking "WTF!!!! WHY ARE WE NOT DOING THINGS THIS WAY?"

The first two stories on slashdot's homepage are:
1. Google releases Angular 2, breaks backwards compatibility
2. Apple releases Swift 3, breaks backwards compatibility

If you use either of those tools, why do you put up with this? When did software engineering stop being about building useful or enjoyable things for our customers, and start being about doing thankless make-work for Silicon Valley billionaire companies? Is this the legacy we want to leave to the world?

Sat down with the Project Management team today to discuss a signage installation. This is how the conversation went...

Me: Right, so we need to get the hardware on-site asap so we can get this configured before it goes over to the production guys to have the facisa installed.
Them: That's fine we have plenty of time. Stop rushing things.
Me: Okay, so do we have the story board in place ready for development?
Them: Nope. Hasn't been done by the designer yet because he is in a bad mood.
Me: Okay so when does the client want this?
Them: 3 Weeks' time
Me: But it is atleast a week of dev time?
Them: Sure. But you can work late if needed...right?

This is a typical conversation between them and me. I'm the sole developer here. So done with today.

Fucking hate when business people says this to me:
- You have no time to do this, we will find somebody else to do it. (EXCUSE ME? how do you know I have no time? If have no time I WILL TELL YOU)
- Your team is too busy, we will outsource that (IF THAT it's a priority, we WILL DO THAT, fuck you, I'll tell you if we need to outsource or not)
- Requirements are too complex to do now. We will think about it and we will tell you, maybe it's just enough to add a column to db (WHAT? WHAT THE FUCK IS too complex? I didn't even see anything we can call requirement, nor speak with relevant people, so how do you fucking know they are complex if you don't know shit about dev and our platform)

Conclusion
It's true, I have no time, because I don't fucking understand what do you want, so I'm running all day and night doing useless things.

My family (dad, mom and I) runs a software business. Things were going decent when I was in college, and just as I was about to finish college, it went slightly bad due to lack of some technical insight. So I figured, I had the knowledge to do so, and joined in the family business as my first job. When I joined, I found out that things were worse that what I expected, (lack of processes in the company to handle day to day business). But we took a year to fix it and solve issues. But during this year, while the company finally runs as a proper company, we went into some serious debt to keep it running, as we were expecting it to get resolved soon. But now, although the company is structurally fine, the sales have seriously dropped. This has us cornered and we aren't able to do anything. We are seriously considering shutting the company down.

Which is not the worst part. The worst part is the debt. Since I, was a part of the company too, I am equally responsible for paying it off. And now, due to both my parents hitting the retirement age, I will be the only one repaying it. I really don't want to invest an estimated 8-10 years of my life living very modestly and spending a large (70-80%) of my income in repaying this.

I don't even know what to do, and things just seem very hopeless for me. Looking for any advice anyone has.

I guess if I had a bit more experience in the real world, I would be better at dealing with this, but I'm literally just 1 year out of my college.

I'd never do anything "risky" in a prod environment if I considered it so at the time, but in retrospect there's *lots* of things considered risky now (both from a security and good practice viewpoint) that were standard practice not long ago:

- Not using any form of version control
- No tests (including no unit tests)
- Not considering XSS vulnerabilities
- Completely ignoring CSRF vulnerabilities
- Storing passwords as unsalted MD5 hashes (heck that was considered very *secure* in the days of plaintext password storage.)

...etc. I'm guilty of all of those previously. I daresay in the future there will be yet more things that may be standard practice now, but become taboos we look back on with similar disdain.

Our IT-Class project: Mathematics trainer in Java
Day 1 (was monday)

TL;DR we didn't save.

So we formed groups and I landed in the UI team with, let's call him Mage and let's call her Goth.

We had an eclipse project folder on our desktop (they said it only works when put on desktop) Btw they didn't even want to use a cloud or something (I wish we'd use git and I'd finally learn it). We should take the changes by USB from computer to computer.

So me, Mage an Goth are making a basic GUI for this Mathematic-Training App. We use this thing from Eclipse but I forgot the name. It has not enough functionality on surface and I hate things that break complex things up to ease things but leave away so much.

So after a productive hour of building a GUI and centering shit by calculating the top and bottom distance and use margins (hurts me really but Mage was designing, Goth intensively calculating on paper), the bell rings.

Mage wants to save the project on my USB-Stick and bamm💥
A black screen.
I don't know how it happened but it sure had something to do with the USB-port looking like you fucked it with a way to huge🍆. It looked damn broken.

So because we have a nice App called HD-Guard, which fucking wipes the desktop on startup and resets all but the documents/images/videos/music folder —

It's all's gone. Today is day 2 of this project so let's see how today turns out.

Working on a new project at work; all_of_a_sudden boss goes:

"A client needs the current software to do this thing, can u do it"

Me: "Yea, sure"

One week later: "Yea, Im not feeling this, can we change this, that, and--what the heck is that?"

Me: "😑 aaaaa the exact changes u wanted"

Boss:"Well, lets change (A list of stuff and new things added)

Me: Sigh....

I'm not a programmer by trade, so the only language I know well is bash. But as sysadmins we do use bash often.

Looking at other sysadmins' scripts though, there are interesting things in it every so often. Like for example `touch file` which creates a file. I've seen some sysadmins just do this instead `> file`. Genius! Or perhaps a `cat file >> elsewhere`. You can do that with `< file >> elsewhere`. It's something that if I hadn't seen it elsewhere, I wouldn't have thought about. But yeah, it saves a program call and it works!

Spent around 5 hours last night trying to do honestly one of the most basic things in PHP with a classmate of mine.
We are making a website kind of like Google Photos where the user can upload their images, store some information about the images they uploaded. (Basically just an online photo storage site). For what ever damn reason we could not figure out why our images that the user would upload from a form where not being put into their associated user image folder; Hell for the longest time they weren't even being loaded onto our LAMP server.
We still have no fucking idea what made it start working, we went over our code and iterated it probably over a hundred times and suddenly..... Like I said we have no fucking clue why; it started to work.
Over 2 hours in a hangouts call and around 500 messages later it worked.
I think we all know how this feels.

What a fucking mess.

Lately I've noticed a lot of people complaining about webview apps (electron and so on)... While I see their arguments for resource hungry apps, slow and unreliable - I strongly think that it's just complaining for no reason....

It's slow - yes
It's stupid to make web work in native - yes
But guys, isn't it awesome that technologies allows us to do such things? Even a simple web developer can quickly prototype an application on mac/windows/linux/android/iphones - even if it's not a great one, you still don't need to learn all the corks and quacks of the languages... You just need to get it out there!

So, I'd like to say that we should actually appreciate things we have more, even if it's as stupid as emoji coding language :)

ps. I really admire the emoji language as it's amazing on the spectre of what is possible.... :D

The more I hear about algorithms creating political bubbles the more I start to think about if I'm in one. Its crazy how as soon as you watch certain types of content you get a lot of political stuff. Eg. watch fishing and outdoor stuff and soon you will find a lot of conservative politics in your feed.
I feel like the science and engineering side has been mostly untouched, but on this topic people are more clever to hide a political agenda. Theres a lot of content that shows if we can do something and almost none whether we should do it. So we have a lot of unaware people that are pushing tech without understanding the deeper consequences of their agenda. I get the feeling of a trend, that a lot of people, sometimes myself included, don't do much thinking about the things they know and simply let others do the processing. Any new information then gets stored and never processed.

TLDR: Fuck you, take the time to read it or get lost!

Went to the O’Reilly conference on architecture last week. Will say there were some good points made (really liked the elephant in architecture and tech debt talks). But wow developers love to circlejerk. If you don’t deploy microservices on the cloud with serverless actions for everything then they’ll talk down to you like what you do isn’t important. Like so many talks memed monoliths were annoying. Like I get we love the new and shiny things but it’s kinda ridiculous.

No matter how much we do for client, sponsor, do the app for free. They will still not be happy with me. Always trying to bullying me to get more things done for free. Plus the fucken asshole bad mouth about my company and doesn't recommend us to anyone.

This one client we did a website for free 3 years ago. Just came in today wants to revamp the website for free again but this time they want more features. What surprising is that they don't want our company link to be on the website as they don't want to tell the world that we made the website. According to my boss via sponsorship they have not given any client.

First rant from my new job.
I got a position as backend-dev in a startup and for now i'm learning angular. Yes, you read that correctly, because the frontend-team is short-staffed i decided to switch teams. We are 3 people and neither one has sufficient angular-experience (the framework was a management decision).
First of all i got confused because we use slack and trello but the frontend-lead decided to do some stuff via google-spreadsheet too. Then we didn't have any code in our repository until yesterday. I tried to check out the repository after that, did an npm-install but when running ng serve i got an error "css-file not found". It turns out you had to download some files from the official website and put them in the unversioned node_modules directory. It was the teamlead's decision to do so and me and my coworker got really annoyed when we tried to set up everything on our end. But that's not all, yesterday the other dev's merged their first versions of the project. But not via git, that is way to mainstream. The coworker had to upload his code into the cloud and the teamlead copied the files into the project folder.
Aside from that the code already isn't the best, some things should be done differently imo and we have credentials in the code (not in some separate files, but in an if-else-clause that checks node.env.production).

We'll have a discussion about this tomorrow, let's hope things can be straightened out.

Going through site after senior dev asked front end dev to go through it and tweak it for design and better responsiveness(he and I are back end oriented and have no design skillz).

Things are breaking visually on almost all devices.

Client sends an email saying it suddenly looks terrible on mobile and wants to know what happened. I let him know we were actively working on things and it should be good in a few minutes.

Looking over CSS...there are "!important" tags EVERYWHERE, media queries are in the wrong order and have "!important" attached to almost everything so the largest screen size settings win.

Why do I even bother?

I think the reason why git beginners have a hard time with it is because the api is a bit untuitive.

For example: if you want to "unstage" staged changes, you run git reset, and if you want to "delete" those changes from your working copy, you git checkout those files.

But then, you find out that you can do all of that if you git add . and git reset --hard.
So you're like "huh..."

And then you discover that if you end the resethard with a branch name/commit id then you also make current branch point to the commit or that branch/commit (respectively).
So you're like "huh..."

And also if you add a commit id or branch name to git checkout, you change the current branch to specified/enter detached state with HEAD pointing to that commit (respectively).

Oh and you don't use git branch to create branches, you use git checkout -b because it's a lot shorter.

So here's a rundown: git reset mutates things related to files, but also mutates things related to branches.
git checkout also mutates things related to files and mutates things related to branches too (in a diff way). Also, creates new branches.

I don't think this is intuitive. We users use the same commands for different purposes with just a different flag.
Commands shouldn't mutate different types of things. But don't composite commands (as in, "smart" commands that mutate different things) shoudln't be a flag in an existing command, it should be a single new command of its own.

Maybe if I reread the internals of git now, I'll be able to disgest the dozens of technical terms they throw at you (they are many). And in my mind, the api will cognitively fit to the explanations.

Here's another one that feels weird too.
If you want to make your changes start on top of someone else's commit, you do git rebase.
But git rebase -i can be used for that, and also to delete, modify changes or message of, reorder or combine previous commits of the current branch.

Maybe the reason why several things we do overlap with the same commands is because they internally do similar things, and while not separating those commands might make it less intuitive, it makes them more sensible? i dunno...

disclaimer: I'm not setting this opinion in stone though, and am aware that git was created by one of the most infuential programmers.

Writing an efficient, modern renderer is truly an exercise of patience. You have a good idea? Hah, fuck you, GPUs don't support that. Okay but what if I try to use this advanced feature? Eh, probably not going to support exactly what you would like to do. Okay fuck it I'm gonna use the most obscure features possible. Congratulations, it doesn't work even on the niche hardware that supports that extension

If I sound jaded, ya better believe I f*cking am! I cannot wait for more graphics cards to support features like mesh shaders so we can finally compute shader all the things and do things the way we want to god dammit

Here we go, classes are starting again tommorow, tried to do most of the things on holiday, delegated school project stuff to the project members and made a planning with them...
and still nothing happend on their part in a timespan of 2 weeks and the deadline is in 5 days and A FUCK LOAD OF STUFF STILL HAS TO BE DONE AKA I guess I have to do their part too in 5 days..
*going into caffeine induced rage insane mode for 5 days*

SCStudentRant?

I have a subj called "Fundaments of Operative Systems" (or something along those lines), and I have 2 crappy teachers, one for the theory classes, the other for the exercise classes.
The exercise classes teacher is said to be the worst in uni and every time I think about that class I get a bit anxious because I can never do anything in it. Basically we don't get taught code in theory classes and he just comes and says "do this exercise" without explaining anything first. And when he does I still don't understand it.
I bet like 90% of us have no idea how to program in C and we need that for those classes. I hate C with a passion because of this.
In the theory classes, the teacher explains most of the things without powerpoints, and when we don't understand something (either ask about something he said or what's written in the board), he REFUSES to explain or say what's written, because he has "explained it before". He even chuckles as if it was really funny that we can't read his handwriting or just didn't listen because we were writting things down OH MY GOD. So most of the times when I copy things from the boards and then look at them at home I'm like "what the hell is this, this doesn't make any sense, what did he even write" (has some word that looks like what he wrote with ?? around it)
I think they wanna watch us fail. I really do.
I kinda understand the theory classes, but half the test is writing code. How am I gonna write code if I don't understand it? I have a work for that subj to deliver until monday but I can't make it work because I don't know the code I have to write. Damn it all to hell jesus christ

Additional note: they're both in their 60s and should be retiring not long from now so maybe that's why they act so carelessly.
Love the uni, not so much some of the teachers

I don't know what you did yesterday, but i did make my company throw away 2 months of progress.
It all started in the beginning, since that i've made numerous complaints about the workflow or code and how to improve it. I've been told off every time, and every time i either told the boss who agreed in the end or wrote code to prove myself. Everything was a hassle and my tasks weren't better.
Team lead: you'll do X now, please do that by making Y.
Me: but Y is insecure, we should do Z.
Team lead: please do Y
Later it turns out Y is impossible and we do Z in the end...
Team lead: please do W now
Me, a few days later: i've tried and their server doesn't give http cors headers, doing W in the browser is impossible
Team lead, a few days later: have you made progress on W?
Me: * tells again it's impossible and uploads code to prove it *
Team lead: * no response *

After that i had enough. Technically i still was assigned to do W, but i used my time to look over the application and list all the things wrong with it. We had everything, giant commits, commented out code, unnecessary packages, a new commit introduced packages that crashed npm install on non-macs, angularjs-packages even though we use angular, weird logic, a security bug, all css in one file even though you can use component-specific css files...

I sent that to my boss, telling him to let the backend-guys have a look at it too and we had a meeting about this. I couldn't attend but they agreed with me completely. They decided to throw away what we have already and to let one of the backend-guys supervise our team. I guess there will be another talk with the team lead, but time will tell.
It feels so good having hope to finally escape this hellish development cycle of badly defined task, bad communication and headache-inducing merges.

Code freeze is such an idiotic concept. What year do we have? Just make a goddamn release branch and do your codefreezy things there. Why the fuck would we stop the entire development just because you can't figure out git?

In horror movies. Characters do things that they them-self know it could kill them. Like getting in basement.

As a developer we all know to never deploy code on Friday. Here we are taking the wrong turn.

Issue in production. Multi billion dollar enterprise. Complex landscape. We sort of make things.

Turns out there is a single point of failure at a specific integration point. Kind of a lot stopped. When I reached out to the people knowing anything about it and I raised the issue that maybe we should make a slight change in how we do things they just brushed it off. Like it was nothing… 😬

No data was lost but everything was delayed for many hours. The _truth_ varied in different parts of the ecosystem causing potential wrong or suboptimal decisions to be taken.

When I asked why this LOS was not detected they told be they have no means of detecting it. 😬

I’m like, yeah, it’s 2023, we’re going to land on Mars and you can bet your ass we can detect it and you are just LAZY DEVELOPERS!

Anyway, I escalated (nicely) and they are now implementing a (more) resilient system and we’re helping the team detecting THEIR LOS in minutes instead of downstream services hours later (they are bad also but it’s not their fault!)

Stay safe!

Sometimes I just HATE Google.

No, this is NOT because they keep all your data, are evil and all the usual things. I just think they suck, yes there are super cool things and a lot of things are just the best in the field but I just feel like we could do better, there are so many smart people out there I just do not understand why everything is taking so much time.

PS. Just deleted all my browsing histroy accidentally because I didn't read the small print - in the picture attatched.

We often rant about people who think that because we can program we can do everything with computers.

But I have to admit that when I get asked what I do I often only say that I program or do something with computers. I usually don't get more specific because it's so hard to explain to someone who doesn't know anything about the subject that I would have to explain the basics each time. And I'm just to lazy for that.
It's nice when people ask me how it is going at work but I probably won't say anything more than ok or fine because my day was fucked up by a memory alignment bug in the chainloader and I now don't have the patience to explain what these both things are and why they fuck up my day.

When I started working as designer my boss at that time liked to invite people to remote control me, sit or stand behind my neck to explain their will and tell me to do this, "can we try this?", "can it be changed to another color?", "is it possible to move logo to the left?" and all that m*f*cking shit.

It didn't take long before I decided that I wouldnt accept that anymore.

They come with that energy, that illusion of power to play god with your fast mouse...

The first solution was to stand up with them around the chair and tell them I would take notes, then do the changes and mail them. That worked but sometimes it didn't feel right for the boss who got mad and tried to handle the mouse like trying to pretend she was going to do it...

In case the visit was by surprise I used this method, not sitting in worst position. Just recover dignity standing to their commaning stance.

The best and what became the real solution was printing things we needed, receive and guide clients to a meeting room where we would discuss things and take notes on the papers.

My project just went from "we can use one of those arduino boards, they are cheap and easy to use" to "we need a mass storage solution for that, maybe we can buy a shipping container and put it down on a nearby field as an on site storage". I love the things I would do if I had the resources for this kind of project!

One thing that’s a shocker and frankly very weird for people who have always used Android, is that iPhone doesn’t show any progress notif for anything whatsoever. Like dude.. I want things to happen in background and see progress in notif bar. But no, not in iPhone. You either wait for things to finish in foreground or do it explicitly inside the relevant app.

For example, when you want to send a big video on WhatsApp via Photos, you have to wait on the Photos screen until it’s sent otherwise it fucking fails. Like dude.. wtf?! Why can’t that happen in background?

On top of this, things that can happen in background have so limited processing power to themselves (because iPhone doesn’t like things happening in background; we have already established that though) that they just crawl until done and sometimes fail.

Another thing is that there are no fucking loading indicators. You touch something and then the guessing games starts whether you touched it correctly or not. Like dude.. I know your phone got a superfast processor but sometimes things take time to happen. You gotta give some kind of indication that things are happening ffs!

I know security and all, but dude you gotta give me something! Don’t make me suffer for little things.

Dude.. fuck you!

!Rant

Any skilled front enders in South Africa looking for a job in Johannesburg? My recruiters definition of qualified is "bookmarked w3schools - once".

It's a well paid job in a great work environment which approves the use of devRant. You will have complete control over design & ux. Lots of interesting things to work on we don't do 5 page sites and WordPress is a swear word.

Happy to offer a joining / relocation bonus.

I agree with many people on here that Front-End web development/design isn't what it used to be.

Things used to be simple: a static page. Then we decoupled design from description and we introduced CSS; nice, clean separation, more manageable - everything looks nice up to this point.

Introduce dynamic pages, introduce JavaScript. We can now change the DOM and we can make interactive, neat little webpages; cool, the web is still fun.

Years later, we start throwing backend concepts into the web and bloating it with logic because we want so much for the web to be portable and emulate the backend. This is where it starts to get ugly: come ASP, come single pages, partial pages, templates,.. The front-end now talks to a backend, okay. We start decoupling things and we let the logic be handled by the backend - fair enough.

Even later, we start decoupling the edge processes (website setup, file management, etc.) and then we introduce ugly JavaScript tools to do it. Then we introduce convoluted frameworks (Angular,..). Sometimes we find ourselves debugging the tools themselves (grunt, gulp, mapping tools,..) rather than focusing on the development itself (as per ITIL guidelines; focus on value), no matter how promising today's frameworks claim to be ("You get to focus on your business code"; yeah right, in practice it has turned out differently for me. More like "I get to focus on wasting copious amounts of time trying to figure out your tangled web").

Everything has now turned into an unfriendly, tangled web (no pun intended).

I miss the old days when creating things for the Web used to be fun, exciting and simple and it would invigorate passion, not hate.

<my cents="2"></my>

Smartphone manufacturers these days, imagine how meetings to come up with ideas for new products go about.

Product manager :ok people,what can we do to make our next smartphone 'different'.

Employee 1: let's add more cameras
Employee 2:Let's kill the notch
Employee 3:Let's include the buzzword AI in all of our marketing
Employee 4:Let's put 8Gb of Ram in our phone
Employee 5:Let's just do all of those things and also give it a screen with a ridiculous aspect ratio and unnecessarily high resolution.

!Rant

Wrote a crawler and now has 18 million records in the queue. About 500.000 files with metadata.
1 month until deadline and we have to do shit many things.

Now we discover we have a flaw in our crawler ( I don't see it as a bug ).. We don't know how much metadata we missed, but now we have to write a script that scrapes every webpage that we've already visited and get that metadata..

What's the flaw you ask? Some people find it funny to put capital letters in their attribute names.. *kuch* Microsoft.com!! *kuch*

And what didn't we do? We didn't lower case each entire webpage and then, only then, search the webpage for data..

TL;DR: What's cool about your company or what you'd like to have in your company?

I work at a small company (<50 employee) but it has some time around (I'd say almost 20 years or so).

The thing is, the boss here is cheap or inattentive or outdated or all previous options. This translates into a company stuck in the 90's management ways. Well, maybe late 90's.

So we don't have a lot of 'cool' or nice things here; and I've been thinking of coming up with a proposal of a progressive update of some things that gives us (the employees) some sort of identity.

For example, I think that small things like personalized notebooks or post-its or t-shirts give the employees some sort of sense of belonging. We don't have any of that. The only thing we have are business cards and I find them completely useless since I don't visit customers and all my communication with them is via email.

One thing I find very cool is when one employee starts in a company, in their first day they get a 'welcome kit' (example picture): notebook, pen, cup, t-shirt... It may look like stupid shit but it's way better and more motivating than the "Sit here and that's it" welcome I got when I started here.

So I wanna do a proposal of this sort of things that we can adopt, and I wanna know what do you find cool in your company or what would you like your company did so you'd feel more confortable or 'proud' (maybe that's not the word) of working there.

OMG you fucking little cunt!

Previous issue with this co-worker we hate eat other but can maintain minimal contact due to covid. Last interaction was actually nice, we joked a bit.

He teaches me how to do the build and ‘updated’ the confluence page. By update he striked through one paragraph.

Been doing these for week and now others what builds done all the time and since I am not an asshole they can approach me to do this but now I spend all
day long doing builds.

Work on a classified app so it has to
be burned on a disk, taken to a ‘secret machine’ and deployed. Takes about an hour and people are like. Can you rebuild it? I forgot to commit something?

So I updated the page to flush out the directions. Did not remove one thing only added things simple things like do a ls -lah in the dist folder to make sure the are built correctly. Things like check to make the symlink works, bolded words.

He was not at standup so I figured he was out of the office today and was going to ask him to review tomorrow.

Fucker goes in to make changes while I am making changes and doesn’t think to msg me telling me?

He is removing things and moving things which is fine just let me know! What a dick!!!!!

Screenshot of all the activity today, I am
in blue. I will spend all day watching the page to make sure I get the last fucking edit!

My director has started a new thing. We all have to tell what we did the previous day, what we are planning to do in the current day and if there are any blockers.

Good thing, right?

The only thing is that all these things are already plotted on the sprint board. It’s right fucking there in front of our eyes.

So what do we do? Just reiterate what is already written there. Fuck my productive life.

This is a classic example of "We need to justify our Dev's salaries so we made a bunch of changes in the name of innovation."

Why did they have to do this? I miss the old design where one swipe from the top had 5 icons, one for wifi, one for mobile data, one for Bluetooth, one for battery saver and one for flashlight. If you wanted to access something extra, one more pull and you'd get all of the notification tray options.

Now these fucking things take up half of the screen. Absolutely worthless design.

Me and my project partner were explaining a idea for a smart mirror in front of two of our teachers (female) for our major project of final year.
After telling all the features and things it will do for 15 minutes, one of them very seriously said that,
"so basically you are making a smart mobile app".

We both died a little inside that day... 💀

What are your thoughts on working for a company that give their devs jira tickets that don't have any descriptions? I work for a big organisation (It's actually in the top 3 biggest companies in the country I live in) and I work in a team that has quite possibly the worst agile practice I've ever seen. We get tickets without any descriptions at all. The worst bit is then we get pressure from project management for not delivering things on time. Do they actually realise how difficult it is to deliver something without any business requirements? I have to have a million meetings before I even know wtf the ticket is about. It's incredibly annoying.

do you guys think it's dangerous territory to do something you weren't asked to do at work?

like, i know i can improve some minor inconveniences, but they are not the priority. on the other hand, we always have a bigger problem and the little stuff gets left behind. idk, i just want to leave things better than i found them

Another department doesn't pass along the files mine needs until 3 days after they were supposed to and us reminding them 3 days in a row

Lead of that same department writes an email saying we promised a week turn around on our side and the files have been in house for a week so they're expecting finalization to be done today for ALL the files : |

Welp me and my manager speed run things and get half done today and we'll finish the other half Monday. If they really wanted all of them we wouldn't have gotten access so late to do our part

FUCK

I really wanna love Rust. I really, really do. But no inheritance is just such a stupid decision. But inheritence bad REEEE. No. Just no. Composition only works fine for some things because it just isn't powerful enough to properly (without performance penalty or boilerplate, that is) emulate inheritance. Some things are just better with inheritance: Games, UI, html or xml libs, etc. Now I have to use stupid fucking workarounds because oh no we cannot implement inheritance because that's scary and might give the programmers to much power. I can decide when I want to use inheritance or composition for myself, dickheads

I'm trying to bring some structure to the IT department, but I need help with something. I'm on my feature branch for some front-end stuff. I realize that there is some back-end missing that my colleague must do. How should we go about tackling this? Should he create another feature branch, fix the things, merge to master, and then i can merge from master?

Know what really grinds my gears? The fact that at many companies, PM's and QA people aren't required or expected to have even a basic level of knowledge, making communication pretty unpleasant. Even having a grasp of relevant vocabulary would make things so much easier.

Combine this with the bedside manner of a barn-raised sociopath, an ignorance of human and technical capabilities in general, and we have several good reasons to stay at home "sick". What the hell do I keep getting myself into?

Is it only me that I feel I am so special for being a programmer, and also able to think, learn, and analyze better than other people?

I feel like we are small group of people that do magical things that change the world while nobody even realizes or appreciates what we do

For some reason, Tableau is really heavy. I mean, all reporting software is a little bullshit, but Tableau... The server we had took 45 minutes to restart (no exaggerating - we timed it).

Reading the log files, yes, it WAS doing shit the whole time. Lots of shit. It seemed to be running just... Tons of software.

Tableau seemed to be aware of this because they have a page where you can check the status of everything. I assume that starts up first.

If you're looking into Tableau, two things to consider:

1) No, your braindead financial manager won't be making their own visualizations, no matter how many times the marketing team writes "drag and drop" on the Tableau website.

2) You'll make some nice visualizations but find that when you try to do more complex things, you run into constant roadblocks. If your manager asks "can you make it do x"? No matter how much experience you have, your answer can never be 100% "yes"... Or even "no" for that matter.

Not the worst experience with enterprise software, but definitely a surprisingly bad experience.

😔this weekend should be fun, I... I need to... well you see... I need to create a woocommerce site despite my better judgments and opinions on the subject.

God, if you are listening.. well reading, please have mercy on my soul.

One of my most arrogant customers was one that constantly called support because she could not get things to work as she wanted.

We repeatedly told her that she was working against the way the system was built and that was what was causing her problems.

This was not a custom system for that customer but a cloud product we where offering with over a thousand customers on and it was designed with a certain workflow in mind.

Despite this she always complained that the system was wrong and we needed to fix it.

She was also always late for her deadline complaining that she did not get the information from her bosses in time and demanded we help her get it done :)

But I was fortunate that everyone at our company held a unified position that it was not out fault that her bosses gave her info late or that she tried to do things in a way the system was not designed for.

So when she got to aggressive we just offered her to go somewhere else.

I thing they finally did, after about two years.

Rant about IT teacher

(This happened a few months ago)

I go to highschool and in ninth grade you learn about Excel and databases in general. In the first half of the year we learned how to use excel and in the second part of the year we learned about SQL databases.
So we learned SQL and how to set up a database using LibreOffice Base. At the end of the year we had to do one final project which was setting up a database and writing some queries.
We had to do it in groups of two and we had to choose for what we wanted to make a database.
We had like 5 minutes time to discuss it in the groups and me and my friend decided to do something like GitHub, so a database with tables for all the users, repositories, etc.
Then we had to tell our teacher what we wanted to do. Others made databases for hospitals, shops, netflix, app stores. The teacher asked the other groups, they told him what they wanted to do and he wrote it down. Here is how it went down with my group:
Teacher: So what do you want to do?
Me: A database for something like GitHub
Teacher: For what?
Me: GitHub
Teacher: what?
Me (very slowly): G I T H U B
Teacher: what is github?
Me: ...
(I was very surprised that he didn't know GitHub)
Me: well, you can upload files and work on them together with other people. There are also things like branches...
Teacher: Ah ok, so a cloud service
(I was done and wanted to end the conversation)
Me: Yes... it's a cloud service...
(Me in my mind: why do i have to be here)

We named our project 'GitGud', a little bit passiv aggresive.

Yeah so apparently my IT teacher doesn't know GitHub, however he installed Ubuntu on some of the school computers so I guess that's nice

We got an A so that's good.

concious inclusion training: we want you to talk and share about a bunch of shit that's illegal to ask in interviews: age,sex, orientation, family status, religion, values, gender identity, ethnicity etc

what the fuck do any of these things even have to do with the job?

im confused but whatever

We had this new guy working and we assigned him some work to do. We gave him some time to find the way into the code and figure things out on his own.

Instead of doing that, he wrote a paper of 20 pages why WPF would be way better than what we are doing now. There were many flaws in his document as well. Also on day 2 he used resharper to format some code file. Bye bye annotate! His argument was that resharper knew better. But, our code also uses some reflection, so that got broken. He didn't knew what reflection was and assumed resharper "fixed" it.

He doesn't work here anymore now, he felt he wasn't taken seriously. This is just one of many examples of him though 😂

we had that one teacher in the apprenticeship in the first year who taught us C. There were some people who already knew the language but most of us didn't and we had this one horrible test where we had to do some for and while loops with stars... Like generating something like this:
********
*******
******
*****
****
***
**
*
so most of rhat stuff we never learnt and he couldn't explain to us why our code wasn't correct and we all ended up getting really bad grades in that subject for something really basic -_- just because he couldn't explain it to us and test things we never had

Just figured out that while I was on vacation they made a really well thought (not) decision to switch to Firebase despite having 4 fully managed VPS with low usage.

Wanna know what the big deal is?
The only one who looks like knows anything is the fucking intern.

I was trying to understand the thought process and everything revolved around "its real time" argument.

No one knows how the api really works, the benefits of "real time" , and we are using the free plan :)

Yeah... People really do overthink things here...

So my friend who's learning to program didn't really feel like he accomplished much in a uni assignment since he googled most stuff, copy-pasted and tweaked the code a bit. When I told him that's actually the way we do things he found it the funniest thing ever.

!rant
Does anyone else derive great pleasure from creating quality of life/small utility programs?

So I'm learning python in between projects at work (plan on slowly moving new projects to it) and damn, my coding buddy and I have found a package/import for almost anything we can imagine. Heck, we canned ourselves laughing when we started googling random things and still found python packages that do it. I plan to use the language to automate a ton of things when I get a new PC.

Aside from that, I recently in 2 days (1 day building, 1 day bug fixing) made a tiny utility that shaves a good 5 minutes off a certain task for my colleagues at work, and in bulk use will save even more time. It's a textbox and a button only but it felt so nice to make something useful like that so quickly.

We rewrote the whole thing, except for iFraming some old pages in. We had to, the system was fucking awful and couldn't cope with any of the new mission critical requirements.

Client didn't understand the scope. Our project leader somehow snuck it in and we worked on it for months. We were sure we'd be kicked off the whole project... Somehow things didn't crash and burn. How it didn't blow up defies rational thought and the laws of physics. The new system worked, the client was happy, and boss made a lot of money.

Lead dev worked weekends for what feels like an eternity, it really was his baby and no one else on our company could have done it. It's where I finally learned how to do things the proper way; DDD, unit testing and TDD, architecture, building strong components in front-end, you name it. Before that I had a great nose for code smells and how not to do stuff, but now I got to see a proper system for the first time. It was glorious.

Then lead dev left and the system degraded quite a bit because new team didn't keep to the architectural patterns or general best practices. But we had a good run.

[Working on some really "urgent" report for an about to publish project]
dev: client, can you explain what this value is? we can't figure it out and we though tha...
client: im gonna stop you right there, DO NOT Analyse! we dont have time for silly questions, if the design says there's a 10, just put that freaking 10 in that place...
dev: but sr, we need to...
Client: what did i say? just stop saying things and build it!

I was an introvert while growing up hence I found interacting with non-living things easier. When I was 11 i.e. like 17 years I told my parents to enroll me into computer classes. They didn't see much of a future in it so they refused. I fought hard and finally they agreed. Hence started my journey with computers.

First week all students were allowed to explore the computer we were assigned and also were taught to play basic Windows 95 default games to make it interesting. It was all fun. Next week the teacher said he would be teaching us how to tell computer to do what we want i.e. programming. Hearing that I could make my computer do what I want excited me a lot. I felt I could finally communicate to a computer. This is how I learnt BASIC. I was so amazed I could do so many things like take input and do calculations etc. I decided I would do this kind of job in the future if it exists.

So now I am actually doing what I wanted to do when I started programming i.e. coding job!

Team Leader(TL): So you finished the sql scripts and stored procedures?
Me: Yep!
TL: And properly formatting the front end to look exactly how we want it.
Me: Yep
TL: Well we waiting on feedback from the boss so i guess you'll have to do the documentation.
Me: I hate documentation, please give me anything else
TL: It's not a lot dude, you can do it.
Me: Didn't one of the intern's and the database admin do it already?
TL: Yes. but you can take both of them and make one complete one.
Me: *You just don't want me to work on my own things you FUCKER* Fine, but don't expect it to be done this week.
TL: It's Tuesday, why not.
Me: Because i hate dcumentation

I FUCKEN. hate! documentation.

I stop doing things I don't care about.

If it's low motivation to do my job, I look at why. Am I tired? Do I dislike the kind of work? Does it feel like it's not going to help?

First, I make sure I'm actually doing alright. Usually, I'm just tired or maybe sick. Then I'll raise my concerns to management. There's a good chance that I'm not working on something meaningful and that we should change that.

Somebody asked me for help on their thesis, gave them advise, how they should do it, what are the best practices on implementing things...

I asked the today how are they doing? They answered, we paid someone to do it, we can't do it...

Damn are they even studying and doing their daily programming practice???

Dev: Hey this library you are mandating the use of doesn’t do one of the things you assumed it does

Non-Tech Manager: Well I think it does because I looked at it and that’s what it seemed like and the only reason you can’t figure it out is you are a bad developer and have attitude issues that’s why you are failing. You need to look on the bright side of things more often. This library has over 100k downloads which means it must do what people want it to. I think the problem is you. We can’t spend anymore time on this we have to just fix it and move on.

git add . && git commit -m "Because we're constantly interrupted and because we are not given enough time to do things properly, I need to check in and out of branches all the time (because separate envs are actually separate branches now) and have to interrupt what I'm doing. So this commit message reflects that."

Why do we never talk about angular? It was way ahead all the time. Like you got all these nice things with Vue 3 and React 42, but bro angular got it all for years..

It feels so nice learning it.

* Developing a new "My pages" NBV offer/order solution for customer
_Thursday
Customer: Are we ready for testing?
Me: Almost, we need to receive the SSL cert and then do a full test run to see if your sales services get the orders correctly. At this point, all orders made via this flow are tagged so they will not be sent to the Sales services. We also still need to implement the tracking to see who has been exposed to what in My Pages.
Customer: Ok, great!

_Friday
Customer: My web team needs these customers to have fake offers on them, to validate the layout and content
Me: Ok, my colleague can fix this by Tuesday - he has all the other things with higher prio from you to complete first
Customer: Ok! Good!

_Sunday
Me: Good news, got the SSL cert installed and have verified the flow from my side. Now you need to verify the full flow from your side.
Customer: Ok! Great! Will do.

_Monday
*quiet*

_Tuesday
Customer: Can you see how things are going? Any good news?
Me: ???
*looks into the system*
WTF!?!
- Have you set this into production on your side? We are not finished with the implementation on our side!
Customer: Oh, sorry - well, it looked fine when we tested with the test links you sent (3 weeks ago)
Me: But did you make a complete test run, and make sure that Sales services got the order?
Customer: Oh, no they didn't receive anything - but we thought that was just because of it being a test link
Me: Seriously - you didn't read what i wrote last Thursday?
Customer: ...
Me: Ok, so what happens if something goes wrong - who get's blamed?
Customer: ...
Me: FML!!!

We have this marketing class that none of us gives a rat's ass about and it's not related to software engineering in any way, and our professor knew that.

So to make things easier for him and for us, he made the rule that if we do at least 30% right on the test, we'll pass.

If we got a question right, we get 1 point, if we got it wrong 0 points, and if we left it unanswered, a quarter of a point.

That meant that if we didn't do anything on the test, we get 25 % anyway, so we almost pass by doing nothing.

Fucking genius.

I only answered 5-6 questions that I knew were right and left the rest unanswered and passed

There are few things that annoy me more than an app with unneeded transition animations between menus. An example of this would be the Xbox app on Android. Whenever you navigate to a new menu, it always has a stupid slow fade-in animation. Why do we need an animation every time we switch between menus?! It adds that much more time before we can actually use that section of the app, just because we need to wait for this stupid unneeded animation to run. It's like whoever wrote the app was browsing a generic animation library and discovered the fade-in animation, and thought to themselves "Woah this is so cool, it'll make the app go whooooooosh every time they change menus, they're gonna be so impressed!!"

!rant A guy is standing on the corner of the street! smoking one cigarette after another. A lady walking by notices him and says
"Hey, don't you know that those things can kill you? I mean, didn't you see the giant warning on the box?!"
"That's OK" says the guy, puffing casually "I'm a computer programmer"
"So? What's that got to do with anything?"
"We don't care about warnings. We only care about errors."

At a "guided internship".

Task: Develop a complete web application form

Was assigned to a team of 7 where all are "Frontend Developers" who have never heard terms like "bootstrap" or "mobile-first web pages".
That aside, all are seniors in age and qualifications, hence me telling them something to do is "ordering them around". And if I tell them to leave things to me, they be like "No, we wanna contribute and do the Frontend, as these things don't matter, inline css just works fine". 🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️

Why Lord? Just why?

"Here’s to the crazy ones. The misfits. The rebels. The troublemakers. The round pegs in the square holes.
The ones who see things differently. They’re not fond of rules. And they have no respect for the status quo. You can praise them, disagree with them, quote them, disbelieve them, glorify or vilify them. 
About the only thing you can’t do is ignore them. Because they change things. They invent. They imagine. They heal. They explore. They create. They inspire. They push the human race forward.
Maybe they have to be crazy.
How else can you stare at an empty canvas and see a work of art? Or sit in silence and hear a song that’s never been written? Or gaze at a red planet and see a laboratory on wheels?
 While some see them as the crazy ones, we see genius. Because the people who are crazy enough to think they can change the world, are the ones who do." - Apple Commercial

How do you deal with the learning curve frustration?
So, as a software developers we need to learn things frequently. But when we start, we have a lot of things to cover before we call ourselves average on that subject. Before this stage, there is a lot of frustration, stress, anxiety etc. How do you people handle it?

From perfectly working scrum team to... Don't know what it is now...
Long story short - our SM left company and our team have ongoing "reorganization", our tester leaving at the end of this month, probably we will be out of tester for next month...

I don't mean reorganization, it's normal thing, but... It looks like it's slowly collapsing under bad head decisions (one of them is the reason why our tester is leaving)... Multiple "side" projects / tasks for ppl in team and problems with delivering sprint tasks on time because of it, context switching etc.

I fucking like this project, it gives me much opportunities to learn new things and design new features - it's up to us how we will implement it. Client is satisfied with our work and we worked for their trust for long time. But if things will be going same way as now, we will probably lose it.

How do you think, is it worth to try stay with this project? Or should I update CV just in case?

BPOS client sub contracts a website and wants a WordPress one. Creates a design based on a theme.
This particular theme has a demo page.
And when running it through pagespeed insights returns a score Of 29.
Pingdom score of grade D.

Halfway through "development" we get a complaint from BPOS that the site is returning a score of 49 and a Pingdom score of grade B.

Considering how bad the theme is and how optimized we got. I believe that this was a miracle.
The things we do to make a living.

Sometimes you want to scream but you can't,
sometimes you want speak about how fucked up this society that we live in is... how the fundamental concepts of our lifes are wrong... How some things just don't work in the present... but there is no one who would listen to you... and even if they did, there is nothing they can do to change anything until the whole world listens.

hmmmmmm let me see.

Web based? lets do web based.

Do something simple like a basic crud app on web api format:
Do it with full authorization and authentication.
Start hard. Do it with pure golang using NOTHING but the std libraries.
Now, do it in a magic mvc framework like Rails or Laravel
Now do it on dotnet core
Now do it in django rest.

Watch the differences in all of them, sell your soul to something and now do it in Clojure. If you do it on a Scheme dialect or on Common Lisp my CMS admin will suck your whatever you have. Dude seems to be pretty good at it, we are trying to keep him from pulling tricks on the street but he insists.

Then add a React client with Typescript to get them basic ass endpoints to display nicely.

It should give you a fuckload of perspective amongst the different tools and way we do things and might make you appreciate the differences in paradigms required(pro points for doing modular in c# dotnetcore using different classlibs for the major points of the application using some crazy pattern like the mediator pattern)

I would hire a mfker that throws all this shit at me on a portfolio on the spot.

Data representation is one of the most important things in any kind of app you develop. The most common, classic way to do it is to create a class with all the fields you want to transport, for example User(name, lastName). It's simple and explicit, but hell no, in my current company we don't play that kindergarten bullshit, the only way we know how to do things here is full hardcore. Why would anyone write a class to represent a Song, a Playlist or an Album when you can just use a key-> value map for pretty much everything? Need a list of songs? No problem, use a List<Map<String, String>>, OBVIOUSLY each map is a song. Need a list of playlists? Use a List<List<Map<String, String>>>... Oh wait, need to treat a value as a number and all you have are strings? That's what casting is for, dumbass.

No, seriously, this company is great. I'm staying here forever!

I hate interviews. I am not too keen on giving them and not too great at taking them, though I typically do well.

We are smart people, there has to be a better way than coding things on the fly...

In all seriousness, the best part of being a dev is that you learn something new every day. That serves me personally as motivation. There are so many fields of study that embody what a dev is, and because of this, there are a LOT of things that you can do and create. On the other hand, the worst part of being a dev is the fact that we can't do it forever.

Now... I understand 2FA is to make things more secure, and I do appreciate it. BUT can we please work out a damn solution for people who work in an agency for other corporates which only have one shared account across the agency that bundles one phone number or mobile app.

What if people are on leave or sick? I need stupid 2FA to be able to login/work. uhhhhhhh.....

I hate my AWS professor, he just sucks at explaining the practical part of AWS. How one can make it completely dull, I just don't get - explain almost anything the right way and I am fascinated. I will also say the subject is taught online and I really do not jive well with online teaching outside of self-paced things. He has on one particular occasion given us a homework that he took from an Indian guy online that was impossible to do in our scenario, with AWS Academy student accounts, and we protested by not doing it and calling the professor to the attention of the administration. We'll see how it turns out by the Friday...

Me and the lead developer of my team gave a long and detailed explanation to our manager entailing the current state of a budge program our workplace uses.

This app has been bugging him for a while, he did not write it and has not been given an opportunity to rewrite the damned thing. Its a really...really messy application, and whilst it is a functional one it most certainly is NOT an efficient one since adding or moving things only incites more spaghetti mess.

We were laughing while giving our report, but both of us were crying inside. The main thing is, we both love PHP and the things he has built are very well structured and efficient, he has good technique, but will admit at certain caveats regarding the way he structures his dbs stating that he always has to do changes, which hey, its the nature of the beast, dbs change all the time. But our issue with php is the same: it lets beginners write monstruosities that are harder to do in other environments.

It really is a permissive language. But I reckon thay such lax nature is better left at the hands of the more experieced developers that know what they are doing.

Either way, we will restructure this motherfucker taking advantage of the new standards (which both of us are well versed in) and applying a more structured approach with a nice frontend interface (we be looking at Vue.js and React although we are considering Angular as well)

Gon be some good times.

Every meeting that contains one or more of the following points:

- "I don't think it belongs in the meeting, but"
- "Didn't get the meeting notes"
- "When's the food coming?"
- "I know we've said no technical discussion, but..."
- "Why is he so strict, this is no fun meeting at all :("
- "I think it's unfair to include risk assessment, you blame US before XY is finished"
- "The admins / the Team XY / ZX didn't talk with us, so we don't talk with him / her / them..."
- "Why are we here?"
- "Why is it so bad when production is down?"
- "I didn't know we do security / audit checks... Why hasn't anyone told us?"
- "Not happening. I'm against it"
- "I don't want to work with XY - he doesn't do it like I want it"

...

I could add thousand more things here.

I had countless meetings where I really thought that I was an alien who got broadcasted in a comedy reality TV soap...

Random opinion question:

I'm working on a thing where the user provides a big CSV and we process it and put it in the database, or update existing records.

This data impacts other things, but the data isn't front and center as a group of n the application for them to notice / see again (well they can query for it).

I'm thinking of taking the CSV and then presenting them with a table showing how we processed that data giving them a chance to review it before they commit it to the database...

I like this idea for two reasons:

1. If something goes sideways there's a chance someone will see it and I'm not sure I can do enough validation on a big ass CSV from god knows where to be sure we're going to process it right... (I'm going to do some validation but just can't cover it all)

2. It takes some of the mystery out of what happened / is happening for the user for.

Anyone try this in the past? Seems reasonable, but lots of things do before they go sideways.

How the hell do I understand want people want???

I listen to them, I pay attention to them (for the most part), but for the most part when someone assigns me something but it is not clearly explained, they expect me know what to do.

I had the most unproductive meeting with this guy I work for because of this... he had a problem, so we worked on ideas for this solution, and I thought I knew exactly what he wanted. We were getting somewhere. I get ready to leave for lunch and it turns out that is not at all what he wanted. We're back to square one.

Is it me, or are people really bad at explaining things?

I *hate* it when a senior asks me to write a functional test report. Like I thought we hired functional testers to do that sort of stuff? I'm a programmer, I only write 3 things: code, documentation, and more code. Not freaking reports about how something did not work before, and after this 1-line fix does work. Oh and don't forget to include screenshots and a description of the issue. Arghhh

I got assigned to work on a new project a couple of weeks ago. We got the POC code handed off from senior management, since he came up with the idea over the weekend. The project concept is hella exciting, but the dev manager and PO I have to deal with make life unbearable to say the least.

We have only 2 devs (including me) and 1 QA on this supposedly very important project. Of course, management announced the project to the clients already, so now we have to deliver ASAP cause it adds “sizzle”.

The MVP deadline is... no one knows when, either July 30th or September 1st. The MVP requirements are... unknown. I swear if someone saw the list of tasks and issues attached to “MVP” Epic, they would call us nuts trying to fit it all in.

To make things better, each PR requires 2 reviewers, so we end up adding manager as a reviewer just cause we need him to hit that “approve” button. So in attempt to make life easier, we requested to have a third developer. We are getting another developer, but that guy doesn’t know how to unit test a pure function...

Current priorities are... unit testing with coverage of 95% and if we want to refactor code, we have to add area to the list in a Google Doc. As a result, we are not tackling big things like risk of SQL injections not to mention big features like i18n (5-6 languages to support by the way and yes, it’s part of MVP as well as SSR no one knows why). Currently, I spend 2-3 hours a week in calls with the team just to figure out what the hell MVP is, what we have to do and why we have to do it. Last time we spent an hour refining 1 spike and breaking down one story into 3.

Oh, we also don’t have a deployment plan, not even to test environments since DevOps team was not aware of this project at all. Thus, QA cannot create any test suites and have to test everything manually which eats a lot of their time.

This whole project is a big hot mess and I’m considering leaving it all together especially since I’m working on two squads at the same time. I love the project, I love the idea, but management makes it unbearable, so I’m not even motivated to work on that.