[Thursday afternoon on a call...]

Client: Before we get started, can you create a sitescape outlining all of the pages and sections of the new website?

Me: Sure! I'll go through the website and shoot you a full layout in xls format as soon as possible, that way you can easily make notes on what you want added, modified or removed.

[Two hours later...]

Client: Hey, did you build that sitescape yet?

Me: Actually, I've been on back-to-back calls with other clients.

Client: So when are you going to get it done?

Me: Well, I have to go through the current website in it's entirety, which I'm guessing is about 1,000 pages. I have to determine which pages work fine on their own, which need to be combined for better presentation and which should be removed due to redundancy. That's something that is tedious and takes some time to complete. That, in combination with having an existing work queue that I need to fit you within and being at the end of the work week, we're looking at Tuesday morning to have it ready.

Client: "Existing work queue"? This is ridiculous. We're paying you good money to make our project your only priority. If we wanted to wait days for work, we would have saved money and paid for a cheaper service. You're already gouging us as it is! If we don't get the sitescape by end of day Friday, we're going with another company.

Me: I would tell you that I'm sorry for the inconvenience, but I'm not. I'm not going to feed you a line to make you happy. I'm also not going to work on my days off just to rush something out to you. You hired us because you wanted things done right, not quickly. Your current website is the result of not focusing on quality, but by how fast you can deliver it. We don't work that way. We only build quality products.

By rushing your project, not only do we alienate our current clients, affecting our reputation, but we build product of less than the highest quality. That will upset you because it isn't perfect, and it reflects poorly on us to use it in our portfolio.

If you want to hire someone to pump out this project to your unrealistic deadlines, be our guest. But you paid a 50% non-refundable deposit, so not only will you lose money, but your end product will suffer.

I'm going to let you sleep on this. If you decide tomorrow that another direction is the way to go, we wish you luck. But please understand that if we conclude our business, we will no longer make ourselves available for your needs.

Please find the attached contracts you have signed, acknowledging the non-refundable deposit, as well as the project timeline and scope, of which a "sitescape" was never originally mentioned or blocked out for time.

I hope that tomorrow we can move forward in a more professional manner.

[Next morning...]

Client: My apologies for yesterday. We're just very anxious to get this started.

-----

Don't let clients push you around. Make them sign a contract and enforce it whenever necessary.

Today was my last day of work, tomorrow i have officially left that place. It's a weird feeling because i'm not certain about the future.
The job was certainly not bad, and after all i read on devrant i'm beginning to believe it was one of the better ones. A nice boss, always something to eat/drink nearby, a relaxed atmosphere, a tolerance for my occasionally odd behaviour and the chance to suggest frameworks. Why i would leave that place, you ask? Because of the thing not on the list, the code, that is the thing i work with all the time.

Most of the time i only had to make things work, testing/refactoring/etc. was cut because we had other things to do. You could argue that we had more time if we did refactor, and i suggested that, but the decision to do so was delayed because we didn't have enough time.

The first project i had to work on had around 100 files with nearly the same code, everything copy-pasted and changed slightly. Half of the files used format a and the other half used the newer format b. B used a function that concatenated strings to produce html. I made some suggestions on how to change this, but they got denied because they would take up too much time. Aat that point i started to understand the position my boss was in and how i had to word things in order to get my point across. This project never got changed and holds hundreds of sql- and xss-injection-vulnerabilities and misses access control up to today. But at least the new project is better, it's tomcat and hibernate on the backend and react in the frontend, communicating via rest. It took a few years to get there, but we made it.
To get back to code quality, it's not there. Some projects had 1000 LOC files that were only touched to add features, we wrote horrible hacks to work with the reactabular-module and duplicate code everywhere. I already ranted about my boss' use of ctrl-c&v and i think it is the biggest threat to code quality. That and the juniors who worked on a real project for the first time. And the fact that i was the only one who really knew git. At some point i had enough of working on those projects and quit.

I don't have much experience, but i'm certain my next job has a better workflow and i hope i don't have to fix that much bugs anymore.
In the end my experience was mostly positive though. I had nice coworkers, was often free to do things my way, got really into linux, all in all a good workplace if there wasn't work.

Now they dont have their js-expert anymore, with that i'm excited to see how the new project evolves. It's still a weird thing to know you won't go back to a place you've been for several years. But i still have my backdoor, but maybe not. :P

"devRant has changed" "I'm so fed up with this site" "Its a bunch of hate and memes, it was so much better before"

A rebuttal.

devRant is approximately the same as it was when it was just a newborn. Remember the days of semicolon jokes being unironically funny?

Look at the top rants of all time, for fucks sake. #2 ever is:

"A different error message! Finally some progress!"

Posted three years ago. That's the second most upvoted rant in history (Remember, this was a "rant" because the joke/meme category didn't exist back then), it made it's way into the app store screenshots, and was a welcome post.

Now imagine that posted today. It would probably go over okay, in fairness, but it's certainly at risk of any number of pretentious pricks complaining about how this is "devRANT not 4chan" or how they had seen the joke before and it's a shitty repost.

And sure, the repost bullshit is fair. I'm not saying that all the reposts are good content. What I'm saying is devRant has always been full of reposts - they just weren't reposts in the early days. The quality of content is the same.

There's also the common misconception that your posts need to be directly related to tech to post on devRant. This is a myth propagated by 0 IQ heathens that don't read any further than the name of the application. Your posts can be anything that isn't prohibited, like porn, spam, and, importantly, politics (commonly overlooked rule)

"All the memes are just too much". Oh you poor fucking baby, let me pour you a healthy serving of pity juice. First of all, you can turn off the memes category, and while they will still find their way to your feed, the concentration will be much lower and it will once again be bearable for your pitiful, weak little soul. Do you seriously get annoyed that severely by shitty posts that you need to leave the app altogether, or do you just want the attention of being a "cool hipster that hates on xyz"?

"This place is just filled with hate! Why can't you just respect xyz technology, it isn't actually that bad!"

This is probably the most stupid fucking thing you could possibly ejaculate from your fingers into whatever device you are using to type. Welcome to devRant, we hate on shit. That's at our core. No, xyz technology ISN'T actually that bad, you're correct. But we're here to tear it apart because it probably has frustrated us in the past. I fucking hate JS because it was my first language and it confused the shit out of me. JS is a great language. But I still talk shit about it, and that's what we're here to do.

Like seriously, I know a lot of people post stuff they're proud of here, and then they're met with "Would be great if you didn't use xyz tech", and that hurts, but holy shit, this is devRant. If you're sensitive to criticism, or even just straight up being made fun of, don't post shit that you're proud of. You won't have a good time. It's just not what we do here.

Quick interlude before the conclusion, "My girlfriend dumped me after I named a class after her. She felt I treated her like an object." is also on the first page of all-time most popular posts.

In conclusion, devRant has not changed. Reposts have been a nuisance since day 0, and just because reposts look different these days doesn't mean the quality of content has decreased in any manner. The two main sources of your frustration are the volume of low-quality posts (Mind you, not the concentration of them, but the volume of them) and your own prejudices about the platform. You're looking back with rose-tinted glasses.

Here are some tips for a more enjoyable experience:

-Make sure you have the "Hide reposts" setting ENABLED in settings. Any posts marked as repost will be hidden in your feed, pulling down the concentration of low-quality posts.
-Keep to the algo sorting method. Obviously, algo is a bot, and there's still gonna be some shit content in there anyways, but if you're in recent, you are absolutely guaranteed to see low-quality posts. It's unfiltered.
-Keep in mind that what you consider a "quality" post is not what others consider a "quality" post. Just because you don't like memes doesn't mean memes are poor content. There are people here who have never seen the bobby tables comic. And they deserve the same experience we got when discovering dev humor.
-Don't be a prick. And if you cannot help yourself, leave. Ironically, you're making the site worse by complaining about how bad the site is. You can always come back if you aren't a prick anymore. And you can leave permanently if you choose as well.
-Downvote and move on. You're not doing anything but making yourself more aggravated by leaving a shitty comment about how shitty the shitty post is.
-Think critically. Obviously optional, and I know not many people like to use their brain when a phone is suspended between their hands, but if you want a better experience, remember to use your head and not to lose it.

---- Startup RantLife ----

A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)

Just who the fuck from apple thought its a good idea to make the FUCKING SCROLL BAR overlap, the FUCKING PROPERTY ARROWS, everytime i accidentaly hover over it? I cant change shit! I have to wait few seconds every time i accidentaly hover over the scrollbar so i can be able to FUCKING CHANGE the value!

Dear Apple Inc,

Fix your shit! We're paying 100$ a year for what? More bugs and toruture? I didnt sign up for this bullshit! Give us back some real quality products, or just buy the company Jetbrains and let them build the IDE for you instead.

An entire night I've spent on this shit.. preparing wires, soldering them on the motherboard, and finally connecting everything up to current meters, my PC's USB port and a lithium cell from my old Doogee phone that I still had laying around. All in the hopes to get an adb shell. But all in vain.. the turd doesn't even want to boot up. What a fantastic waste of time 😑
(Apologies for the terrible picture quality btw, this tablet's camera is absolute garbage)

KISS.
Keep it simple, stupid.

At the beginning the project is nothing but an idea. If you get it off the ground, that's already a huge success. Rich features and code quality should be the last of your worries in this case.

Throw out any secondary functionality out the window from day 0. Make it work, then add flowers and shit (note to self: need to make way for flowers and shit).

Nevertheless code quality is an important factor, if you can afford it. The top important things I outline in any new non-trivial project:
1. Spend 1-2 days bootstrapping it for best fit to the task, and well designed security, mocking, testing and extensibility.
2. Choose a stack that you'll most likely find good cheap devs for, in that region where you'll look in, but also a stack that will allow you to spend most of your time writing software rather than learning to code in it.
3. Talk to peers. Listen when they tell that your idea is stupid. Listen to why it's stupid, re-assess, because it most probably is stupid in this case.
4. Give yourself a good pep talk every morning, convincing you that the choices you've made starting this project are the right ones and that they'll bring you to success. Because if you started such a project already, the most efficient way to kill it is to doubt your core decisions.

Once it's working badly and with a ton of bugs, you've already succeeded in actually making it work, and then you can tackle the bugs and improvements.

Some dev is going to hate you for creating something horrific, but that horrific thing will work, and it's what will give another developer a maintenance job. Which is FAR, far more than most would get by focusing on quality and features from day 0.

"We need to reduce the scope of the project, guys... What if we don't make tests? They're taking some time do write, so..."

Yep. Let's compromise the quality and call it scope reduction. It will make wonders to our roadmap 👍

Boss: Have you finished that feature?
Me: Almost there, i'm refactoring some classes...
Boss: What? Refactor? But thisnis a new feature, it does not need refactor! We don't have time for this!
Me: 😵🔫

This is what happen when you care about code quality.

Worst experience with cs profs? Oh boy....

Databases lab: "You'll need to work of this snippet, if your IDE tells you it's deprecated you don't need to care about it"
If you want to imagine the quality of the code base we were expected to work upon just think about that attached xkcd comic, basically an undecipherable black box.

The instructions where at the same time micro managing everything (he gave us frickin variable names to use, and no good ones, no the database connection had to be called datbc, yeah very descriptive) and yet so obfuscated that I'm not completely sure he didn't resurrect Kant himself to ghostwrite for him.

He also didn't like us to use any Java feature that was to 'modern', for example for each loops since "they offer no benefit over normal for loops".

Further, everything we wrote had to be documented with a relationship diagram and a uml. So far no problem if he hadn't invented his own flavor of both (which can be read about in his book).
Oh, and he almost failed me because I used a lambda expression in his 'code on paper' exam and this "arrows are a C command" I "must have been confused"... which is glorious coming from the guy who can't get operators and commands straight.

My boyfriend, actually. But I value the human aspect more than the tech genius in fairness. He may be no Linus Torvalds but I don't care and wouldn't change him.

Why him?

He's very kind to less experienced developers and always happy to help them. He teaches them not only how to solve things but how to get un-stuck the next time and what to learn.
His code reviews are inside out, not just a quick scan, he gives a chance to learn and takes one for himself too.
He takes pride in delivering great quality, well thought over code, on time.
He owns his mistakes and isn't afraid to admit when he makes them.
He reads a ton of tech books and always learns something new yet stays humble while discussing things he knows a lot about.
He has a ton of hobbies other than coding which he's good at.

Ah there, yeah whatever I'm a big softie today 😋 he's not on DevRant btw. Also sometimes I want to punch him too, but mainly he's a good guy :)

tl;dr: thanks! :)

I just love this community.
The idea of devRant is great. The emotions, the shared knowledge in each post. Never seen such densely packed quality content in a social media! :D
I enjoy spending my time here, though I do not post that much. Reading just about the life of @linuxxx, @gitpush @alexDeLarge (to name a few) share with us is just wonderful, it makes me happy! :)

I think this post is meant as a thank you, I guess? Just felt like it... hope you guys don't mind having read a non-dev related post.^^'

btw:
@dfox and @trogus, you guys are awesome as fuck!

To me it seems that Software eng has become a „I wanna get rich“ thing..

Too many idiots do it and think they’ll get tons of money..
Not that many new geeks because of that..

Also, I feel like the mentality has switched from quality oriented to shiny oriented..
3/4 of new Software i use contains serious bugs that don’t get fixed because it takes time..

Fucking hell, that's now the fourth time in a row that I see my clients getting ripped a second asshole by previous developers, this one charged 1500$ for a "python script" that only calls ffmpeg with couple args, claiming tons of shit like the video being e.g. better quality after conversion - even though all it does, is a straight convert from one format to another. (no filters, anything, just a convert) I feel always so terribly bad discovering that shit and them proudly telling me about the "solution" they invested in..

Stack Overflow. Everyone uses it but everyone seems to hate the community. I very often read about someone getting down voted and they all say the same thing - "I have no idea why".

I have spent a lot of time moderating SO posts, which gave me a lot of reputation and medals. I find it fun to help people and it feels good to give back to the community.

I have asked a bunch of questions and I've never gotten a single down vote, which leads me to believe everyone of you that is constantly getting down voted are doing something wrong. Because the posts I see getting down voted are fucking stupid questions that either lack information or contain too much information.

Example 1:
Server java error

Why is my server not working? I am using Tomcat, port 8080 and I'm getting IOException.

Example 2:
Webpack configuration not working

My webpack is not a working, why?
[entire webpack config]

End examples.

What the fuck are you expecting asking questions like these?? No one gets paid for answering your questions, so the least you can do is write a CLEAR AND UNDERSTANDABLE question. I'm not gonna tell you how to do it because there's A LOT of information on how to do it.

People devote hours and hours to helping others on SO, and of course they get fed up with the stupid and lazy questions. That community is not about being nice, it's not about making people feel welcomed, it's about QUALITY OF CONTENT. No one is crying when they find a superb question + answer, right? That's the result of a community not accepting low quality content.

So please, the next time you get a down vote on SO - do not come here whining about it but instead take a look at what you have posted there and ask yourself if it could have held a higher quality.

Thanks!

Manager: We will be building a new app. THIS TIME EVERYTHING MUST BE ABSOLUTELY PERFECT, ANYTHING LESS THAN TOP QUALITY WORK WILL BE REJECTED!!

*Not even 2 days into the new project*

Manager: Ok that’s good enough, we can fix it later. Can you go quicker on the next feature? Just sacrifice a bit of quality so we get these tickets closed as fast as possible. I said we can fix it later. Getting tickets closed asap is top priority.

Dev: …

I think having the wrong job can really bring down the quality of life.

My friend has to drive two hours each way to get to and from work. That's four hours wasted commuting.. and his job is service desk agent.
What are the consequences, you ask? He never has a spare second to talk to me, he's quickly developing gray hairs and he has no time awareness.

Having the wrong job is unhealthy and results in a cascade of bad side effects.. When most of your day involves work-related things, that's just wrong. There is no Yin-Yang there. I know because my work life is somewhat balanced.

A nice word to all developers who say stuff like "I know I write bad code, but what does it matter.":
Please try to think in a logical way about what this part you are about to write has to do. It is much more difficult to rewrite code, the longer you wait after you started to code.
Bad code can have big impacts on different levels.
For example financially: Bad coding style or program structure can lead to thousands or much more in losses because of nasty bugs, bad performance, expandability or maintainability.
Think about quality over quantity.

A little example: I had to work together with other coders to meet a fucking tight deadline. The last day we coded like crazy and these dudes started to apply styling changes (CSS) directly as inline styles to the HTML code, instead of taking a few minutes more to find where in the CSS files they had to make the changes.
At the end of the deadline we had more stylingbugs than before. It took us another whopping 3 hours to fix what they had done.

So next time you code: Thinking before coding is mostly faster than just straightahead coding and fixing at the end. 😉

Story #1: So I took a month of parental leave. And was planning to extend it a little longer to deal with my final exams. I was planning to spend lots of quality time with my wife and newborn son. Little did I know... It turns out that out of 5 OoO weeks I was looking forward I actually had 3 at most. The rest I've spent working remotely as I was insisted to deploy a brand new and poorly tested feature to PROD 2 days before my paternity leave. So I spent 2 weeks debugging things in PROD. Remotely. Needless to say that did suck.

Story #2: After story #1 I've learnt my lesson. This summer I took 3 weeks annual leave to renovate my apartment. I asked to not to be disturbed unless there's an emergency. And an emergency it was. One of our app users had a planned hi-load batch job lasting for 2-3 months. Hundreds of thousands of items had to be created and processed. It turns out the _processing_ algo had some flaws and was acting out. I was called out and asked to assist. I knew this sort of debugging is going to take a lot of my time so this time I put my conditions on the table: I will assist but I'll extend my leave by 1.5 the time I spend working now. They took the deal. Instead of 3 weeks I had 5 weeks of vacation!

I don't care that much about my salary. I prefer to exchange it for my time off hence I didn't ask for compensations.

Bottom line: NEVER EVER underestimate or undersell your time and effort. You are a valuable asset and if the team/client needs you on your day off -- make it count. Your time off is YOUR time. Never forget it.

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

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

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

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

Everyday single day I have to give time for family, personal work and office. Prioritized in that order.

End result : low quality family time, pending personal projects. Office work - well that one is OK I guess cos the time is dedicated.

Solution : made a deal with wife - one day on weekend dedicated for family (she can plan anything she wants) and I will not do any work. Other day dedicated for my personal work/time (no family plans).
Divide weekdays similarly. On family days I checkout at sharp 4pm from office and come home straight spend the rest of the day with family alone. On the other days I stay either at office or go somewhere to work or hangout with dev buddies.
*Wife agrees*

End result: Quality family time. No interruption when coding (a dev would understand the importance of this). More productive work.

My code review nightmare part 2

Team responsible for code 'quality' dictated in their 18+ page coding standard document that all the references in the 'using' block be sorted alphabetically. Easy enough in Visual Studio with the right-click -> 'Remove and Sort Usings', so I thought.

Called into a conference room with other devs and the area manager (because 'Toby' needed an audience) focusing on my lack of code quality and not adhering to the coding standard.

The numerous files in question were unit tests files

using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Collections.Generic;
using System.Linq;
<the rest of the usings>

T: "As you can see, none of these files' usings are in alphabetical order"
Me: "Um, I think they are. M comes before S"
T: "The standards clearly dictate system level references are to be sorted first."
Mgr: "Yes, why didn't you sort before checking this code in? T couldn't have made the standards any easier to follow. All you had to do is right-click and sort."
Me: "I did. M comes before S."
T: "No You Didn't! That is not a system reference!"
Me: "I disagree. MSTest references are considered a system level reference, but whatever, I'll move that one line if it upsets you that much."
Mgr: "OK smartass, that's enough disrespect. Just follow the fucking standard."
T: "And learn to sort. It's easy. You should have learned that in college"
<Mgr and T have a laugh>
Me: "Are all your unit tests up to standard? I mean, are the usings sorted correctly?"
T:"Um..well..of course they are!"
Me: "Lets take a look."

I had no idea, a sorted usings seems like a detail no one cares about that much and something people do when bored. I navigate to project I knew T was working on and found nearly all the file's usings weren't sorted. I pick on one..

using NUnit;
using Microsoft.Something.Other;
using System;
<the rest of the usings>

Me: "These aren't sorted..."
T: "Uh..um...hey...this file is sorted. N comes before M!"
Me: "Say that again. A little louder please."
Mgr: "NUnit is a system level nuget package. It's fine. We're not wasting time fixing some bug in how Visual Studio sorts"
Me: "Bug? What?..wait...and having me update 10 or so files isn't a waste of time?"
Mgr: "No! Coding standards are never a waste of time! We're done here. This meeting is to review your code and not T's. Fix your bugs and re-submit the code for review..today!"

That moment you realise why you enjoy the dev life again.

It's been a long time since I've had a solid day of coding, just coding..., no meetings, no wild requests, no crazy issues, no data fixing because someone can't type a number correctly, just me, myself and that keyboard going on a field trip of quality coding time again.

Ah, it's a good day to end the week on!

I switched to Comic Sans for any internal communication.
Those in delivery/support/sales/HR/emotional crap/professional buzzworders/etc no longer take me seriously and therefore I no longer waste my time with their BS.

If not an improvement in the more materialistic side of the career itself, certainly an improvement in the quality of life.

I used to think Electron apps were gonna do great and make it more accessible for companies to produce high quality programs with ease.

Oh boy I was wrong. All it did is enable big companies with the ability to refactor all of their software to run 5 times slower, consume 10 times more memory and kill your battery 20 times faster.

I fucking hate all of this prototype fast optimize later bullshit. Can I get some value for my dollar? How come technology is just being degraded for the same of "ease of programming".

You save programming time but sacrifice end user time, cus our time just doesn't fucking matter.

Full year of cutting edge delivery on or before time, year end feedback time:

Manager: we r gonna give u lower rating this year because u we're not up to expectations

Me: but what expectations I did not meet

Manager: u completed all tasks before time and with quality and in half time compared to others...but unlike others u didn't slog...u should have slogged...

Me: fuck u...!! I resign!

Dear Product owners / Company Owners / Whoever requesting a feature:

Devs like to know they are adding value to whatever product they are working on. Every time you request a stupid no value added request, you kick the dev's soul.

After several hits the developer will stop caring about the software and eventually will get the job done, but oh boy, the amount of tech debt/trash code the dev is gonna leave behind will be horrendous.

Then the next developer, not only takes the hit from another stupid request, he/she will see the crappy code the past sad developer left and will take a double hit. Of course all of them start proactive and try to fix previous blood trails but sadness will catch them eventually.

If you want you're apps/products/reports to be good in a long run don't make stupid requests.

BAs, Stop being Expensive Email Forwarders and challenge a request, understand the process and then hand it to the developer.

Us developers are sensible cute ponies. Treat us well or expect poor quality projects

Indian web dev companies suck ( for developers )

when I finished 3 year grad program in computer application here in my country (India), I thought life's gonna be fun working as a developer. Oh boy, I was so wrong.

I started out working for a small service based IT company, followed by 2 more. I realized really quickly that they're nothing short of a scam. If your company's only agenda to somehow survive in the market and showing no signs of growth in 8 fucking years, then I'm sorry you're working for scamsters.

Now I'm not saying that all of them are alike. But most of them sorta are.

They don't give a shit about quality, not one bit. Quality means no money in the short run. And they haven't been able to develop any strategy to deal with that. Hence, no growth.

They promise 100 things on their website but only provide shitty services in 10.

There is no pair programming, no code review, no code quality check, no architect, no database designer. They won't give you extra time to write test cases. They use git as a storage device.

They don't put their developers (especially the ones who are learning) under any sort of managed development framework to ensure smooth work.

At the end of the day, their main objective is to somehow NOT deliver a project but finish a milestone and make money out of it.

After cashing out for a milestone, they want you to put your current project on hold and start working on a new project until you have like 10-15 projects in the pipeline and you're severely overwhelmed and you just wanna fucking QUIT.

They would say YES to literally every fucking thing, only to disappoint the client later.

I can't believe someone in the US, or UK thought it'd be a good idea to approach these companies
for their brand new app ideas. They're so fucked.

They're rarely finishing any project.

I'm sorry if I hurt your feelings. I had to get it out of my system.

Quality takes time.

devRant on a HoloLens!

The HoloLens is really cool, I was allowed to use it after a short hackathon. I am still surprised, but it works great and the concept feels natural after a short moment - web browsing is not recommended as no website is optimized for mixed reality (yet?).

Sorry for the low quality photo (it is not the compression algorithm's fault this time).

DuckDuckGo SUCKS!

I mean, I like the concept. The private, highly customizable search engine is what we all need.

But if 4/5 times I have to use 'g!' just to find some really basic stuff, because the results are incorrect or point to low quality content then what's the point of using it in the first place?! It's really frustrating especially if I try to find something in Polish or Dutch, but even in English most of the time the search results sucks!

I'm working in a blockchain company for $180 as a junior programmer and there is a mid-senior guy who get ~8 times more than me. So we got a project to make a backend API with its tests. When I was partly completed my part of the project I asked that "mid-senior" to share his code with me. Nothing was done, and he asked me to push my changes to git so he could start to do something (view at my code and start copying). BUT. He couldn't even pull from git. He couldn't use that fucking Visual studio's team explorer and even the solution explorer. Ok, he was working with VS for the first time, but I did too. I cloned the repo gave him the environment to start "working" and get back to my work. After that nothing changed, he was writing each one-lined if block for half hour and the code was very dirty. Finally I've got his laptop and started to writing his part by teaching him all the programming. You may say I'm mad. I really do, I think that I did all project. This is sad... How can people get this much by being this far from the programming? We need really high quality programmers.

Hey guys, I'm here to upvote quality content. I don't have much to rant, so take my support!

Been lurking for quite some time now =)

!rant

This might be the most ambitious project I've ever started up till now, teaching my girlfriend everything college isn't.

As some of you may know my uni isn't the greatest and lacks in professor quality, my girlfriend (who's taking the same bachelor) knows this and when she knew I was starting a new little side project she wanted in.

At first I was skeptical, this could be just an excuse to spend more time with me, so I told her:

"if you really want to then I'm all for it, it'll be done my way and the first few weeks will be tough, however I promise by the end of it you will know 10x what you do now"

She agreed and so our journey began 3 weeks ago, my goal: make a kick ass project, do it in record time and teach her enough to cope with a IRL job.

I've setup the project so by the end of it she is well versed in the following: scrum, Django, MVC, python, HTML + CSS3, git, GitHub, PostgreSQL and Docker. In about 4 to 6 months.

We are into our third sprint this week, she had two small breakdowns because she couldn't believe how much she was missing out and felt she lacked talent, this is our third week and I'm glad to see that she's actually enjoying herself.

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

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

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

So.... We spend most our lives learning languages and methodologies and best practices and all that crap while depriving ourselves of sleep because the rules said if we did that we'd make something cool and have fun doing it...

But then *any company here* comes along and says make this shitty feature in *arbitrary time here* for our stupid *product here*.
You do it working overtime and sacrificing quality to have the client say afterwards that he wants something different (from his own specs).

And then the circle repeats...

I should consider a different profession...
Hey plants don't speak... Maybe I'll be a gardener!
Clip here clip there - done. I'll be a happy fucking script

I worked someplace once that fired a person for lack of quality output. Before that he sued the company over a labor dispute. After they fired him he went and founded his own business. A year later the company decided to recycle his old laptop to another developer and discovered the source code and business prospectus on it. The company took it to court and said it was actually their business because it was created on its own equipment and the time stamps confirm during business hours also. Courts agreed and they got possession of his business and then fired him again.

Our CEO suddenly wanted to work with an outsourcing company to build the product. On one of the "sale" meetings I asked a guy from that company:
- Can we interview developers before they join our project?
- Our company is responsible for the quality of the service we provide, - the guy replied
- What are you going to charge us for?
- For all the hours developers worked
- So your service is developer hours, and we'll be obligated to pay for all the hours they worked regardless the code quality or the performance, right?

So it seems outsourcing company is only responsible for their time sheets to correspond to real hours worked? :-)

We call such a companies in Ukraine - a galley

Hello everyone,
I am a french student and I was wondering if college sucks everywhere ...
This is my third college year and I have the feeling that I am wasting my time.

I am in a quite good engineering school but most of the programming courses suck because «teachers» are clueless about the course that they give.

I am not here to tell that «I am better than them blabla» but I just wanted to know if the quality of education has slightly dropped not only in France.

I am really interested in your opinion, feel free to debate in the comments :)

Do you still store your music files locally?

I like owning my music files on my storage.

Disadvantages:
Storage space
Time spent organising metadata

Advantages:
Savour the quality
Accessible

I don't have an internet access all the time unless I'm home. I feel left behind seeing everyone just streaming music.

If you're a manager that cuts on hardware quality — listen.

When you die, I will contain your soul into the closed cube made of cheap whining SMD coils. You'll be there forever unable to end your suffering and will forever hear that coil whine until the end of time.

A) Create something that works, is fast, minimum bugs, have edge cases covered, nice testes, clean code. Cool, you did your job. END.

B) Create something shitty with bugs, performance issues, non or poor test coverage, mess code, etc. Cool, you did you job. But...

Next week you reduced bugs by 50%. Wow, you're rockstar.

Another week you improved performance by 15%. Again, you're the hero.

2 weeks later, you reached 85% test coverage. Management is so happy that almost got orgasm.

"A" took 3 months, "B" took 3 months plus few months of fixes. The only time where B was winning was first 4 weeks, where A was carefully building it's architecture and quality.

Yet B is seemed more successful.

This industry is F****d Up beyond my understanding.

1. Success in supporting my wife for her personal goals

2. Quality time with my family, especially with my daughter

3. Maintain my current brain abilities

I forged a katana once, under the supervision of a swordsmith. Nothing super special like damascus patterning or anything, but the cutting edge was pretty sharp.

Ugh sorry, lame word jokes.

In terms of software...

Microsoft Office Ribbon (cutting edge at the time, lol). Only as a maintenance drone on a bunch of manual search-and-replace work and merge conflict resolving.

Ariane 6 family of rockets (Welding X-rays and other DICOM quality assurance).

Software for continuous flow chemistry, developing microfluidic PCBs to perform Elisa immunology assays during the Mexican flu outbreak. Idea was to eliminate the need for microplates, expensive robots, microwell washers, etc — just have blood plasma, enzymecoated nanoparticles, antigen, conjugated detection reagents and substrates flowing programmatically through a PCB with a spectrophotometer built in.

My current project is a fucking nightmare.

It started in 2007, using a solution developed by an Indian company due to outsourcing (aka low-quality code).

It's running on Java 7 on the back-end and its front-end side is pure Javascript files. There are thousands of little .js files everywhere, no documentation, no comments, differents coding styles, outdated API that were already outdated at the time, mixed oop and procedural.
Not even when I started coding, I wrote something so horrible.

Yo, it's a clusterfuck and I just wanna get drunk.

Switched jobs one month ago.

Used to work overtime on complex features, every engineer was 10x, learned a bunch, worked my ass of everyday. Switch due to overtime and because I wanted more personal time.

Anyways, at the new job I’ve completed two tickets in a month, code is shit, no one cares about the quality, scalability, etc. I’m payed 2x more and I currently work max 3 hours a day. Feels weird AF. I guess I got what I wanted, but didn’t know back then that professionally I’m going to degrade. Didn’t happen yet, but I can see that in the future.

🤷🏻‍♂️

Its all fun and games until your malfunctioning software costs people their lives - if you're just starting out as a dev or in the "ain't nobody got time for writing tests" camp, I highly recommend you to lookup and read about the Therac-25 incidents during the 80s.

Even if you're not working on a life-critical/mission-critical application, the realization of the impact that us devs can have on the society can push you to become a better developer producing quality software...

Most tedious part of my day...

While meetings are boring and awful and all, it's probably spinup times for me. Each and every change requires a minimum of 35 seconds of spinup to test. If i'm testing something with mailers or other daemons, that increases to easily 90+ seconds (plus the worker thread pickup times).

It's not enough time to do anything useful, and more than enough time to lose my focus. It turns every task into boring, tedious struggle. It's awful.

Apart from my coworkers, this is the single worst part about my job. (Okay, the awful code quality totally pushes this to third place.)

So working on the Android for work, and go to add in images for parts of the app. I add in images and load the app up and it crashes, I thought hmm maybe I missed something for the imageview.

The exception was an out of memory exception and from looks of it, it exceeded my phone memory by quite a bit (OnePlus 3 has 8gb LOL), I was stumped since I don't typically run into this.

Turns out this time around it wasn't my fault lol, I had some images outsourced to a company our company uses for doing design work and well Android doesn't like 2000 x 2000 super high quality for logos.

I mean sure it's good it's high quality but to have 3 images eat up a lot of memory (I assume my phone won't allocate all 8gb to one app lol).

Lots of oof in one image.

I like how they had the audacity to say (and I fucking quote): "this is good news!"

I don't like to complain about sites generating revenue. I understand it is important and I even feel morally obligated not to use an adblocker. But all I will say is that the site has sustained itself for a very long time without the use of poor-quality and unrelated ads, and this feels like a lot more of a money grab than something the site actually requires.

Anyways, happy to see a -400 score on it. And I guess I can't wait to get Amazon ads on SO.

Our company maneuvered themselves into a classic technical debt situation with a project of a second team of devs.

They then left, signing a maintenance contract and now barely work on the project for exorbitant amounts of money.

Of course management got the idea to hand off the project to the first team, i.e. our team, even though we are not experts in that field and not familiar with the tech stack.

So after some time they have asked for estimates on when we think we are able to implement new features for the project and whom we need to hire to do so. They estimates returned are in the magnitude of years, even with specialists and reality is currently hitting management hard.

Code is undocumented, there are several databases, several frontends and (sometimes) interfaces between these which are all heavily woven into one another. A build is impossible, because only the previous devs had a working setup on their machines, as over time packages were not updated and they just added local changes to keep going. A lot of shit does not conform to any practices, it's just, "ohh yeah, you have to go into that file and delete that line and then in that other file change that hardcoded credential". A core platform is end of life and can be broken completely by one of the many frameworks it uses. In short, all knowledge is stowed away in the head of those devs and the codebase is a technical-debt-ridden pile of garbage.

Frankly I am not even sure whom I am more mad at. Management has fucked up hard. They let people go until "they reached a critical mass" of crucial employees. Only they were at critical mass when they started making the jobs for team 2 unappealing and did not realize that - because how could they, they are not qualified to judge who is crucial.

However the dev team behaved also like shitbags. They managed the whole project for years now and they a) actively excluded other devs from their project even though it was required by management, b) left the codebase in a catastrophic state and mentioned, "well we were always stuffed with work, there was no time for maintenance and documentation".

Hey assholes. You were the managers on that project. Upper management has no qualification to understand technical debt. They kept asking for features and you kept saying yes and hastily slapped them into the codebase, instead of giving proper time estimates which account for code quality, tests, reviews and documentation.

In the end team #2 was treated badly, so I kinda get their side. But up until the management change, which is relatively recent, they had a fantastic management who absolutely had let them take the time to account for quality when delivering features - and yet the code base looks like a river of diarrhea.

Frankly, fuck those guys.

Our management and our PM remain great and the team is amazing. A couple of days a week we are now looking at this horrible mess of a codebase and try to decide of whom to hire in order to help make it any less broken. At least it seems management accepted this reality, because they now have hired personnel qualified to understand technical details and because we did a technical analysis to provide those details.

Let's see how this whole thing goes.

I remember a bad freelance experience.

It was a sophisticated mobile applications (many UI, many customization, many APIs to integrate with). since the client have many future freelance projects, I give him 3 weeks as estimation time, and one day per week I work on its place to evaluate the progress and sync our work.

I worked hard, the quality was excellent.. but he kept ask for "small" changes and "small" features.. at first it was OK, and I was planning to give him a good example to profit from his future projects.. but he toke advantage for that and the same app extended from 3 weeks to 2 months and more.. he barely added a little to the initial price..

So what I did? I uploaded the code to a private repository in Bitbucket, added him to the team.. I wrote few lines how to sign and publish the app.. aand disappeared.
his luck, I disappeared from the country, I immigrated to another country for best job opportunity.

I've thought of couple of good outcomes of Apple removing the headphone jack:

1. Wireless headphones will be developed much more

2. They will be available for better prices as competitors starts to compete. At this time most of the wireless headphones are quite expensive.

3. Quality over wireless will now become a priority.

But I don't support this decision and will stick with my Xperia Z5.

The effect of the scoring system is interesting.

On Facebook, where I usually spend most of my social media time, I have been training myself to NOT comment unless I really wanna engage, because I have an IRL habit of just talking shit just to hear myself speak that bleeds into my Facebook engagement, which is a character flaw I’m trying to change.

On here though, I will see something I wouldn’t normally respond to and I’ll comment cause I want those ++s.

BUT the quality of my comments on here are generally way “better” (more meaningful, usually kinder, etc) than my FB comments, obvi because I want those ++s and on Facebook I can be as dumb and mean as I want without having “consequences” aside from the obvious social consequences of people thinking I’m an asshole...but on here it kinda forces me to be more mindful of how I’m engaging with people

To anyone asking for tips and tricks to start programming or become good at it, here is your ultimate golden advice: learn how to google and stop asking stupid questions like this before doing a quick research.

Reasons why:

1. You will most likely to learn better if you do your own research before asking for help. Even if you can't solve problem, you will be better and better at googling over time.
2. It is instant source of information. No need to wait for response (except response from server of course).
3. It takes only YOUR time.
4. Much more possible solutions/answers to your problems/questions.
5. Your quality of life will be improved over time. Not only your dev life but your daily life too.

So a little story about finding your way. I worked at an IoT software firm, very well established. I had a hard time with the on boarding process due to some factors, and I must have lagged behind their mental schedule for my growth. It was clear nonetheless that I was a quality coder and had made some friends there.

It wasn’t enough for the ensuing corporate bullying. It went by and I took it. I became the yes man just so I don’t frustrate anyone enough to turn away my ask for help. This made things worse and before long, I a grown man went to visit my mum and all but cry at how small I felt, after all my hard work getting to the company.

I felt sick with failure but I knew I couldn’t go back. I emailed my resignation and dropped off my company laptop.

4 months later I am working at a medical startup with my own projects, that I have 100% control over. And the quality of my work and ethic is pleasing upper management in all the right ways. I’ve never been happier, and there are barely any perks on paper. No free lunches on Thursdays or discounts at the local high street. I’m the happiest I’ve ever been in my life because I said NO to feeling or being treated any less than I worked and progressed to be.

Don’t let other people stop your potential for their own ego, or any other reason. 😊

The weekend is here!!!
Time to go out and have fun!!!

Nah just joking. Time to write some quality code after cleaning our company's backend (pun definitely intended) all week!

1. Apply to as mant jobs as possible daily on dice/linkedin/indeed
using keyword resumes customized by scrapping

2. Filter out low-effort crap companies and filter out recruiters.

3. Post "dice/indeed/linkedin daily decrapified."

Tada! Fewer time-wasters during the job hunt.

4. Bonus: turn into a search engine.

5. Daily double round: turn crap listings and quality listings into AI training sets. Incorporate into search engine.

If industry can use bullshit hiring filters, we can use application filters!

It seems like there are more lower-quality or duplicate comments on rants these days.

Please, save me some time and show a little respect for members of the community by ++ the comment you agree with instead of adding a nearly identical comment and tagging the commenter.

Additionally, comments like '@commenter 😂' when the great comment is still at +0 generally don't add to the discussion and should probably be downvoted.

Comment if you think you can add something, not just because you saw it.

Everyone is on their vacation and I am in good mood so time to refactor some 3 year old frontend, angular, javascript code. After 5 minutes of looking, some great quality of code snippet on the image below.

As a developer, I'm fed up with companies that expect us to work miracles in impossible timelines. We're not wizards, we're not magicians, we're not even superheroes. We're human beings who need time to develop quality software.

It's frustrating to be given a project with a deadline that's completely unrealistic. It's even more frustrating when the same company that gave us the deadline is unwilling to give us the resources we need to meet it.

And let's not forget about the endless meetings, emails, and phone calls that eat up our valuable time. We need to code, not attend endless meetings that never seem to accomplish anything.

And don't get me started on the non-technical people who think they know more about coding than we do. Just because you know how to use Microsoft Excel doesn't make you an expert on software development.

It's time for companies to start treating developers with the respect we deserve. We're not just code monkeys, we're skilled professionals who can create amazing things when given the right tools and resources. So stop treating us like we're disposable and start investing in us. Trust me, it will pay off in the long run.

My company’s upper leadership is sooo focused on the NUMBER of defects that are open on our project and only the number. We give each defect a priority of P0, P1, or P2. You would think this would help prioritize and strategize our plan to fix them. But nope. Every week we have some arbitrary “goal” to hit. A number purely made up by clueless leadership as to what makes a “quality” product.

On Friday’s, managers start harassing devs to merge their fixes and for QA to close out defects. So effectively rushing to hit that arbitrary number or else we’ll have to work Saturday.

Meanwhile they want more test automation coverage to reduce the incoming defect rate. But when the fuck do we have time to develop said tests when all you want is the defect closed to bring down your precious little number?!

They’d rather us close 25 P2 defects to bring the number down rather than 10 P0 or P1 defects. These leaders are so incompetent it kills me! Without any back story, they’re ultimately the reason we’re in this position in the first place! Argghhh!

TL;DR don't fiddle around with batteries if you aren't ABSOLUTELY sure what you are doing

For my arduino project I need to use 18650 Li-Ion batteries. They are pretty awesome but at the same time pretty dangerous if you don't use them the right way. You need protection boards etc. or they can/will go BOOM.

So I am looking around Amazon to find some good quality ones and reading some reviews made me wanna cry.

People were REMOVING protection circuits from the batteries and even removing the foil around the batteries. NEVER EVER FUCKING DO THAT!

I also found out that these are the batteries used in E-Cigarettes and now I really don't wonder anymore why they explode so often. People fuck around with the batteries just so they fit into their vapes, or reduce the resistance of the coil (the thing to heat up the liquid) to an absolute minimum so they can get more watts. A side effect of this is that a lot of current gets drawn from the batteries (>20A or something) which makes them go BOOM if no protection/fuses are used in the circuit.

The feeling when random dudes downvote a question, because a guy who finally earned some points on SO dared to format the code with `<code>`<br> He pasted code, log, even explained a little bit and ~500 point guy even flags it like _unclear_ although there's clearly visible import error.

I mean... as an answerer or moderator, I'd be damn ashamed for such behavior! I have absolutely no problem kick a person with words + explanation in my answer or comment, so that (s)he remembers to ask better questions and feels bad about that, because nooby questions are already answered so many times there.

But to downvote because of formatting even if you have a permission to edit and a flag for low quality or because you can't read ~40 lines of log makes you just a retard and hurt the whole remaining community of guys like me who find time to sit there and answer questions to help another people.

You know your a dev when quality time with the kids is sitting them on your lap and letting them watch Netflix on one monitor while you program on the other.

Attention Software Engineers!

Quit shooting yourselves in the fucking foot! And this ESPECIALLY goes to new grads. I get that you have just finished school. I get that you need a job! But don't fucking settle for a $30-$40k salary because you're "entry level"! The only reason why there are employers who offer that type of salary is because they know that there are enough idiots who will settle for it!

On average, an entry level software engineer's salary is between $50-$60k at the very least! For Senior developers, it is at least $80K/year (although an argument can be made for why they shouldn't settle for less than $100k/year).

Each time a moron low balls his/her salary, that brings down the market value for that talent. And keep this in mind! They don't have a choice but to hire you. They could choose to outsource their work to poorer countries but they don't want to do that due to obvious quality-related reasons so they HAVE TO hire you if they need the work done. And since the ball is in YOUR COURT, demand your fair salary. You went to school for 4 fucking years. You dealt with that stress for 4 fucking years. Why settle for a salary that you could've made without going to school?

So recently my open source project took off and got trending on GitHub (680 starts and 225 forks). This was the first time a project of mine really gained some traction and invested more of my time and weekends to maintain this project - I wrote comprehensive docs, contributing guidelines and reviewed PRs and made sure I commented on every single one of them. Sure, it isn't easy to review 50 PRs a day after coming home from work but the excitement of seeing this project becoming trending fueled me.

First 2 weeks it was good. I would come home from work and have dinner and sit down to maintain the project. Whenever contributors would be stuck, I would help them and write comments on each PR.

But the problem started since last week. People just really want to see their contribution activity graph get populated and hence they would make stupid PRs and literally no one followed contributing guidelines - I mentioned in that that the code should adhere to Pep8 styling but no one gave a shit. Each day I would spend reviewing PR with crappy formatted code and no sign of Pep8, and even some will just file PR and add a fucking docstring to every function or add paragraph of comments. Also, the PR quality was bad with unsquashed commits amounting to 10 or 20 or even sometimes 50.

I wrote the contributing guidelines doc and in that I mentioned every source that contributors could find helpful like how to squash commits, how to file a PR and Pep8 and not to write useless comments. Seriously people, grow up!

I guess I've just got the ideal dev job. Working from home, with nice people in my team and enough time to deliver quality work.

I carry the same mindset as an aspiring programmer as I did when I was a music major. There were times I practice for hours and got very little out of it in terms of quality (because I wasn't interested, focused or willing) and then there were times I practiced for 20 mins and really made progress on the piece. So I always keep that in mind to save me time and to produce better code overall.

> asks for better pay
> starts trying to evaluate the quality of our efforts
> complains about doing things that are not good in the long run
> spends time mastering best practices
> unemployed

Am I the only one that thinks it's extremely fucking stupid that the software engineering industry is simultaneously experiencing a "shortage of talent" and maintaining the same ATS that filters legitimate talent just because the resume doesn't fit keyword specifications?

We see it every day. People with years of experience that should never be allowed to touch important code. People with little to no experience that learn fast and perform well. Fuck years of experience being the only thing some recruiters see.

"We generally don't hire people with less than 3 years experience" shut your fucking mouth. Ridiculous. You hire people out of college, don't lie to my face.

Oh and don't even get me started on how many people fabricate their industry experience and get interviews from it. That's what happens when recruitment patterns fail to catch up to an industry that increasingly trains people better up front, and in shorter time periods, and values skills that ATS doesn't give a shit about.

Crazy idea: make job applications test problem solving competency instead of weeding out quality candidates.

Job searching is frustrating.

I’ve come to the conclusion that developers who like react have never used it for anything even remotely complicated.

Because here’s reacts dirty little secret; it doesn’t scale. Not even a little. It’s flexible, but that leads to every developer writing their code in a different way.

It’s simple and easy for simple side projects, but as soon as you have to pass state to a child component, you’re fucked. And god help you if you’re modifying the state in said child component. You can try using redux, but that’s a bandaid solution to the real issue.

There are better alternatives, namely Vue. There’s no need to write unintelligible code that’s a mutated hybrid of html css and js. We as web developers realized mixing these technologies was a bad idea a long time ago.

React simply doesn’t scale. It’s flexibility, complexity, and the awful code quality it leads to makes it a nightmare for large projects with multiple developers

Some of its concepts are interesting and useful though. It’s functional concepts allow for easy code reuse, among the other benefits associated with functional programming

I sincerely hope that the hype around react dies out, and a new framework emerges that takes the best from react and fixes the glaring issues it currently has

So a non programmer friend of mine needed an in house time tracking tool and found one on codecanyon. He bought it for 40$ and asked me if I could provide him some Webspace to host it until they deploy it in house. I said yes and took a look at the code as some stuff wasn't really working. All I can say is "wtf is that pile of crap". Nothing works, it looks like it's written by a first grader and it's UI looks like it was assembled by a chimp (well actually I think chimpanzees could make a better UI). Now I am interested the progress of rewriting that tool for him and I am almost done with all functions that thing should have and even more after 6 hours. I wonder if all stuff on codecanyon has the same quality and if, I am considering this as bonus income...

Step 1. Learn to code .
Step 2. Exchange code for money.
Step 3. Exchange money for car, soap & a clean shirt.
Step 4. Profit.
[GOTO: Step #1]

Lol. OK on a serious note coding improved my love life, it drastically reduced the frequency of dates - but dramatically improved the quality and duration of my relationships.
I used to believe that anyone/thing had the potential to be great - and (like me) all they needed was a little time to seize an opportunity.
This essentially meant there were no deal breakers and I spent a lot of time giving people benefit of the doubt and investing a lot of time & effort supporting and trying to build on aspirations that would turn out to simply be fantasies I was indulging.

I still idealistically believe that everything/one has infinite potential - only now I know which problems are worth solving, which are purely for fun or a thought experiment and which should immediately be thrown out and refactored.

All the ambition in the world is void without drive.

End user when criticizing a developer for 'taking long' to create something of value from scratch:
(4 hours later): "What's taking you so damn long? Are you retarded?"

Oh I don't know, maybe I have to make sure that tests in my code run well, maybe I have to evaluate everything to meet the custom satisfactions of the user for his ever-so-custom requirements and I also have to make sure I discard what they don't like? And maybe it takes time to deliver a quality product, and so on?
Or would you prefer I deliver an untested product that I didn't bother to think about and I haven't bothered to make sure it matches with their requirements?

What end users don't understand is the involvement in a quality product.

PM: this is our super fancy new CI/CD pipeline, it's the greatest. i expect you to learn and understand all this in no time.
devs: so i have to spend some more time on this topic because it's completely new to me and requires some learning...
PM: nooo, that's a super easy task with zero effort, my braindead hamster can do that in no time, so can i, and so can you! let's assign 1 story point for that.

~ 3 months latèr ~

also PM, after he has started developing as well: so i'm realizing there are many things that i have to learn, and it takes me some time. i haven't developed with C++ and <other tool stack> for a longer time. by the way, you guys don't need to check for any quality right now, we need to deliver fast. it's okay, when you have memory overflows, your code is completely crappy, poor architecture or memory overflows, it doesn't matter.

he even has a subtask for migrating his code from VS project to our new project structure, since he refused to learn our pipeline right from the beginning and created VS project instead. シ why is this a subtask? this job can be done in no time, my left vanishing twin named Klaus who has dislexia and hates vim can solve this task in 20 seconds!!!!11

(and still no PR, not even a feature branch in our repo)

I like js and node in general.
But there's this thing I hate about NodeJs...

The blogs. The goddamn blogs.

Every goddamn blog post. Is code. Dozens of lines of code.

Oh, so you want X feature? Just copy paste this shit.

I swear to god, blog posts are the source versioning system to these people.

What they should instead is
a) Create a package.
b) Add tests to it.
c) Present the package to the reader with some minimal code.

But I'm a getting a huge impression that node blog writers want you to copy the code in their post, paste it in your project, and be happy with it.

Now, I'm not assuming that every person posting in medium.com is a software engineer (and by engineer I mean an engineer, not some fuckwad who begs for github stars on dev communities).

The problem to me is that they fucking SATURATE the goddamn search results.

The same goes for finding an npm package for your need, because there are so many low quality packages it's saturated too, you have too plow this stinking pile of projects that have very low quality,
and there's not a really good npm finder out there. Half of them are dead, some look and load like shit, and npm search has a low barrier for good code.

Me on rails, OTOH "ok, I need this thing", I google that and I swear to [-∞,+∞] I find GOOD packages, well designed, no cookie cutter bullshit, no obscure marketing shit on the README.md, it is very clear what this shit does, and the api is designed for HUMANS.
and it actually takes very little time to know if there's no such package.

I don't have to read dozens of fucking my-fuck-blog.io (jesus christ, the io domain has become such a fucking joke, it got fucking abused to death, there are some cool sites out there using it, but my god, James H. Marketing likes to just absorb everything he can, and the internet was not going to be a fucking exception)

does all of this make sense?

I am a senior Android dev, and I have an old colleague (iOS senior dev). We work on the same project, but in every estimation session he pushes a lot on the lower side: he estimates 4h a task that normally takes 6h or 8h, and the reason is that he has no social life. Right after work he starts working again from home (I can see all his commits), he also works almost entire weekends. I would say he works as average 12/13 h per day.
I don t want to work extra time (unpayed).
About him, it is his life, so I don t care...but at the same time this makes me pressure. I care a lot about quality of code, and I don t want to sacrifice it just for catching up. Most of the people in the team know that he works a lot extra time.

How would you handle this?

A beautiful gem ticket from a manager today:

Title: "Check Stripe "Snippet APK" that might help for integration into the app to track pricing easily."

Alright, it's very clear this particular individual has no idea what they are talking about, but, I'll give them the benefit of the doubt and read the ticket description!

Description: "I think stripe offers some sort of snippet that can be implemented into the app similar to FB pixel. (I could be wrong here..) let’s briefly check this, if it’s of value for our A/B-Tests → e.g. if it makes your life easier = good otherwise it’s not important."

...

I might as well replace the management team with GPT-3 at this point.

Or even just a simple Markov chain; that'd probably be more accurate if you want to match the ticket quality more exactly of this ABSOLUTE PILE OF HORSESHIT WASTE OF TIME I GET FED EVERY SINGLE FUCKING DAY.

🤡

Fuck unreasonable deadlines. Just do your stuff as if you have the time of the world. Stop compromising the quality of your work and things are going to be done when they're done. Good quality stuff that's worth the wait.

I started to tell this to myself this week. For months now I took the bait that everything is urgent. And whatever crap management want has to be done yesterday. But.... Well... They pushed it too effing far.

Redo this module that took the former team about six months to finish. You have 10 days.

Well... What? Everyone is saying yes?... Everyone going full code monkey making no progress?

This is the moment I stop compromising and stop listening to your suggestions. I am going to do what I know how to do, the way I know it works, and I will not cut one corner based off your suggestions. I'm sorry, I've been dealing with this shit for too long already, and I don't want to suffer the consequences of degrading the quality of what I write anymore.

Sorry, long since my last post...

I have quit my job recently at DERP & CO.. The level of anxiety was already somewhat of medical severity.

For months I had been in a project that not only did not progress, but that it was getting worst day by day.

A bit of Context

November: "Dev, junior anon needs you to help him on the SHIT project because they are running out of time, it is mainly doing unit tests."
Well, the code was a mess, there was a LOT of copy paste and it was all bad quality (we talk about methods with complexities between 80 and 120 according to SONAR QUBE).
Dev: "Anon, you know this is wrong, right?"
Anon: "Why? it works"
Dev: after long explanation.
Anon: "Oh well, yes, from now on I will take it into account." And he did it / try his best.

Dev does the unit tests and do extra work outside of the reach of the sprint (y than i mean work after hours, classic) and alerts the boss of the mess.

December: After a project of approximately 6 or 8 months of development, the boss discovers that the junior anon have been doing everything wrong and/or with poor quality (indicating that throughout the whole development the quality of the code was NEVER checked nor the functionality).

Boss: "This is a shit. Dev, you have to correct all the errors and warnings marked on sonar", which are around 1200 between smelling code, high risk errors, etc.

Dev fixes something like 900 bugs... lots of hours...
Boss: "This still is all wrong, we have to redo it. We will correct the errors leaving something stable and we will make a new repository with everything programmed as it should be, with quality and all"
- 900 corrections later, now are irrelevant -
Boss: "Dev, you will start to redo it, anon is out on other project. First you must leave the existing one working properly"
Dev: "ok ..."

January: How can I correct the mess if the client asks for more things. I am just fixing the mess, doing new functionalities, and when I have free time (outside the work) I try to advance the new repository, poorly I must say because burntout.

Boss: "Everything should be arranged at the end of January, so that you can redo everything well in February."
I can't handle everything, it starts to fall further behind. Junior Anon quits the job.

February: Big Bad Bugs in the code appear and practically monopolize the month (the code is very coupled with itself and touching in one place sometimes meant breaking other stuff).

Boss: "It can't be, you've been with this since January and you haven't even started correcting this mess in the new repo"

Dev: "It is that between the new things that are requested and the bugs I cannot put myself with that"
Boss: "Do not worry, you will be helped by random dev if you needed. SPOILER ALERT: random dev is allways bussy. Not made up bussy, He had a lot of work by itself, but it can't help me the way I need it.

High anxiety levels, using free time to try to reduce the work left and gradually losing the taste for develop.

March: So far, not only do they add new things day and day, but now they want to modify things that were already "ok", add new ones and refactor everything in a new repo. I just did not see an end of this nonsense.
Dev breaks, the doctor says it's anxiety, so I just know what I have to do.
Dev: "I quit my job"
Cool Manager: "Damn, why?"
Explain everithig
Cool Manager: "Do you want to try if I can change you to other project or anotjer scope on the same project?"
Dev: "Thanks, but no Thanks. I need to stop for a while".

End. sry for long sad post and maybe poor use of English (?) Not my native language.

I've taken a year's break from university to work on projects using various languages. For the first half, I've been trying to produce as much as possible. Now, I'm taking my time and producing less. I've gotta say, I'm enjoying it far more now. I feel like I'm learning more and producing better quality code.

I was eating my oats happily when, suddenly, Boss called because clients complained data duplication in reports, and asked why I removed DISTINCT in the query. So, I stopped eating and obliged to answer the call because I so loved my work :) <3

How is it my fault now, when the QA just told me to make the data transparent and to not display them distinctly by name?

Been 122 days since my last post, since then I have been working on a game engine on Vala using SDL2 in my free time (Lol I have none)

Decided to put that on ice or just work on it when drunk (very common occurrence) and teaching myself C while working on a game or game engine, hopefully will have some quality rants inbound!

A (work-)project i spent a year on will finally be released soon. That's the perfect opportunity to vent out all the rage i built up during dealing with what is the javascript version of a zodiac letter.

Everything went wrong with the beginning. 3 people were assigned to rewrite an old flash-application. Me, A and B. B suggested a javascript framework, even though me and A never worked with more than jquery. In the end we chose react/redux with rest on the server, a classic.

After some time i got the hang of time, around that time B left and a new guy, C, was hired soon after that. He didn't know about react/redux either. The perfect start off to a burning pile of smelly code.

Today this burning pile turned into a wasteland of code quality, a house of cards with a storm approaching, a rocket with leaks ready to launch, you get the idea.

We got 2 dozen files with 200-500 loc, each in the same directory and each with the same 2 word prefix which makes finding the right one a nightmare on its on. We have an i18n-library used only for ~10 textfields, copy-pasted code you never know if it's used or not, fetch-calls with no error-handling, and many other code smells that turn this fire into a garbage fire. An eternal fire. 3 months ago i reduced the linter-warnings on this project to 1, now i can't keep count anymore.

We use the reactabular-module which gives us headaches because IT DOESN'T DO WHAT IT'S SUPPOSED TO DO AND WE CANT USE IT WELL EITHER. All because the client cant be bothered to have the table header scroll along with the body. We have methods which do two things because passing another callback somehow crashed in the browser. And the only thing about indentation is that it exists. Copy pasting from websites, other files and indentation wars give the files the unique look that make you wonder if some of the devs hides his whitespace code in the files.

All of this is the result of missing time, results over quality and the worst approach of all, used by A: if A wants an ui-component similar to an existing one, he copies the original and edits he copy until it does what he wants. A knows about classes, modules, components, etc. Still, he can't bring himself to spend his time on creating superclasses... his approach gives results much faster

Things got worse when A tried redux, luckily A prefers the components local state. WHICH IS ANOTHER PROBLEM. He doesn't understand redux and loads all of the data directly from the server and puts it into the local state. The point of redux is that you don't have to do this. But there are only 1 or 2 examples of how this practice hurt us yet, so i'm gonna have to let this slide. IF HE AT LEAST WOULD UPDATE THE DATA PROPERLY. Changes are just sent to the server and then all of the data is re-fetched. I programmed the rest-endpoints to return the updated objects for a very reason. But no, fuck me.

I've heard A decided (A is the teamleader) to use less redux on the next project and use a dedicated rest-endpoints for every little comoutation you COULD DO WITH REDUX INSTEAD. My will is broken and just don't want to work with this anymore.

There are still various subpages that cant f5 because the components cant handle an empty redux state in the beginning, but to be honest i don't care anymore. Lets hope the client will never find out, along with the "on error nothing happens"-bugs. The product should've been shipped last week, but thanks to mandatory bugfixes the release was postponed to next week. Then the next project starts...

Please give me some tips to keep up code quality over time, i cant take this once more.
I'm also aware that i could've done more, talking A and C about code style, prettifying the code, etc. Etc. But i was busy putting out my out fires, i couldn't kill much of the other fires which in the end became a burning building (a perfect metaphor for this software)

If you want developers to track of their hours (for grants etc) then that is fine.

If you require them in a to be in a markdown file in a repository then you are fucking up.

If you won’t pay for any quality time tracking software for your developer then you are an idiot!

I've found a job as a junior developer several months ago, but I really want to find another job...

I know, my knowledge and skills aren't superior yet, but I am tired of that feeling of being useless.. I constantly self-educate myself after work and university, but still, I often need to ask co-workers "where's this form?", "wtf is that", "how do I access this"... Plus, their projects are HUGE, but no matter how big the project is, there are 2 to 4 people working on each at a time. And 1 person may work on 2-3 projects. And we are usually late for deadlines :/

Also code quality is meh..
Me: Why do we implement it here?
Co-worker: oh, we don't actually use it, it's just to hide warnings and pass the test.

Holy shit, wtf, I've spent half day trying to figure out wtf is this and why is it not working :/

[Half question / half rant]

Would you rather work with a laid-back, humorous colleague who produces shit code and won’t understand advice for improvement?
Or would you rather work with someone who’s more serious, even slightly boring, but who takes quality seriously and is open to advice?

Yes I’ve worked with both types. Hands down I prefer working with the latter. With the first dude I’ll have good conversations and a good laugh at his puns and jokes. But at the end of the day I’m pulling my hair trying to make sense of his code and spending a shitload of time reviewing his PRs just to make sure he’s not fucking things up even more.

Fucking cant solve productivity problem. Since I was working as programmer, about 8-9 years experience, constant complaints about my productivity and some jobs even fired me for this. Only one job did not complain and I worked in it longest time but still I was worrying very often about my productivity. It is fucking annoying. Why others are productive and I am not. How the fuck to find biggest bottlenecks to know which to work on.
I know I am not knowing technology perfectly, and from time to time I get stuck and so I ask other people help, or somehow manage to find solution myself but it takes more time. But dont know if that is the biggest issue. Should I intecify my learning? I am regularly studying, and working with symfony about 2 years, so I think I should know enough to be productive even with those strugles from time to time. But maybe they are too often?
I have listened book "deep work" and basic thing I think from this is - to minimize disctractions and learn to focus very well. But to minimize like in this book, I should work alone in my room. And even then I would like each hour for few minutes to read some new or smth, which this book says is bad, but a lot of people do that and they somehow get away with it. Plus if I work alone in my room, my social skills might get worse, and we all need social skills, even programmers.
I so envy to others who know how to be productive. I would hate if the only thing to be more productive is to reduce quality of the code, make more bugs. THats fucking cheating system.

So I got this new job as Java developer, the people are really great but is the kind of companies that only takes care for fast results and not for code quality.

Because this I have to deal with libraries updated 4 years ago, classes with 8000 lines, methods with 500 lines, a WHOLE lot of work arounds because there is no time to really fix the issue unless it affects directly the customer (something not working or being really slow) aaand we use fucking svn.

Some of this practice's they know and encourage it (+1000 lines classes for example) and every time I try to talk about good practices in the code everyone seems so interested but there is always no time.

Sooo I will stay here for at least two years, I hope I can make a change for good in their code smells.

I gotta say, I actually admire the work that content creators must go thru to make quality content.

So as I stated before I’m working on YouTube channel, under the name “TheSoftwareSage” ... to create tutorials and a way of me teaching software the way I believe it should be taught, not how the mainstream methods of today are.

Bottom up approach rather than top down

(Must start with a firm understanding of the foundation.. and build upon the knowledge as we go thru the layers of abstraction but the key concepts must be understood first)

Anyway, I’m working on this in my spare time and I was not aware of how much effort I would actually need todo this right haha. At first I figured I’d just screencast a monitor and have a ppt or text editor or terminal open and that stuff and just do it.

As In person with my interns I never have “planned” lessons or content is all impromptu based on the need at the time and I just go with it, with their computers and a whiteboard lol.

I was wrong for video recording lol... maybe it’s OCD... or perfectionism, I’ll make a video, review it like 5times and then be like shit I forgot to mention this or that or I didn’t like how I explained this or that
OR
I keep worrying too much about colors, and sound levels and quality and transitions and video angles and all this other shit.
And then post editing fuck.... I’m about ready to say fuck it and “do it live .. one shot” and just upload the end result.

I guess this would be in the content world similar to our “paralysis analysis” notion.

Only company that I really "hate" is Abstergo haha.

All others have their up and downsides I guess....

Microsoft:
+ Xbox One
- Windows

Apple:
+ iPad Mini (don't know any company that produces such high quality but very small tablets... Therefore I still use my ~6 years old iPad Mini 1. (The battery life is insane! After all this time it still lasts about 6-7 hours!)
- The new iPhones. No innovation. Just making money.

Samsung:
+ TVs
- Smartphones (a few crashes here and there, kinda ugly, explosions!)

LG:
+ TVs (webOS is the shit!)
- Heard the Smartphones suck, not sure

And so on....

Building an interface for a client between industrial power quality meters and a database that serves a webapp of data.

Client had heard of a way of sending data between meter and raspberry. From some manager in a big firm.

Currently we where using modus to connect the meter to a raspberry. This method was tested and proofen to work. Both devices could talk to each other in modbus.

Client kept demaning to use mbus, and was nog listening to any reason because the firm suggested it. In the end we end up going modbus to mbus to send it to the raspberry. There the mbus was converted back modbus. Because the meter could not communicate in mbus.

Really weird experience to program something so useless. But protesting about it was going nowhere and taking more time than the changes would take to implant.

“We mob every thing so that means we don’t need pull requests, because by the time the code is committed it’s had plenty of pairs of eyes on it”

Well, I beg to differ.
Today I read through some of this spaghetti mobbed code to look into a performance issue. Wasn’t supposed to but bored stiff so I ‘went dark’ and did it without the mob.

After about an hour I figured out it runs a few lines of dubious code and if there’s an error it tries many times over with an exponential back off.
And each run of the methods will fail for sure because of how it’s written.
Someone must’ve seen this problem but instead of realising it can never work, they’ve wrapped it in retries and back offs.

So many back offs and retries that it just sits there doing this for 25 minutes.

But yeah. The mobbing works great guys, keep churning out this quality code. 😂😂😂
Can’t wait to see the back of this joke job.

The best kinds of comments:

/**
Gets user CC info datas.
*/
public Object getUserCCInfoDatas() {}

If you really want to outdo yourself:

/**
Gets user CC info datas.
@param someshit Outdated docs ftw
*/
public Object getUserCCInfoDatas(String unrelatedToDocAbove) {}

Honestly, no documentation is better in some cases. At least I can't be angry about their shitty quality... And they don't waste my time.

So I spent over 200 hours recovering a raid array because the the business that hired the company I work for tried to do all the work in house. Now I'm to the point of trying to quote a new server setup to the company because the last one got hit by lightning. My quote $8000-$20000 in just hardware alone. If im going to do this I want to do it right. Twin servers running xenserver holding virtual machines with a high-quality Nas to hold the virtual machine. Then have the vm's being imaged to two off site backup devices in two different locations and a cloud backup. My boss comes in after me talks to the guy in charge and tells him all that is needed is one server holding all storage on it just like the last server that died and one off-site backup for $4500. How stupid can someone be who has been doing this for over 20 years? Oh btw the software running on this server will be 911 dispatch, jail records and the database for fine payments. The sheriff making the final call me and my boss are meeting with him tomorrow if my boss tries to undercut me I'm going to tell them both that if the same shit happens next time they can spend the time themselves trying to recover stuff because I done the over 200 hours in just short of two weeks.

I've been a Macbook user for over a decade, after the initial disappointment of the 2016 MacBook Pro release I decided to move to a PC, against my better judgement I decided to buy a new Dell XPS 15, after reading all the reviews praising it's build quality and performance + it seems to have good hardware for Linux compatibility.
Soo much regret, I couldn't be more disappointed, it's such a piece of shit, I admit I probably got a bad egg, but dealing with Dell support is like pulling hairs from my testicle sack. If I have to pay an extra $500-$1000 on my next laptop for an "Apple Tax" to get a product that has been through proper quality control and has awsome customer service so be it, last time I try something new.
BTW I'm not a PC hater, I just wish more companies made high quality products.

A client asked for a tool for his website. So I built it for him and he was satisfied with the thing, cause it did what it should. Nevertheless I was not, because it kind of had a messy backend. I made it working and charged my time. Now I am wondering if I should rebuild the thing to satisfy my code quality for free, or just keep that thing as ugly as it is....

What your opinion on this?

Last week I received an invitation to lead the development of a e-commerce redesign, replatforming and data migration. I was excited to work on it, and started the analysis and planning, glad to spend time focusing on quality. But Murphy's law is never asleep - this Monday, I was asked to speed things up and reduce a 4 month project to 1 week.

I'm a junior dev, been on placement a year.

I get tasks done mostly on time, my pull requests are merged, yet I still feel like what I'm writing is seriously under quality.

What point will I stop writing code that isn't good enough to not be stressed about? 😷

I take this chance to post my setup while spending some quality time with the pi!

When I was about 10, I used to read these magazines with code listings for programs, and the only things I really understood were these text adventures that I imagined to be of Zork-like quality (gasp!). In reality, it was more like the choose-your-own adventure books of the time (which were actually pretty cool, and had pretty tight memory management). At one time, on a vacation somewhere in the eighties, I got tired of playing in the river with my friends and instead opted to continue writing lines of BASIC in a little paper notebook, inside my parents' car (at 34 degrees C), trying to perfect a storyline about my little brother and his pet dog he got for his most recent birthday, fighting the cat empire etcetera etcetera. Weird looks, good times.

> do you feel sorry for freelancing contractors
> whose previous client abandoned them
> they ask you to help them fix some trivial bugs in the shitty code
> you believe you can change the world by going overboard by also improving the code quality, along with fixing the bugs
> initialize an empty file where you'll translate the shitty code into a more organized one
> start creating variables and generic functions which can be used in a modular and organized fashion
> meticulously document the first function you write
> realize this is not worth your time
> insert some glue code into the original code which fixes the trivial bugs
> glue code has hard coded values so it adds to the shittiness of the code
> submit the work
> get $$$

I think JavaScript is great actually

Though I don't like the community

But that's not saying much, aside from maybe c++ people (who I don't actually understand so maybe that's what's going on there) I don't seem to like any communities

Mostly because they're wrong and fight over irrelevant things and don't realize they're wrong so they just keep going wrong and it makes me cringe

But javascript is nice because it's intuitive, and if it isn't intuitive to you right now just look into the thing and it'll be a second language to you later... Isn't that a skill issue?
Easy to start hard to master, perfect difficulty curve. Exploits that sunk cost fallacy. It isn't overwhelming either you only run into the edge cases slowly over time.

But there can be a point made that an easily accessible anything is just always going to turn into a cesspool because unskilled people keep contributing and thinking themselves experts, so it over time reduces quality of secondary tooling =[

Was going through old photos from university time and...I present to you the result of deadline + lack of sleep + boredom + shitty university project because somebody decided that CS folks needed to learn webdev in old ASP.NET.

Yes that is one query. I wrote the entire thing out as a string in my C# program in one go and tested it by running it from the program. Must've worked properly because I got them grades so eh. I recall I had one nested seven levels too (this is just 5) but I can't find a photo of it. These two queries did all the business logic. Yeah.

Apologies for the poor quality photo of the screen, I don't have the code so no screenshot, this is just from my photos archive

Product Management thought of automating an entire legacy product so they funded undisclosed amount to program management who in turn hired >20 contract devs managed by architects and dev managers with zero functional or technical knowledge of product and who in turn went ahead automating the product in selenium, end result of which was an useless automation framework with lot of browser specific dependencies and whuch could run only on one setup environment and migrating test cases to another environment and running is almost impossible and tyrannical to configure. The automation test cases are highly disorganized with all generic setup, DB configurations and business case test data mixed up in same config files and which need to be rewriten every time ported from one environment to other.To add misery to my woes as a dev working in that product I was told to utilize that framework and enhance the quality of my code by writing inline automation Cases for the same. I am left speechless thoughtless and emotionless after that decision.

Working on codebase of a 20+ year old system that the company I work for bought five years ago and in that time there’s been no refactoring, no security updates, no attempt to create automated testing (there is none), new features have just been built on the codebase with no regard for quality and it’s just spun into the horror cesspool that it is today.

I joined one year ago and I’m slowly refactoring the codebase and updating it to get it to a more modern codebase, cleaner code, faster load times and creating a ton of dev documentation so the devs in India can start getting into best practices and start producing quality code.

For the first time apart from Data Structures and Algorithms, there was a Machine Coding round where they asked me to create a small app using any language without data persistence or GUI, to see my code designing ability, LLD, code quality, whether I can implement OOP and write modular code and to see how extensible my code will be.

I did well.

!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.

Don't you just love customers?

It al began when they showed us the flyers they were printing for their new products, an some one at our company who doesn't work here anymore had the brilliant idea of copying it to their webshop, as a fucking gimmick... Ooohh man the customer didn't seem to understand it was only visually

They wanted the 3d layering effect to be dynamic, so each product would have its own with custom colours

So it was made

A few weeks later they didn't want the informational text, they wanted links to each product that the layer uses

Sounded like logical so it was made

Again some time later, they noticed that the layers were not textured, but just plain

I argued against it because it would add unnecessary loading time for some 300 by 400 px element but they insisted

So they got what they wanted

A few days later they said that the textures were of low quality, and that we had to create ones with higher quality

Again our management said, yes

We made ~ twice the size of the element in image pixels to create a higher definition image

Then the customer wanted that the layers should change based on some selection menu above it

(At this point we realized that it would no longer be just a fun little gimmick)

So we tried to refactor/rebuild it to remove most if not all the hacks we did just to make the customer happy, that took too long for them (the customer) so we had to revert back to the hacked together version because otherwise we would not be done on time (commanded by management)

But again, we ... I say 'we' as in the company but realistically I've been the only one who has worked on the fucking abomination

But I digress...

A few stupid requests later, some layer images are almost fully transparent PNG images that are almost 1mb in Filesize each (some products have 5 or even more layers) and the god damn thing now has to account for optional layers...

I AM FUCKING SPENT... I'VE JUST CAME BACK FROM VACATION BUT I ALREADY NEED IT AGAIN... FUCKING WORKING 60 HOURS A WEEK JUST TO KEEP ONE CUSTOMER HAPPY WHILE OTHER PROJECTS BREATH ON MY NECK

I am sick of misrotated videos.

Sometimes, the phone camera software saves a video vertically because the user hits "record" before the software has detected that the user is holding the smartphone horizontally, because the software stupidly launches in vertical orientation by default.

So the software wants the user to wait until it has finally detected horizontal orientation, which causes the user to miss out on a moment.

How about the camera software actually saves the video in the orientation it was recorded in for the most time, rather than only the beginning of the video?

If I can think of this idea, billion-dollar companies surely can.

In the meantime, misrotated videos can be fixed using this ffmpeg command on Linux or Windows:

ffmpeg -i input_file.mp4 -metadata:s:v rotate="0" -c copy output_file.mp4

And if the phone was held with the home button to the left side:

ffmpeg -i input_file.mp4 -metadata:s:v rotate="180" -c copy output_file.mp4

This solution is superior compared to using -vf (video filters) because it only touches the metadata of the video. No re-encoding. This means no quality loss and no CPU/GPU power needed to process the video again. It just passes through.

Time spent on devrant:
50% trolling
25% challenging people's worldview aka trolling
15% making witty remarks, and more trolling
10% looking through my notifications to see wtf @Wisecrack said
<1% posting "quality" content

Many "purists" love to piss on JavaScript and web development. And to an extent I can understand ostream’s frustration with these people.
It’s easy to criticize because yes: many web projects are indeed shit.

But I’d like to argue that the reason why so many of these projects are crappy is because of bad management:
- unrealistic deadlines
- no clear testing strategy
- or no testing at all because of deadlines
- no time allotted to catch up on technical debt
- etc.

This type of management is far more commonplace in web projects because things need to get delivered quickly and if they’re delivered with bugs, it’s no big deal as lives aren’t at stake.

I doubt this type of management is tolerated in projects where you’re working on software for welding machines (for example), where the stakes are that "you’re expected not to kill anyone" (to quote demolishun)

So in these types of projects, management can’t tolerate anything much below perfection and thus has to adapt by setting realistic deadlines that take into account the need for quality processes and thorough testing.

If this type of management was more common in web development, I can guarantee that web applications would be much more reliable and of better quality.
I can also guarantee that poorly managed non-web projects as outlined above would be just shitty as many web products.

My point being that’s it’s really DUMB to criticize fellow devs that work with web technologies on the basis that the state of websites/web apps is a mess. It just so happens that JS is the language of the web and that the web is where things are expected to be delivered quickly (and dirty … but we can fix it later mentality)
Stop acting like you’re the elite. I have no doubt you’re super smart and great at what you do. So be smart all the way and stop criticizing us poor webdevs that have to live with the sad state of affairs. ❤️

Anyone here making big bucks working for a small company? I've interned at startups and worked full time for fortune 500's, but I'm considering looking at smaller companies in the future just because the corporate environment kind of burns me out. What's it like being a senior level developer for a smaller company? Is the money typically there? And in your experience, what about quality and expectation of work? I would love to have some more say and passion into what I'm building and take home a big chunk of what a business earns but I don't know how realistic that is.

I'd also like to start my own e-commerce company but as a web developer with 0 business / marketing experience that seems far off lol

I'm so sick and tired of people feeling threatened when improving upon their shitty code! I'm here to do a job and I enjoy my profession.

Don't take that away from me by wasting my time making me say every fucking time that I come from a good place and that I just want to provide a better solution AND not create fucking mess that will have to be rewritten when some ninja bugs occur because of completely unmaintainable crap nobody can understand. Holy shit!

I couldn't care less if you're 10 years in the company. I see that all the good devs left after dealing with your shit every God damn day.

I'm not here to deal with your insecurities and couldn't care less about pointing fingers! I just wanna do better and not write same level of quality over and over again!

You're not getting bonus points from me by sitting on your ass all day and half-assing everything you do with some lame ass excuse.

So no LGTM from me when it's utter error prone shit!

So if you don't wanna help, just get the fuck outta my way and don't waste my time! Jeeez

To be honest I forgot completely about the ducks and was kind of disappointed to see them, don't understand me wrong, its a great addition to the shop (especially to support devrant more when buying them and I will probably do too) and trogus (wow it's pronounced t-rogus) deserves a lot of respect for going through the very hard process of developing it, getting somebody to do a decent quality result etc. but I was hoping for the new site that got hyped up some time ago or some update to the app that fixes design issues on phones that have 2k resolution and no statusbar and more. ("just open a github issue" - I don't have one right now and it didn't get much attention anyway, since I am in the niche of people with those kind of setups, most people it seems have phones that can even barely run the app lol). The login still pops up each time you visit the site (basically just click it away, but it's rather annoying to have it pop up), it's nowhere near to the original app (although the native app is written in some sort of wrapper anyway?) - especially what comes to options, customizing, deactivating things, posting into categories (newest feature), getting notifications etc

There is some community builds that try to recreate a better desktop experience, but sadly fail to do so (sorry to devrantron and others, but what the fuck were you thinking when you rounded only the top right and left corner?) - since they always have something that is just thrown out to "be there" or design fails (which devrant just lacks and looks good across the board), that makes me rather cautious if that program doesn't send my credentials to some african prince. ("just look at the sourcecode", yes I have better things to do, thanks)

I could just create my own build, having to reverse engineer the whole website and app (granted, most of it are just api calls), but I simply lack the time (so I understand why my mentioned problems aren't getting really any attention or can't be implemented that fast, yet still its somewhat bugging)

I have listened to the Q&A and I know you guys are working full time at for example adobe (amazing that you both have time to be putting it towards devrant), so its not as much of a rant, just wanted to get out my disappointment about the event I felt personally. Still nice to have seen you and talk with the community a bit (although the time I feel was picked more towards your US audience rather than EU?).

I was talking to a friend about the current state of machine learning through tensorflow and commented about the use of Javascript as a language.

He discarded the idea as he views Javascript as something that should only be used as a frontend technology rather than something to build backends or deep learning models.

I am thorn. I have always liked Javascript but will admit that I have used it mostly in the area of front end with very few backend instances(i did create a full stack intranet app in Express once, major success for the application it was hosting, it was a very basic api which had its own nosql db with no need to interact with the company's relational data, it was perfect for the occasion and still help maintaining it from time to time)

My boi states that node's biggest issue has always been npm and the quality of packages. I always contradict those statements by saying that if one uses community standards and the best packages then one does not need to worry about the quality(i.e mongoose over some unmaintained mongo wrapper etc)

I sometimes catch myself finding that my way of thinking adapts better to JS than it even does Python (which is his preference for deep learning) and whilst there are some beastly packages for python in terms of quality and usefulness such as matplotlib etc that one can do great things with the equivalent JS.

I mean, tensorflow.js came from the same wizards that did tensorflow (obviously) and i find the functional approach of JS to be more on par with how we develop solutions.

I am no deep learning expert, and sadly I have no professional experience with machine learning. But I venture to say that we should not cast aside the great strides that the JS community has done to the language in terms of evolution and tooling. Today's Js is not your grandaddy's Js and thinking that the language is crippled because of early iterations of the language would be severely biased.

What do you guys(maybe someone with professional experience) think of Js as a language for machine learning?

Do you think the language poses something worth considering in terms of tooling and power for ml?

It is incredible how Google got big with good webdesign and now manages to build the shittiest frontends.

It's not enough that YouTube is super slow and breaks every other time I use the "back" button in the browser. When it only forgot my language & theme settings every couple of months that was still too high quality for Google's dogshit standards, so now they made another downgrade: Whenever I set another language it immediately resets it to the language Google thinks I should speak, and at the same time resets the region to where Google thinks I live. Oh, and I have to disable autoplay for every video individually now cause who the fuck uses cookies nowadays right?

Do they also change the language if I travel to another country because those fucks never leave Silicon Valley and can't comprehend that concept?

Google is the Microsoft of web design.

Remember, the more "cutting edge" and "thousands of clients" a company has is inversely related to the quality of documentation they have on their APIs and software solutions.

I don't give a fuck about your pretty examples, show me which FIELDS can take which VALUES. It's that simple. Instead, I'm wasting your company's and my own time by spamming support for what should be basic questions clearly outlined in the documentation.

Node: The most passive aggressive language I've had the displeasure of programming in.

Reference an undefined variable in a module? Prepare to waste your time hunting for it, because the runtime won't tell you about it until you reference a property or method on the quietly undefined module object.

Think you know how promises work? As a hiring manager, I've found that less than 5% of otherwise well-experienced devs are out of the Dunning Kruger danger zone.

Async causes edge cases and extra dev effort that add to the effort required to make a quality product.

Got a bug in one of your modules? Prepare yourself for some downtime because a single misplaced parentheses can take out the entire Node process, killing unrelated pages and even static file hosting.

All this makes for a programming experience that demands much higher cognitive load, creates more categories of bugs, and leads to code bloat/smell much more quickly than other commonly substituted languages.

From a business perspective, the money you save on scaling (assuming your app is more compute efficient under Node) is wasted on salaries and opportunity costs stemming from longer dev time, more QA, and more frequent outages.

IMO, Node is an awesome experiment, a fun language, a great tool for specific use cases, and a terrible fucking choice for an entire website.

What the hell has happened to Hewlett Packard?
They used to make the best notebooks around. 10-15 Years ago, basically all notebooks my family bought were from HP. These devices lasted for at least 6-8 years each.
Now I have a fucking expensive OMEN series notebook failing after 2 years with the most embarrasing hardware problems: Once a shielded piece of plastic from the bottom broke off and made a short on the mainboard, next time the way too thin power line that goes from the power plug to the PCB was placed alongside a sharp metal piece that damaged the isolation and again produced a short. When the display is moved, the webcam disconnects, which is also a hint at the production quality.
From my daughter's HP notebook the Display just broke off after like 18 months of use. When we brought it to service I asked the guy whether this happens a lot, he was like "I have 6 other notebooks of that type with the same problem in repair right now". After a repair that took forever because they couldn't get the proper replacement parts, the integrated webcam has died.
Never ever going to buy anything from this shitbrand again.

Set some dev goals..

TLDR: spend less time at work coding

No, really..for what I do at work, I am happy. Would like to learn more recent stuff (partially stuck with vb.net), but I don't even know where to start googling.. sooo... get more free time I guess to figure this out..which is a dev goal on it's own too, come to think of it, this translates as don't spend so much time at work coding.. and spend some of it learning new (dev related) things outside of work..new/different js frameworks, python (been fixing/adding some code here & there, but never learned it properly & to check it's full potential, I heard it is awesome btw), read up on algorithm time costs (learn how to fuckin spell this!!)...

And kinda dev related as I will have to spend less time at work is to get back in 'sort of' shape and climb (more)..and spend more quality time with my husband, who is too good, totally supports me & my work, so I never get to hear him nag I was working late, which leads to 'stop working so long' goal I rly need to get in order or I'll burn out again, and I'm bitchy and horrible whe BO..and we don't wanna see that again..

Sum up: work less, learn new things, climb more, be happy/content.

I too got my $1 unix sticker pack (thank you very much whoever posted this by the way) and thought posting a picture of them would be redundant
First thing when I brought them to work to show them or to my colleagues I stepped out of my car and they all fell to the soaking wet ground (it was pouring down at the time)
Luckily they're of very high quality and still intact 😊

Discord...

Okay, I have a lot to rant about discord, but today, exceptionally, to the point.

I have my dedicated server. It has uptime last 3 years better than 99,99% (was down 15ish minutes for maintainance and RAM upgrade and like 10 minutes down becouse hoster's generators failed to trigger when there was outage)

This year it was up 24/7/365.

Why am I saying it?
Well, my TS3 server is up 100% of time this year. Yet still everyone moves to discord and suffers brutal audio quality and audio lags, and outages like right now. Its not first time this year and recently discord was acting up before. Today they scored bigger downtime than my dedi server (thats not redundant, not distributed nor any fancy "uptime helpers") last 3 years.

Why the fuck people prefer discord to ts3 other that it allows to upload images more conviniently? Okay, it looks nicer, and is like 10 times heavier on machine, but other than that? Its beyond me.

E: fix typo
E2: fix typo

Today I finally experienced the power of something I learned in university: propositional and predicate logic.

Many developers I know think that such education is useless. Well, today I have proven that it is very useful. On a day to day basis, working on banking software, complexity in purely logic is very low. However, we have a screen that must show or hide elements based on some input values and conditions associated with certain elements. How hard can that be, right? Well, there are many variables to take into account and as such it's absolutely not trivial.

This screen didn't work properly and maintaining the code is hard as there is a lot of logic to show/hide, enable/disable things and so on. After quite some time and attempts by fellow developers, I decided to refactor the whole thing. I'm responsible for the quality of the software and it was quite degrading, so I had to do something.

In order to get things working properly, I defined collections of constants (ui elements) and predicates. Then, I defined for which element what predicates must be true, in order to hide/show, disable/enable etc. I then translated these predicates into code. And guess what? It works! Of course it works. It's logic. But I'm very pleased I finally could actually use some of all the math I studied!

A lot of people have some very unrealistic expectations when it comes to cheap technology. You just can not expect to pay bottom price and get high quality results at the same time...

My colleague told me today that companies with shit code quality, complete chaos, no tests of QA of any kind, and poor security practices still make loads of money and are extremely successful so it's all a waste of time.

I detest this idea and I refuse to work like that anymore. But I also think he's right :(

As a new freelancer I didn't have much clients , so I paired with a web designer +10 years exp. who work with me as a pm and that was a bad decision.
Although I am a back-end dev , half of the projects were frontend/WordPress theme (less price than back-end projecrs) - so 30% of the projects were cancelled .
sometimes I receive project's which have requirement, like magento, I don't know anything about ,
I tried to push myself but I burned out after six month.
he deals with clients, partner with other companies ,and I don't know anything about the terms.
at the end I was like an employee without any benefits from his company .
moreover I get my money after 45 day!!!
and not all my money .
this is a project I work for another company through him
A requirement for mobile back-end server was integrating with parse and that was my first time working with Facebook parse so ....
after two weeks ..
we received email from parse that they'll shutdown their service after a year .

so we moved to Amazon sns again my first time working with aws .
at the end I can't charge for extra money but my pm became a gold partner for that company .
the only thing that made me hold is that I need some high quality projects for my c.v.
-----------
he didn't show on hangout because I need my money .
this will be my last project with him.
wow I write too much ... I feel better now .😥

!rant

I've always been wondering why do tech companies need everyone to have a strong grasp of algos and data structures?

I've been coding most of my life but didn't get a CS degree so ended up in IT but I kind of want to get into a tech company as my thinking is the quality of code much higher (I spend a lot of time cleaning up other people's code and prod issues over the years...), I've been learning Algo/DS but when I see those technical questions on CareerCup, I go WTF.... it's this the kind of problems you guys do every day?

Have few close friends, not a swarm of people.
Saves time.
And keeps strong bonds with people that really matter.
Spending some "quality social time" is more valuable than shitload hours of fake fuckery with dumbfucks.
Just my opinion.

I cancelled prime a few months ago so when I was doing BF shopping on Amazon yesterday, delivery is now 1wk instead of 2-days.

And shipping apparently is $9 if you don't meet the $25 minimum and manually select free shipping; I remember it was $6 before...

So a few thoughts I had:

1. Amazon really must need the Prime memberships to cover all the shipping costs since it is now a pain in the ass to get free shipping on the checkout page.

2. Americans really want instant gratification? Waiting a week is that painful?

In contrast, stuff from China take about a month but are much cheaper

3. The only thing that's worth buying via Amazon now is electronics and stuff that are fragile... And food that's on sale because they have to uphold quality

4. Lucky for me, I get 1 week shipping, I have more time to cancel orders... Which is what I actually did

I spent about an hour writing my own password generator at work... (And probably my item password safe) because my company doesn't allow using Keepass...

But require super complex passwords... That need to be exactly 8 characters...

And they expect us to somehow think of and remember them... And change it every 6 months....

As a developer, isn't it a given that if we can't have something, we'll just build one ourselves... But one that is lower quality since it is adhoc and with by a single dev... That doesn't have time or the experience of a domain expert...

They also blocked GitHub/Sourceforge so I can't just download from my own repo... And basically need to do it on company time... For better or worse.

The cool feeling when you see your static analyzer that compare previous version and future release and code quality is improved.

At the same time the bad feeling because you was the same dev that made the previous version.

Following my first rant, my boss had the brilliant idea of running the old and the new architecture in parallel. I had advised that it won’t be ideal since the same Scala code was ingesting into 2 different Kinesis streams and one was running an old KCL written in Java where as other was consumed by a Firehose delivery stream(eventually we will be ingesting it into Firehose directly). I had told few manual + automated tests on Code as well as from a functionality of the new architecture and a set of tests for checking the integration of the new Producer code with Consumer.

The statement I got from my boss was “This is the test, we test it on production in parallel”. My boss had a brilliant idea to fucking test the new code on the production directly but running them in parallel without accounting for undefined behaviour it might cause in the current production system. I mean my boss should get a Nobel peace prize for shattering our mental peace.

Anywho, we started the deployment today at 5AM in the morning. I had all the aws services deployed. Was just waiting to deploy the new Collector code which we did at 5AM. Immediately after 5 minutes the system went bonkers, there was fire, blood, demons and I was smoking a cigarette with the biggest “I told you so smile” on my face. I’ve just written an email to my boss and have told him calmly that “Listen motherfucker, 90 percent of the software companies aren’t idiots to focus on testing and quality. We need to start spending time on testing and quality else we’ll again be in the same soup after few weeks again”.waiting for his reply

Fuck,

I've been charging everything with the oculus quest 2 charger because it's very powerful but it just blew up my headphones. I did this often before but this time was a whole night.

I hope I can still get this great headphones, it had such good volume & bass. It's the cheapest Fresh & Rebel but the sound quality and battery is great

Everyone talks about quality, but they don't know what it means/ don't want to invest the time to do things right.

You would think that one might get used to the following scenario, but it still pisses me off every time it happens. I'm getting a design created by the customer that is specific to a pixel-level. The product I create in turn is very close to a 100% match visually and functional. And then a few days later, the work already done, I get renewed versions of the same designs. Just like that. With all those nooks and crannies replaced and new ones added, as if it didn't took time, effort and experience to make them functional in the first place. And no one blinks an eye. Not the customer, not our project managers. So after having me built you intricate card board house, you just smash it and tell me to rebuild? It's not always a huge deal but it happens so often and I guess it's part of the "customer is king" mentality, but it's bullshit. If the customer hands in a final design, then that's it. Any changes afterwards need to be paid extra. Otherwise it feels like I'm wasting my time and those changes will not get the same quality treatment for sure.

Bootcamps get you up and running in coding quickly. If you are a programmer, companies are only interested on how quickly, error free and cheaply you produce marketable output. Bootcamps enable this.

More or less you are not more than a former assembly line worker putting parts on a car platform. Your value is not very high as you may be exchanged at any time at their will.

Nevertheless, you can earn money quickly. You trade in your youth and time which might be a dead end in the long-term. Trends go to machine learning, artificial intelligence. They will not need Bootcamp people and code workers.

It is better you set up Bootcamps and sell them versus absolving this. Like selling shovels during the gold rush, but not working in the mud of Alaska by yourself.

Your choice is: Making quick money, which fades anyway; or striving for the long-term future proof career.

C/S degrees from Technical Universities of reputation give to you the right direction under a strategic consideration. Companies which pay well, or freelancing with a solid acknowledged background, will always look for top graduates. People from Bootcamps are just OK for hammering assembly line coding. Even worse with SCRUM in one noisy room under enormous team server pressure controls, counting your lines of code per minute, with pale people all around. And groups of controllers never acknowledging nor trusting your work.

To acquire a serious degree, a Bachelor is nothing. Here, in INDIA, Bachelor now is what a former high school grade was. You must carry a diploma or Masters degree combined with internships at big companies with high brand recognition. This will require 4–6 years of your lifetime. You can support this financially by working part-time freelancing as making some projects front- or back-end web, data analysis and else.

Bootcamp people will lose in the long-term. They are the modern cannon fudder of software production.

It is your choice. Personally, I would never do Bootcamps. Quality and sustainability require time, deep studies and devotion.

I haven't had an actual burnout ever since I started programming 6 years ago, maybe duo to the fact that I don't accept more than 2 projects at the same time, and I request a minimum deadline of 1 month for any project.

that said, I had to offer the clients something in compensation, basically lower prices and higher quality applications.

so i guess the more you give the more you earn?

I was thinking about the problems one of our clients faced with the launch of their project the other day, because things were rushed, stuff was omitted and in the end they could not meet the launch date, and I started making a list of hard lessons I learned over the years that would have helped them avoid this situation.

Feel free to add yours in the comments.

- Never deploy on Friday
- Never make infrastructure changes right before a launch
- Always have backups. Always!
- Version control is never optional
- A missed deadline is better than a failed launch
- If everything is urgent, nothing is important
- Fast and cheap, cheap and quality, quality and fast. Only one pair at a time can be achieved
- Never rush the start or the end of a project
- Stability is always better that speed
- Make technical decisions based on the needs of the project two years from now
- Code like you will be the only maintainor of the project two years from now. You probably will...
- Always test before you deploy
- You can never have too many backups (see above)
- Code without documentation is a tool without instructions
- Free or famous does not necessarily mean useful or good
- If you need multiple sentences to explain a method, you should probably refactor
- If your logic is checked beforehand, writing the code becomes way easier
- Never assume you understand a request the first time around. Always follow up and confirm

There are many more that should be on this list, but this is what came to mind now.

Lol so we had a meeting where basically the entire dev team got shat on for everything always taking too long... Now, I know a .lot of us suck at estimates but if it's all the time then do you think maybe we're not getting the best quality info to wok from?

Then they revised the WFH policy to 3 days a week in office. AND got pissy about the hours.

so I ask you all what are you hours?

So in our last retros some of my colleagues suggested to (forced) limit the number of lines per method in order to "maximize our code quality".

In the one hand I can see the benefits of this, such as easier testability when having more sperate testable blocks of logic.

But on the other side their code contains lots of such one or two lines private methods which get most of the cases not more than one time called. (And which I then can't even test separately)

I don't understand how this should help...
Is this really a thing? Am I just not "clean" enough?
(it's c# btw)

A while back I was learning web development so I could create web apps. I'm by no means any good at graphic design and whatnot, so every time I'd make a page to rig up with some JS I would get really frustrated with trying to make the page look decent and professional (not professional quality design, but usable as an application in a professional setting), even with bootstrap.

Does anyone have tips for getting over that hurdle? I want to learn, but I get discouraged by my graphical ineptitude.

Someone on WhatsApp asked me did I like the new update or not ?
Well here is what I replied,
WHAT THE FUCK ?! NOOooo ! already there is Snapchat whose USP is this feature, Snapchat is Snapchat, then they introduced this feature on Instagram that's ok...but WhatsApp should be WhatsApp.
ALL I WANTED IS A SIMPLE PLAIN MESSAGING APP, THAT'S IT !

Now it's wasting my time more, earlier I just used to see Instagram & Snapchat stories in my free time BUT now !? I will see these fucking stories again here on WhatsApp too... BECAUSE I can't help it, it's in our human mind psychology too, we are curious beings, we are somehow bound to open that Status Tab when we will see a green dot ! If it's not true SEE THE NEWS ! NASA just found a whole new Solar System just ~40 light years away ! YES we are curious, we explore, we invent things.

I hope they will roll it back, but NO the ugly truth my friend is people will rant about and forget, and we will end up using it too, hate this seriously ! for instance the new iPhones have no 3.5mm audio jack, WTF ?! well say goodbye to my favourite ear buds ! and buy these FUCKING NEW Monstrously over priced bound-to-buy pair of earbuds if you need high quality audio out.

AND are we bound to be slaves and continue using these features because everyone else is doing so ? NO ! I will use whatever I like the most, I will go back to the roots, may be use those old school IMs and may be ask others to join it.

Today I read a great article on mutation tests, how to use and why they are important. It looks like a great thing, but...
I have never wrote any unit test in any of my jobs. Nobody in my workplace does that. And now it seems like 100% test coverage is not enough (I remind you, that I have 0%), they all should mutate to check if the quality of unit tests is high.
It seems that I'm left behind. I played with tests in my free time, but it seems the more you write them, the better you get at it, so I should be writing them in my job, where I code most of my time. Not only that, of course, I would also want to ensure that what I'm working on is bug-free.
Still, it will be impossible to introduce unit tests to my project, because they are novelty to the whole team and our deadlines are tight. The other thing is, we are supposed to write minimum viable product, as it is a demo for a client, and every line of code matters. Some might say that we are delusional that after we finish demo we will make things the right way.
Did any one of you have a situation like this? How did you change your boss and team's mind?

Back on my university internship.

I knew nothing about web dev and it was a full stack role. I was taught nothing and just sat down and ran entire solo projects for websites and web apps. Everything was down to me including client contact.

Taught nothing and had to learn the entire stack on the fly whilst trying not to get fired or lose clients. Company had no version control for these projects, no quality assurance/testing, no frameworks or anything.

The first 3 months were not a good time.

I work as part of a small international team in a big corp , we work product quality of sorts but work closer to dev than qa , last week we found several giant issues and reported them in . Dev and Qa teams of said project are Indians . Meeting starts , two of my colleagues are indian as well , so dev , qa and all the other involved parties from india decided they should join in from the same conference room . My manager(he's a brit) presents the issues . Dev manager starts talking , qa manager talks over him , they start to formally yell at one another . One of them (couldn't figure out which one) started asking my two colleagues which one of them found these issues . At this point I had already passed a headphone to my ex-colleague who still sits next to me , he looks at me when he hears the question . I panic . Colleagues say they don't know (*phu* I didn't CC them in emails and my manager didn't tell them ) . My manager tells them to calm down , take responsibility and find solutions else he'll veto the product back into fullblown development . Other managers start growling and fighting again (more than 10 people were in the same room arguing) me and my ex-colleague decide to go take a coffee since I didn't have a saying in the meeting . We get back 10 minutes later , indians are still arguing over my manager trying to explain the issues a 4th time . I IM my manager and ask to drop the meeting , he gave me the ok and I dropped out, my head was hurting after an hour long meeting of angry indians arguing in a conference room and it kept hurting the whole day...yeah...meetings...fun time...

I have already started the process of a side project by desiging the software, the architecture, the 3d model, ordered all the electronics of a pet 'smart' stable for my guinea pigs.

Which would automatically feed them and refill their water tanks silently but for me the point on playing around with dozens of sensors for like different water levels, water quality, hay, temperature, water quality (you get the point) ... Building a nice looking web interface or an App to control everything and get a live feed from different angles ( sounds a bit crazy altogether but it looked like a cool project )

I even started a instructable and had a github repo for sharing the source of the app/web interface and the whole micro service based server

I'm still at it and hopefully will start to build the ***ing wood and acrylic parts in the next month's but currently and for the last month's free time ist my archenemy

Keep you posted if you are interested 😀

#just Bluetooth headphones things

When you're sitting on crowded public transportation and can't hear anything unless your phone is closer to your headphones than anyone else's, i.e. unless it's close as shit to your face 😍😍😍

When you want to listen to music for longer than 2 hours or several times during your workday but can't because the BT headphones last 2-3 hours 😍😍😍

When the left and right side don't pair with each other but you can pair with each individually 😍😍😍

When half of the button presses and user interactions aren't documented and there's no way to forget a device 😍😍😍

When you try to connect a new device to them in a public area and just see a dozen random serial numbers, so you have to wait and hope they get resolved to the headphone brand name 😍😍😍

When Satan takes your soul and the Bluetooth connection drops in hell 😍😍😍

When the music quality is lower and can experience static and maybe even skip in between 😍😍😍

When the bus hits a road bump, it falls out of your ear, and rolls halfway down the bus 😍😍😍

When it takes a long time to find them because they tiny af, and just as long to find the charging cable 😍😍😍

When manufacturers cannot agree on a standard volume sync system and so you have to check the volume and adjust every time you connect and disconnect your headphones 😍😍😍

Can we please just stop making everything Bluetooth?

Sincerely,
Someone who just wanted to listen to a 2 minute billie eilish song but found it easier to sing in his head

Hello Apple. Let me tell you something.
Even though i like your phones. I ABSOLUTELY WANT TO FUCKIN KILL YOU FOR YOUR HEADPHONES.
It's unbelievable you cock suckers, evey time the same shit happens.
WHY THE FUCK YOUR FUCKIN HEADPHONES AFTER 3-4 MONTHS START TO BEHAVE LIKE THEY ARE FUCKIN RETARDED.
1st headphones, they started changing songs randomly. That was back when i had iphone6.
It's ok i said, happens. Then i bought the iphone 7 and the headphones started behaving like that after some months. Again. Didn't say anything, i still liked them. So i went to buy the same headphones but for iphone6, with the 3.5mm jack. AND NOW THE SAME SHIT HAPPENS. FUCK YOU AND YOUR FUCKIN HEADPHONES AND YOUR FUCKIN 200€ HEADPHONES. COCKSUCKERS.

So, anyone knows any good quality headphones?
FUCK YOU APPLE.

VNC, RDP, X11 Forwarding, WTF.

There is not a single good product to "stream" a linux desktop to a different machine without being logged in in "parallel".

They are all complicated and/or suck big time in quality.

I am still confused why people treat testing as secondary position? Tester are paid less and they hire lower quality engineers. I think testing is as important as any other phase of development, like design or implementation. . . and yeah we do testing of our own code. The only thing I can do in my case is to see that people who change my code may not break basic functionalities. And again about edge cases, try to handle some other left to be seen in production( those which I could not think of due to lack of time) I take care not to leave edge case but sometime cannot do it. I just hope people realise the worth of testing.

Customer: The quality of the software you’re delivering is going down
Me: That’s because we’re developers, support, and spend all day on meetings without mentioning that deadlines are defined by you, not the technical team
Project Manager: I have added more members to the team so you can deliver faster
Me: That’s just slowing us down because this inherited code is shit, there’s no documentation and we’re always in a rush, without time for a proper ramp up
Customer: *throws money to our faces* I’ll remove two weeks to this delivery so we can test it better
Me: …

So I get these spam messages all the time, but correct me if my math is wrong. 15 years of combined experience / 155 employees = 0.096 years experience per employee which is about a month experience each assuming everyone has the same amount of experience. (15 / 155) * 12 = 1.152 (rounded of course). Now I know having the least amount of experience isn’t always a measure of quality since I have about the least in my team yet have been teaching some of the more experienced coworkers of mine some things but if I am trying to sell services I would probably pump up the collective years of experience a bit. Especially if there’s 155 of you.

Over the last few years I started to change my mind about Microsoft, thinking that now it's a different company, caring about its customers more than money, focusing on quality to wipe away their bad reputation.

But no, this week I was proven wrong. I had to use one of the Microsoft products (SharePoint) and all I have to say is: same old shit.

Slow, gives errors at random times, often does not save changes. The online editor has been completely broken for two days now. Never wasted so much time before on such a piece of crap.

Fuck you Microsoft, I guess it's not time for us to meet again.

Perhaps as a tip for the junior devs out there, here's what I learned about programming skills on the job:

You know those heavy classes back in college that taught you all about Data Structures? Some devs may argue that you just need to know how to code and you don't need to know fancy Data Structures or Big o notation theory, but in the real world we use them all the time, especially for important projects.

All those principles about Sets, (Linked) lists, map, filter, reduce, union, intersection, symmetric difference, Big O Notation... They matter and are used to solve problems. I used to think I could just coast by without being versed in them.. Soon, mathematics and Big o notation came back to bite me.

Three example projects I worked in where this mattered:
- Massive data collection and processing in legacy Java (clients want their data fast, so better think about the performance implications of CRUD into Collections)
- ReactJS (oh yes, maps and filters are used a lot...)
- Massive data collection in C# where data manipulation results are crucial (union, intersection, symmetric difference,...)
Overall: speed and quality mattered (better know your Big o notation or use a cheat sheet, though I prefer the first)
Yes, the approach can be optimized here, but often we're tied to client constraints, with some room if we're lucky.

I'm glad I learned this lesson. I would rather have skills in my head and in memory than having to look up things and try to understand them all the time.

Today at work I started doing 1 month old task with production problem.

First of all why now ?
Because I already fixed all the other urgent production problems I had during last month, done about 4 deployments of those super urgent errors.
Now I can start with not trivial one that are pending for quite time.
I am the only backend developer in this project ...

This is a dtp application and the problem is that we are not verifying if we got all fonts embedded in customer provided pdf files.

We are generating high quality images of those pdf for printing just fine from the beginning but now we need valid PDF with all fonts embedded in it. ( don’t ask me why I am only a hammer in this process )

After running simple test using python script against database it turned out we have over 500 broken PDF files without fonts.

So I guess I have just one sentence to say about it.

Fuck you PDF format for not being strict and allowing this shit.

It needs to be outright illegal for laptops to have fewer than four USB ports.

If the purpose of law is to improve the quality of life, why not outlaw the time-consuming annoyance of laptops with few USB ports?

The purpose of laptops is portable computing. Depending on a USB hub makes it less portable.

If it was legally mandatory for laptops to have at least four USB ports, there would be no more competitive disadvantage for laptop vendors sacrificing unimportant slimness for important practicality.

And to the very few people who consider slim design more important than USB ports and who are going to whine online about the extra 3 millimetres of thickness: Sorry, life is unfair. Your preferences don't matter. Practicality is the purpose of computers. You are the reason laptops are ruined for the rest of us. Get lost.

Over the last few weeks, I've learned two things about the head of my division:

1. They "don't care about code quality"
2. They want to try a "low-code" approach for the web frontend of a completely custom piece of what is currently desktop software

This is despite the fact that we have three full time developers with a wide range of both front and back end skills on the payroll, a deep library of existing components for various frontend frameworks, a custom CSS library, and a decent deployment pipeline for frontend code.

But sure, let's try low-code. Let's see how far that gets us.

Working for a large client converting paper forms to the web. Stated goals, simplify data entry for clients, improve data quality, reduce resourcing in backend human processing.

We met to review prototype and discuss workflow questions. Crazy deadlines, with the usual changing scope creep.

We start to point out the need for data validation, to shorten # of questions based on answers.

Business says no. All forms should be submittable regardless of what user enters, don’t put validations in because all that warning messaging confuses them and takes up more time.

Web form should behave like the paper copy....

Welcome to 1975!!! This is why 2018 won’t be like 2018...

Well, this happens time to time...

I'm freelancing as a backend guy. I like to take care of all infrastructure before really starting to build anything, this mostly includes dev/staging/prod environments with some linear promotion strategy. So.. I did this API. Still on staging, proceeding with the development as planned, everything goes according the timeline.

And then.. this happens... At some point PM told frontend guy that it's time for production (without notifying me), so the frontend guy does what "anyone" would do in this case - tells PM to create DNS record for production to point to staging app.

Time passes, I'm still unaware of this. But I'm starting to see some quality entries in the DB, not the usual QA crap. I write to them that they're doing good job and continue with my tasks.

One of the tasks required some major DB change. I could've written migrations script, but since we're not in "production" yet, I just wipe the DB and recreate schema as I need it.

In 10 minutes the furious PM starts shouting that "production" is down and I need to fix it ASAP.

I'm lost, I'm asking questions, I'm slowly understanding what's happening...

So I want to grab some coffee, sat back down, wrote politely that they suck, added a finger emoji and terminated the contract.

Felt like the right thing to do as I definitely don't want to continue within the same "team".