Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "workload"
There's this guy where I work who's one of the senior linux engineers. To me, he's like a linux god. He knows how to solve the most difficult problems and somehow copes with all the stress/workload. Next to that, he's only one year older than me!
Whenever I'm at work, I consider myself a junior, which I actually am. I also, as said earlier, see this senior guy as a fucking linux god and consider myself to be an absolute newbie around him but he is the most kind/friendly guy ever.
But then, today, something happened which made me feel like a god in front of him, a very, very weird feeling.
For him, doing his stuff is the most normal thing in the world while for me, it's still a learning process.
For me, programming is the most normal thing in the wold, while for him, it's still something he just knows the very basics of.
Told him I'd give him a working script in 30 minutes. Emailed it to him in 10.
He seemed/reacted the way I always do when he solves something I have no clue how to solve.
It was really weird to witness *him* being amazed of something that *I* made/did.
Today was a good day where I saw that one person's limitations can be anothers' most easy thing, even if that another person sees that one person as a god.14
**Reflecting on my life and current workload**
rm -rf new_project.3
Started working in a company as an intern, they want me to do everything whether I know how to or not.13
Long rant ahead. Should take about 2-3 minutes to read. So feel free to refill your cup of coffee and take a seat :)
It turns out that the battery in my new Nexus 6P is almost dead. Well not that I didn't expect that, the seller even explicitly put that in the product page. But it got me thinking.. why? Lithium batteries are often good for some 10k charges, meaning that they could last almost 30 years when charged every day! They'd outlive an entire generation of people!
Then I took a look at the USB-C wall charger that Huawei delivered with this thing. A 5V 3A brick. When I saw that, I immediately realized.. aah, that's why this battery crapped out after a mere 2 years.
See, while batteries are often advertised as capable of several amps (like 7A with my LiitoKala 18650 batteries that I often use in projects), that's only the current that they can safely take or deliver without blowing up. The manufacturer doesn't make this current rating with longevity in mind. It's the absolute maximum in current that a given battery can safely handle.
The longevity on the other hand directly depends on the demand that's placed on the battery. 500mA which is standard USB 2.0 rating or 1A which is standard USB 3.0 rating, no sweat. The battery will live for at least a decade of daily charges and discharges like that no problem.
But when you start shoving 3A continuous into a battery, that's when it will suffer. Imagine that your current workload is 500mA and suddenly you get shoved 6 times that work upon you. How long would you last?
Oh and not only the current is a problem, I suspect that it also overvolts the battery to maintain a constant current all the way till the end. When I charged my lithium cells with my lab bench power supply, the battery would only take a few milliamps when it got close to the supply voltage. Quick bit of knowledge: lithium cells are charged at constant current first, then when the current drops below that, it continues at constant voltage - usually 4.2 or 4.35V depending on the battery. So you'd set your lab bench power supply at 4.2V 500mA. But in that constant voltage mode, as the battery's voltage and the supply's voltage equalize, the current drops because the voltage difference becomes lower. Remember, voltage is what causes current to flow. Overvolting at the supply to stay in constant current mode all the way till the end speeds this process up but can be dangerous and requires constant monitoring of the battery voltage.
So, why does Huawei and a bunch of other manufacturers make these 3A power chargers? Well first it's because consumer demands ever more, regardless of the fact that they can just charge at 500mA for the night (8h of sleep) and charge a 4000mAh battery from 0 to 100% no problem. Secondly it's because sometimes you need that little bit of extra juice fast, like when you forgot to plug the damn thing in and you've got only 30 minutes in the morning to pour some charge into it.
But people use those damn fucking things even when they go to bed, making that 3A torture a fucking standard process!! And then they complain that their batteries go to shit?!
Hopefully this now made you realize that the fast charger shouldn't be used as a regular charger ^^30
This week I quit the corporate life in favour of a much smaller company (60 people in total) and i never felt so good.
After 3 years in 2 big corporations, I began to hate coding mainly because of:
- internal political games. It's like living inside House of Cards everyday.
- management and non-tech people choosing tech stacks. Angular 4 + Bootstrap 4 alpha version + AG-Grid + IE11. Ohhh yeah. Not.
- overtime (even if it was paid double). I never did a single minute of OT for fixing something that I caused. I spent days fixing things caused by others and implementing promises that other people made.
- meetings. I spend 50-60% of the time in pointless meetings (I tracked them in certain time intervals) but the workload is same like I was working 8 hours / day.
- working in encapsulated environments without access to internet or with limited access to internet (no GitHub, no StackOverflow etc.)
- continuously changing work scope. Everyday the management wants something new introduced in the current sprint/release and nobody accepts that they have to remove other things from the scope in order to proper implement everything.
- designers that think they are working for Apple and are arguing with things like "but it's just a button! why does it take 2 days to implement?"
- 20 apps installed additionally on my phone (Citrix Receiver, RSA Token, Mobile@Work Suite etc.) just to be able to read my email
- working with outdated IDEs and tools because they have to approve every new version of a software.
- making tickets for anything. Do you want a glass of water? Open a ticket and ask for it.
- KPIs. KPIs everywhere. You don't deserve anything because the KPIs were not accomplished.
The bad part of the above things is that they affect your day-to-day personality even if you don't see it. You become more like a rock with almost 0 feelings and interests.
This is my first written "rant". If anyone is interested, I will post different situations that will explain a lot of the above aspects.13
Best boss I have ever had?
He owned a car dealership and made me the first fulltime employed webdev in a car dealership in germany.
He believed in me and our mutual vision, and we had an awesome 7.5 years together. he gave me time to develop myself and to develop software and websites.
through my software and process optimization we were able to go from 300 sold cars per year to 3000 without hiring any more employees and without increasing workload and stress on the employees.
When I had my last day at his company, he didn't show up.
I was mad like hell, because we have spent so much time together, went to many countries together, even slept in the same hotel bed! I considered him pretty much a friend, even though he was my boss and 10 years older.
Much later he told me that he didn't show up on my last day because he didn't want to cry.
now we meet every 3 months and go out, eat and drink and just talk and laugh.
best guy ever, will never forget what he did for me.12
Ladies and gentlemen, prepare yourselves for a rant with a capital R, this is gonna be a long one.
Our story begins well over a year ago while I was still in university and things such as "professionalism" and "doing your job" are suggestions and not something you do to not get fired. We had multiple courses with large group projects that semester and the amount of reliable people I knew that weren't behind a year and in different courses was getting dangerously low. There were three of us who are friends (the other two henceforth known as Ms Reliable and the Enabler) and these projects were for five people minimum. The Enabler knew a couple of people who we could include, so we trusted her and we let them onto the multiple projects we had.
Oh boy, what a mistake that was. They were friends, a guy and a girl. The girl was a good dev, not someone I'd want to interact with out of work but she was fine, and a literal angel compared to the guy. Holy shit this guy. This guy, henceforth referred to as Mr DDTW, is a motherfucking embarrassment to devs everywhere. Lazy. Arrogant. Standards so low they're six feet under. Just to show you the sheer depth of this man's lack of fucks given, he would later reveal that he picked his thesis topic "because it's easy and I don't want to work too hard". I haven't even gotten into the meat of the rant yet and this dude is already raising my blood pressure.
I'll be focusing on one project in particular, a flying vehicle simulator, as this was the one that I was the most involved in and also the one where shit hit the fan hardest. It was a relatively simple-in-concept development project, but the workload was far too much for one person, meaning that we had to apply some rudimentary project management and coordination skills that we had learned to keep the project on track. I quickly became the de-facto PM as I had the best grasp on the project and was doing a lot of the heavy lifting.
The first incident happened while developing a navigation feature. Another teammate had done the basics, all he had to do was use the already-defined interfaces to check where the best place to land would be, taking into account if we had enough power to do so. Mr DDTW's code:
-Wasn't actually an algorithm, just 90 lines of if statements sandwiched between the other teammate's code.
-The if statements were so long that I had to horizontal scroll to see the end, approx 200 characters long per line.
-Could've probably been 20 normal-length lines MAX if he knew what a fucking for loop was.
-Checked about a third of the tiles that it should have because, once again, it's a series of concatenated if statements instead of an actual goddamn algorithm.
-IT DIDN'T FUCKING WORK!
My response was along the lines of "what the fuck is this?". This dipshit is in his final year and I've seen people write better code in their second semester. The rest of the team, his friend included, agreed that this was bad code and that it should be redone properly. The plan was for Mr DDTW to move his code into a new function and then fix it in another branch. Then we could merge it back when it was done. Well, he kept on saying it was done but:
-It still wasn't an algorithm.
-It was still 90 lines.
-They were still 200 characters wide.
-It still only checked a third of the tiles.
-IT STILL DIDN'T FUCKING WORK!
He also had one more task, an infinite loop detection system. He watched while Ms Reliable did the fucking work.
We hit our first of two deadlines successfully. We still didn't have a decent landing function but everything else was nice and polished, and we got graded incredibly well. The other projects had been going alright although the same issue of him not doing shit applied. Ms Reliable and I, seeing the shitstorm that would come if this dude didn't get his act together, lodged a complaint with the professor as a precautionary measure. Little did I know how much that advanced warning would save my ass later on.
Second sprint begins and I'm voted in as the actual PM this time. We have four main tasks, so we assign one person to each and me as a generalist who would take care of the minor tasks as well as help out whoever needed it. This ended up being a lot of reworking and re-abstracting, a lot of helping and, for reasons that nobody ever could have predicted, one of the main tasks.
These main tasks were new features that would need to be integrated, most of which had at least some mutual dependencies. Part of this project involved running our code, which would connect to the professor's test server and solve a server-side navigation problem. The more of these we solved, the better the grade, so understandably we needed an MVP to see if our shit worked on the basic problems and then fix whatever was causing the more advanced ones to fail. We decided to set an internal deadline for this MVP. Guess who didn't reach it?
Hitting the character limit, expect part 2 SOON7
At the peak of the dotcom boom of the early 2000s I had been hired above my skill set because recruiters were desperate to fill seats. I had a pulse and could code even a little so they hired me.
I was the senior web developer on an agency contract with a major corporation working on an ASP (pre ASP.NET) website. I had hired a temp to help me with the workload and one day, in exasperation at my spaghetti code and non-understanding of MVC concepts, he threw his hands in the air and exclaimed, "Do you even know what you're doing?!"
Not having the type of personality to give any subordinate a dressing down for insubordination, I just felt awkward. He was right, of course. I used that as impetus to study more and attend conferences. I'm still a below-average coder because my brain struggles with math and logic. A lot. But that definitely took me down a peg. All those recruiters treating me like I was hot snot on a silver platter when I was really just a cold booger on a paper plate.4
Yeah so OK this ancient legacy clusterfuck we've been maintaining and keeping alive finally broke. And even though I'm very pleased with both being right, and the well deserved right to say I TOLD YOU SO, SO MANY MANY FUCKING TIMES to all in management, it's the definition of hate to work 18 hours a day to fix the shit someone else built, that they refused us to refactor. Ah, but wait; there's more! Everyone thinks it's our fault (R&D), because historically it was our department that built the system. Ten years ago. So sales and support are now all over us, those responsible for us being in this mess are either gone or so high up in management that they refuse to take part.
Taking the fall and blame and workload, for something we warned repeatedly about, but were refused to do something with, because shiny features and new apps is what is important!
I'd understand it if the numbers were red, but they arent!! We are growing so fast it was inevitable!
I fucking hate companies who dont listen to their devs..... also companies who places ops on dev shoulders.
Yaaaargh! Also; two developers means twice as fast? No? Fuuuuuck!!!11
I'm the sole developer at work.
Literally the entire company, save myself, is sales people. (We have one remote mobile contractor as well, but he only does mobile; I'm responsible for everything else.)
I inherited a gigantic pile of nightmare from the previous "senior-level intern" solitary dev/CTO, and I'm still trying to figure out the bulk of it, meaning everything takes longer.
Anyway, we have a meeting roughly once a week, and during each of these -- and several times throughout each week -- the salespeople say things like "We should address this" or "This should be our top focus" or "We really need ___ so I can sell more merchants" or "___ doesn't work right; we should fix it." All of these "we"'s and "our"'s, of course, mean me.
So, today, I decided I'd make a list of everything I have to do, and their general size. Assuming large projects will take one month, medium projects will take one week, and small projects will take one day... I have four months, two weeks, and four days of work ahead of me. (yet I know one of those large projects will take at least two months...)
Make it stop ;;15
It's fantastic how you blame me, the back-end developer, for the things that the manager, business analyst, and front-end developer missed.
The front-end developers didn't make the user interface and admitted they didn't get to do it and outright forgot about it due to workload, oh it must be the back-end guy's fault for not asking them. You, the manager, have no fault here at all. Why are they overloaded again? And they, as the developers who totally missed out, were just innocent creatures who "were not informed".
The business analyst admits that he thought I was the front-end developer even though I corrected him during the first meeting where he said, "Oh okay, so Rutee is the back-end and <this other guy> is the front-end." EVEN THOUGH every day, we have a meeting and you see my JIRA ticket in all caps "BACK-END". Ever thought about asking? Then the manager comes in there and says, "No, it's not your fault. We as a team should take responsibility. That's how smart teams work." And yet your fucking face, I hate your face, man, and your fucking insinuations. I swear you're all just looking for a scapegoat, now it's making sense why you borrowed me.
While I'm doing my job here minding my own task and knowing that shit has been assigned to the proper person, the manager, business analyst, and other developers who's been in this project for years never bothered to ask for updates regarding the front-end until now. Why is back-end making noise the past few weeks? Because someone is WORKING on it. Someone is RAISING issues. Someone is CLARIFYING the requirements.
I had my own problems. Your requirements are severely lacking, your setup fucking sucks and doesn't fucking work, there were issues and dependencies from several other teams, and now it's my fault that I didn't ask about the front-end? How is that? I create the API, you fucking call it. If anything, you should be asking me about the endpoint but I guess I have to do EVERYTHING and know EVERYTHING in this project where I was just borrowed and I'm technically the new guy here.
I guess it's a "let's blame the new guy" game around here. You can hire the most senior of all developers you can but no one can ever just guess or read your fucking minds. You can't just put someone in one project and expect them to know all your processes, your repositories, your developers, your fucking uncommitted code changes THROUGH EXPERIENCE and PROGRAMMING LANGUAGE PROFICIENCY. This has nothing to do about proficiency and being proactive. I can be proactive TO AN EXTENT. I can't do YOUR job for you.
Jesus fucking Christ. This project is so disorganized and yet you can't acknowledge that. Then I would get an advice from someone else that we should have talked while front-end is there. He WAS, he's even on the invite. Every fucking time shit hits the fan, you all get a week to fix something and I get a couple of hours or a day. Issue two weeks ago? Resolved Friday after my shift, yet I managed to deliver the next morning. Issue last week? Resolved Friday afternoon, yet I managed to deliver before end of day.
"This is the first time this happened." I highly doubt that. You just want to correlate my *new* presence to your failure so you can insinuate that the new guy is to blame. Your team sucks. Your management sucks. "Oh, that's just how he manages, he tells you the end goal and it's up to you to THINK what you have to do." I did THINK but why the hell do I have to THINK for them or for everybody else?
So yes, another rushed deadline. Another excuse for the slacking pieces of shit, "Oh, I can't do my job because back-end doesn't have this other endpoint I need for this one. Guess I'll go home." When did you say you need another one? "Just now. But you should have known earlier if you asked." IF I ASKED. At what point of my life would I randomly ask, "Do you need this endpoint that isn't part of the requirements but does this/that?" where "this/that" is some functionality I know nothing about because it was never discussed.
Seriously, fuck you and your fucking requirements. You fucking lazy pieces of shit cunt whore motherfucker. I hate all of you. You ruined my entire fucking month. How do you expect this to be less chaotic when you defend the slackers and punish the ones who actually do their jobs and use them as scapegoats?
Three more fucking days, man, and I'm out of this shit. When I get back, I hope you don't bother me with this shit anymore. Your mom's a hoe and I'm accepting calls from recruiters anyway.25
I'm gonna have a serious talk with my bosses the day after tomorrow. We have so much to do, we are basically at 150% workload. Problem is: they don't pay us for overtime.
This has been going on for 18 years in the company. It will not be easy. But they either start paying our overtime or I am out (and probably taking the whole dev team with me.)
Wish me luck!27
Back in my sysadmin days we had an IT zoo to look after. And I mean it... Linux side was allright, but unix.... Most unices were no longer supported. Some of their vendors' companies were already long gone.
There was a distant corner in our estate known to like 2 people only, both have left the company long ago. And one server in that corner went down. It took 2 days to find any info about the device. And connecting to it looked like:
1 ssh to a jumpbox #1
2 ssh to a jumpbox #2
3 ssh to a dmz jumpbox
4 ssh to an aix workload
5 fire up a vnc server
6 open up a vnc client on my workstation, connect to than vnc server [forgot to mention, all ssh connections had to forward a vnc port to my pc]
7 in vnc viewer, open up a terminal
8 ssh to hp-uxes' jumpbox
9 ssh to the problematic hp-ux
A lot of engineering fads go in circle.
Architecture in the 80s: Mainframe and clients.
Architecture in the 90s: Software systems connected by an ESB.
Architecture in the 2000s: Big central service and everyone connects to it for everything
Architecture in the 2010s: Decentralized microservices that communicate with queues.
Current: RabbitMQ and Kafka.
... Can't we just go back to the 90s?
I hate fads.
I hate when I have to get some data, and it's scattered on 20 different servers, and to load a fucking account page, a convoluted network of 40 apps have to be activated, some in PHP, others in JS, others on Java, that are developed by different teams, connected to different tiny ass DBs, all on huge clusters of tiny ass virtual machines that get 30% load at peak hours, 90% of which comes from serializing and parsing messages. 40 people maintaining this nightmare, that could've been just 7 people making a small monolithic system that easily handles this workload on a 4-core server with 32GB of RAM.
Tripple it, put it behind a load balancer, proper DB replication (use fucking CockroachDB if you really want survivability), and you've got zero downtime at a fraction of the cost.
Just because something's cool now, doesn't mean that everybody has to blindly follow it for fucks sake!
Same rant goes for functional vs OOP and all that crap. Going blindly with any of these is just a stupid fad, and the main reason why companies need refactoring of legacy code.13
Web Devs - How many projects do you typically work on at once? I am currently developing 24 websites at once, most of them custom (homepage). I just feel like that is absurd and my company is absolutely insane. Not to mention I'm the front line for client communication as well, pretty much the project manager AND developer. We're a huge company too, not a start up. Just feel like not having project managers for web dev industry is unprecedented except for freelance. 😡👎🏼18
Once upon a time, one or two jobs ago, a really awesome engineer specced out a distributed search application in response to a business need. This company was managed pretty oldschool and required a ton of paperwork and approvals.
The engineer spent many weeks running tests and optimizing the hell out of this app cluster. It flew, and he had the data to prove it could handle production workloads (think hundreds of terabytes of data being processed every single day)
Part of the way he achieved this was having RAID0 on all of the servers to maximize I/O throughput. He didn't care much about data loss, since the application itself was fault tolerant on a much more granular level.
Management, hearing about this, absolutely flipped their shit and demanded RAID6 instead. This despite the conclusive data that the engineer had that proved RAID6 couldn't keep up.
He more or less got told to STFU.
Even this despite the fact that a RAID restripe would actually take many times longer than rebuilding the failed node from scratch (a process that took about 30 minutes by hand, and could probably be automated to be done in less than five), causing a longer exposure to actual data loss throughout the length of the days-long array rebuild time.
The ill-thought-out requirement added about 50% to the cost of the project (*many* more hard drives now required), beyond the original budget, and the subsequent bureaucratic wrangling resulted in a late product launch.
6 months or so later, after real customers were using this product, the app was buckling under around half of its expected workload. A friend of the engineer suggested to management to try RAID0. Sure enough, that resolved the I/O bottleneck.
This rage-inducing story has a happy ending, though! Said engineer left the company not long after this incident, citing it as a reason for his departure. He was immediately hired by another company, making integer multiples of his prior salary.
The product the company botched the launch of by ignoring his spec? It died a few months later. Maybe the poor customer experience was to blame? Maybe the late launch? Maybe it was another reason entirely.
Either way, millions of dollars of hardware now sat fallow. This was a black eye on the company all the way up to the C-level.
tl;dr: Listen to your engineers. You hired them for their expertise.5
There's this huuuge project I was a part of for half a year. I was kicked off along with a few dozens of other devs (>60% of total manpower) a while ago for particular company reasons.
Now the remaining devs are oh-so-enjoying their time there..
1. workload has not changed
2. deadlines have not changed
3. no one will have Christmas-NewYear vacation
4. a new k8s-based infra is scheduled to roll out to PROD on Dec 23 (k8s is still far from ready - might need a few more months)
The most fun part is that it's not client's mgmt who has decided for #4 -- it's our own....
Boys.. Girls.. Save yourselves.3
Had a code that handled home network and was checking if everything is OK and ETC. I once noticed when i was at home and when i unplug NAS from outlet that it took hour or so to get email.
This is bad as you can imagine.
So after looking at the code i changed some code and just made it more dynamic to workload.
Lets just say that the email were now instant and also i somehow fixed CPU temperature website as side effect for whatever reason.
I felt good that day and bought pizza and got some beer and said fuck to school.
In order to reduce support costs, manager instructed his team to remove all logging/reporting of errors in the company’s CRM application.
Team’s support tickets went down 80%, manager received an award for his efforts, but mysteriously, DBA/support workload increased, bad/missing data,
increased support tickets in other areas of the business (shipping, etc. that relied on correct data from the CRM) and other side-affectual behavior.
Even after pointing this out this correlation, showing before/after code, no one believed the two were related and I was accused of not being a ‘team player’.
“You and the other teams need to learn from his example!”. As ‘punishment’ was I was moved to the team managing the CRM application.1
Been sick since Wednesday with a heavy feeling of dizziness and vertigo (BPPV). Basically I got sick in the week I intentionally planned nothing to tackle my workload and get some stuff done, but I was physically unable to work on it until now.
Meeting is on Monday.
Also preorder my new book on O'Reilly, much appreciated.
(No, I am not panicking, pls send help)3
Well i was between jobs at the time, looking for something, anything to fill in the black hole being created in my wallet.
I applied online though this company’s website and within 20 minutes was on a phone interview setting up a face to face, this was Monday afternoon.
I went in on the Wednesday morning with the manager, no cv, no resume, no examples of work, we talked, did a couple of brain teaser questions and Friday morning I had the job 😂
I have never put so little effort into getting a job before but it was all a sham, the workload and requirements this job constantly sets out to kill me with are godly.
3 years later I’m still alive ( somehow ), and no blood has been shed.... yet.
Told my advisor that I was not interested in an additional position due to the massive workload I’m already carrying in my back. Lo and behold, I get a message from a colleague congratulating me on the extra position.
What an awesome feeling it is to have three meetings sceduled for tomorrow and not have made any preparations for either of the because your workload is somewhat a fuckup and you also just don't fucking give a shit anymore.
Quitting at the end of the month.
So, 9months ago my scrum master came to me and asked me to spearhead a "little" API... 2months work, no worries... I started the analysis and quickly discovered that that estimation was grossly understimated...
I convinced them that it was not 3 months but 4. I alerted to the design mistakes that were made, I pushed changes and made sure the entire project worked, was stable and the best it could be... 4 months passed, target proposition donne... Several change requests since then and we have been implementing braindead CR after CR for 5 months... Most CRs came from design issued I raised but we're ignored at the time just to come back and bite them on the ass...
Horrible design, bad documentation, amateur requirements analysis... However, delivered successfully with great acceptance...
What was my reward? They rearranged my team, removing virtually every good performer.
Never did I receive a "good work" or a "thank you"... I don't want one, I am just doing my job... However can you please not fuck me in the ass!? I now have 2 projects to spearhead at the same time and virtually no team... I can only handle so much!!!
Some good news? Ok, just announced I'm the project owner of a new project, that we will take advantage and make a 2 in one.... Great! Some more work for my lap! Thank you for the workload raise!... Ok, timewise? One month! And I still don't if that includes implementation....
TL DR; did my job, got fucked with more work...
Sorry for the vent, just wandering if I should try and not do my job...2
Accepted a feature request that practically doubled the workload without asking for more money, on account of trying to be fair to a customer who was working through a translator.
Only to get stiffed on 3/4 of the money agreed to in the first place.
Only saving grace was everything was on my servers, so I took him down for non-payment.1
My current new boss is pretty awesome. When he arrived, we were a lot of juniors dev crumbling under pressure. He directly went to product team and to sales team and totally reduced our workload to something acceptable.
He values sane work environment a lot, and I think that's what make a good boss
So one of my clients had a different company do a penetrationtest on one of my older projects.
So before hand I checked the old project and upgraded a few things on the server. And I thought to myself lets leave something open and see if they will find it.
So I left jquery 1.11.3 in it with a known xss vulnerability in it. Even chrome gives a warning about this issue if you open the audit tab.
Well first round they found that the site was not using a csrf token. And yeah when I build it 8 years ago to my knowledge that was not really a thing yet.
And who is going to make a fake version of this questionair with 200 questions about their farm and then send it to our server again. That's not going to help any hacker because everything that is entered gets checked on the farm again by an inspector. But well csrf is indeed considered the norm so I took an hour out of my day to build one. Because all the ones I found where to complicated for my taste. And added a little extra love by banning any ip that fails the csrf check.
Submitted the new version and asked if I could get a report on what they checked on. Now today few weeks later after hearing nothing yet. I send my client an email asking for the status.
I get a reaction. Everything is perfect now, good job!
In Dutch they said "goed gedaan" but that's like what I say to my puppy when he pisses outside and not in the house. But that might just be me. Not knowing what to do with remarks like that. I'm doing what I'm getting paid for. Saying, good job, your so great, keep up the good work. Are not things I need to hear. It's my job to do it right. I think it feels a bit like somebody clapping for you because you can walk. I'm getting off topic xD
But the xss vulnerability is still there unnoticed, and I still have no report on what they checked. So I have like zero trust in this penetration test.
And after the first round I already mentioned to the security guy in my clients company and my daily contact that they missed things. But they do not seem to care.
Another thing to check of their to do list and reducing their workload. Who cares if it's done well it's no longer their responsibility.
2018 disclaimer: if you can't walk not trying to offend you and I would applaud for you if you could suddenly walk again.2
Fuck people that do not show up on Mondays because"they're sick".
Thanks for extra workload of two more people on top of my already two-man job.7
PM measure workload by UI upgrades and careless abt backend, meaning you cant justify u were developing backend while there is no output.3
I was reluctant to try out flutter earlier on because of claims online stating that hybrid frameworks aren't there yet. That's one hell of a crap!
I fell in love with flutter after completing my first flutter app. Shit was just too easy. So many helpful libraries which has eased my overall workload lately.
We built a Native Android app which took 2months+ to complete and I just finished porting it to flutter for iOS and Android in 3 weeks. Boss was happy, Client was happy, I am freaking joyous, everybody is happy!
From the mouth of a Native Android Dev with over 5yr of exp. This shit called flutter is worthy of all the hype. I fucking kid you not!
I don't know about the past... I assume it was shitty then cus I also blasted it based on git issues but now it seems even more faster to build production worthy apps than anything I've encountered.6
I am 99% done with my academic project, but still the workload is heavy, and I've got too much on my plate already, mom's spaghetti
I just had a professor unironically ask why students are stressed all the time. Education has changed. The insane assessments and workload make a healthy work-life balance impossible. There's no love of learning when the pace is shoved down your throat.8
>be me, working at IBM as CC operator
>onboarding freeze, people leaving team, not enough operators
>take extra workload to sustain monitoring
>team gets merged with other CC team(different customers)
>take over of developing full workload automation project
>sick coworker, have to take more extra workload to cover monitoring
>get tiny raise
>coworker gets the same raise for only one extra workload
>be expected to do both programming and monitoring for the little salary
>too autistic to quit
>too autistic to confront my mamager with this
What do, devRant?5
So today I was offered a job at the company as a junior frontend developer. Digging a little deeper I found out that they don't have any other frontend devs in house.
So the job offer translated to:
- senior skillset
- senior workload
- junior wage
Best part is that I was freelancing for them in past and was helping to establish some of the workflow a year ago for more money they offered now.
Thanks, no thanks, I guess?4
So I just found an old branch, from an ex co-worker, with a whole bunch of unmerged docs. This effectively cuts my workload for today in half.
Today I'm going home early fuck yeesss
Also I will be sending that guy some well deserved couple of beers1
It's just after midnight.
I have a heavy workload starting tomorrow.
Going to require lots of time away frm my wife and son.
They're all in bed, but I am awake.
My only dilemma at this point:
Work on my side project?
Or play Command And Conquer?2
OMFG I'm exhausted from the workload this last week, but everything is due this week and I'm totally ruined because everything is half done. Just murder me in my sleep please.3
When ur the only one who can do a job and u feel sick but force urself to go so the workload doesnt double tomorrow.2
I usually work in a two person team on a hybrid application we are developing, using AngularJS and node.
This normally works okay, because he handles the back end (he's been on the project since January last year, I joined in August as a placement student), and I handle the front end.
However, due to Christmas holidays and such, he's ended up taking an entire month off, and won't be back until the end of January.
I've dabbled in back end before, some routes and that for SQL queries, but nothing serious.
Last Tuesday our core service for the application that needs to be updated in real time broke and pissed off the API provider because we were hammering them with requests.
My first day on back end and this happened. I didn't really know what to do, and had to call my teammate to ask what to do. I essentially just restarted things, and left them as is, until I could find a solution.
From there, I had to mock the operation of the service (which is a complex enough beast) to figure out the problem, and find a fix. Our app more or less hinges on this service, so if it messes up, it's the end times.
All of this while flying on what I've interpreted because the guy that's on holidays was the only guy that knows more about this project than I do.
To make things worse, the clients are being very particular because they're waiting on investments and don't have money to pay our company. So, if they're paying for 5 days work, they're going to put in 5 days of project development. The problem is that their interpretation of 5 days of project development has not changed from when there were two people on this project.
There are 40 tickets in this sprint (ends Friday) and 35 of them are assigned to me. Granted, not all of those take a day to do, but estimates don't mean anything, I guess.
Back at my masters degree there were 3 group projects and 2 of them were dev related. Being the last to enroll and classes had already started, I entered a team missing one person. 2 out the 3 team members were complaining how they couldn't keep up with the workload and kept doing nothing on the group assignments. The other person and me did all the work because we wanted to get good marks on the project. Sadly, the teams remained the same on the 2nd semester, mainly because all the star students were grouped together to our chagrin. This time though, neither the teammate nor me were lenient on our comments during group assessment which influenced heavily on the individual marking.
Told department lead several of us devs are considering quitting due to low wage and insane workload.
Result: Team spirit questionaires and team building gathering.
No extra pay and now even less time to get work done.2
IBM, because I work in there.
Well maybe it wouldn't be as bad if I didn't work at command centre. From the beginning I did my best to get a promotion, but it resulted in me having shitton of workload and no raise. Maybe it's just shitty management tho. But still.
Did I start watching SpongeBob SquarePants at 00am? Yes.
That's how tired I am of absurd workload and salesmen that promise features we're not close to have.
This is to inform you that due to the workload of Diwali 10th Nov would be working a half day
So the 10th Nov holiday would be shuffle to 17th Nov 2018 (i.e. Saturday)
Note:- Those team member taking leave on 10th Nov it would calculate 5 days of leave."
Got this mail -_-9
Working 18 hours per day was tough, at the beginning coffee helped a lot. However I started loosing friends and the little free time I had, I spent it drinking, lonely in anonymous pubs, trying to socialise.
Workload increased and stress started to affect me, so I began smoking weed to relax.
To recover and work with renewed energy coffee was not enough anymore, I started with pills, amphetamines, coke, crack. After the biggest deployments I would disappear for days in an opium den.
Work, it's a gateway drug.6
So I've been working as an operator in IBM for a year now. Two months after my onboard our team got an onboarding freeze. Since then more than a half of the team left and more are supposed to go, soo there is a problem covering all the workload. I volunteered to take 4th customers workload (out of 4 customers our team supports) because I already knew most of the work that is done there.
At a one-to-one meeting with my manager I asked for a little raise, because I have the 4th customer, I take other peoples shift anytime they need to take a free day, I update the documentation regularly, I write scripts for coworkers for installing software/automating what can be automated (and I'm the youngest here...) bla bla, telling him that I think I do a lot for the team and I deserve it. He told me that he would rather take away one of the customers workload. I rolled my eyes and went with it.
Two days later this asshole gave a raise to a guy, who was onboarding with me, because he wanted to motivate him. That very same day he told us that it seems like two customers are going to merge into one workload.
I'm so pissed because of this. I do my best all the time so I can get promoted to 2nd level linux team (I'm kinda one foot there) but the freeze is still preventing me to go. I'm already so tired of dealing with the bullshit of customer not knowing their own infrastructure, shitstorms of tickets during changes after level 2 didn't set maintenance mode again, repairing coworkers linux boxes because they don't know better and I'm so pissed at this un-initiative dickhead of a manager that gives a raise to lazy people.
Finally switched jobs after 7 years, with the expectation to have bigger workload then at my previous job where i almost fell a sleep.
To find even less workload at my new job, asked my manager if i could do something extra because i'm bored.
To get the answer that i don't have permission to do extra work for a half year, because they think its already a big workload for a new employee and they don't want to give me a burn out..
Sigh... what to do... any ideas?8
So with my current windows heavy workload it is with a heavy heart that I commit to learning powershell. Wish me luck8
1 dept with only 1 staff, well 1 chief to be precise, all employees quit. Another dept with not enough manpower. Requested the dept with highest manpower to help with other depts tasks while struggling and solving the shits out. Thought company is bullying them with extra workload and voice out they are looking for new jobs.
They are not wrong. And that's the bittersweet shit I have to swallow. In the end, it was my responsibility and I'm not doing enough.
In june 2018 I am going to get my software developer diploma! I am very excited about it. But for now the workload is just getting higher and higher.
Therefore I think I am going to be less active on here for a while.
But before that I would like to introduce you to a new app two colleagues and I wrote to help students in similar situations.
It is a Website that allows you to manage all your study / school related stuff in one place.
It would be great if some of you guys would give it a try.
We appreciate all your feedback!
But it's a side project and still in beta... so please do not expect it to be perfect (yet, we are trying to get there...)
PS It's completely open source just search for outcobra on github. Feel free to open up as many issues as you like2
TL;DR: When picking vendors to outsource work to, vet them really well.
Got a large redesign project that involves rebuilding a website's main navigation (accessibility reasons).
Project is too big just for our dev team to handle with our workload so we got to bring a 3rd party vendor to help us. We do this often so no big deal.
But, this time the twist was Senior Management already had retained hours with a dev shop so they want us to use them for project. Okay...
Have our scope / discovery meeting about the changes and our expected DevOps workflow.
Devs work Local and push changes to our Github, that kicks off the build and we test on Dev, then it goes to Staging for more testing & PM review. Once ready we can push to prod, or whenever needed. All is agreed, everyone was happy.
Emailed the vendors' project manager to ask for their devs Github accounts so we can add them to the project. Got no reply for 3 days.
4th day, I get back "Who sets up the Github accounts?"
fuck me. they've never used Github before but in our scope meeting 4 days ago you said Github was fine...??
Whatever, fuck it. I'll make the accounts and add them.
Added 4 devs to the repo and setup new branch. 40min later get an email that they can't setup dev environment now, the dev doesn't know how to setup our CMS locally, "not working for some reason."
So, they ask for permission to develop on our STAGING server.. "because it's already setup"... they want to actively dev on our staging where we get PM/Senior Management approvals?
We have dev, staging, production instances and you want to dev in staging, not dev?... nay nay good sir.
This is whom senior management wants us to use, already paid for via retainer no less. They are a major dev shop and they're useless...
Cant wait for today's progress checkup meeting. 😐😐
Tomorrow starts a new guy in my team (I am TL), but I have never seen him before! 😕
A coworker resigned during the hiring process and has had his last day today and I am overtaking his team because my boss is unable to set up a job profile.
180% of workload and even more new guys arriving (2 more in the next 2 months!)
No salary raise either...
Took a week of PTO for a vacation because I'm pretty close to spent these days. Planning on getting in some kayaking and fishing I think, maybe some noodling on the guitar or read some Tolkien, as I really need to take a break from the computer and screens in general, and living in the latest COVID epicenter in the US I can do fuck all else.
I'm /really/ trying to force myself to ignore slack and work emails. I did all I could to leave my team prepared, and given that most are juniors who need A LOT of supervision since working remote, I fully anticipate having to fix everything and get shit back on track when I return next week. Telling myself it's inevitable so worrying about it now won't be any better than waiting till next week. LEARN TO READ CODE AND COMMIT HISTORY FUCKERS!
I know I have a full workload slated for the rest of the year and into Q1 21, so I know letting shit go for a little while is the best thing I can do for myself, and so that my family doesn't have to deal with me being a bastard all the damn time.3
An application requiring lots of servers to handle the workload is not the problem.
The problem is an application that cannot handle workload no matter how many servers you throw at it.2
I am working as intern with a super cool startup. I love working here.
But, for the past few days I've been busy with college, exams stuff. This has affected my work severely. I'm constantly past deadlines etc.. The startup understands the fact and also puts no pressure on me for to show up every day and decreased my workload.
College work will be the same for the next two months. I don't want to underperform at the company, at the same time cant do away with my college too.
It's like a relationship where you love the girl a lot but are genuinely too busy to spend time with her.
I'm meeting my supervisor today. I need a subtle way to let him know of the same. I know this would mean me leaving the company, but I want to join them back after two months. Or at least be a work from home, part time employee.
I'm in serious need of some help.9
Started this day great with the mention that a coworkers contract isn’t suspended.
Thats in freaking 6 months. Workload is already fucking insane, and STILL you fucking decide to fucking fire another fucking person from YOUR fucking company.
This has been the 5th i think and my contract is due to July. If it is prolonged i’m thinking of screwing this company over my going away myself. Bunch of mother fucking idiots.
Ended the day great as well.
Heard that a new person is going for lead promotion. Haha.
He has been here for only two months. :,)
Left and right projects are exploding meanwhile i’m in the middle trying to cut the right wire!
I've been a "firefighter" on our big money-making project for like a year now and probably will be for the next year. Every sprint, fully booked out.
However, this sprint, some people think I have time to brainstorm, learn new tech and attend meetings related to a completely new project.
"Will it done in 2 weeks?"
"How long do you estimate?"
I can knock up a rough version of your fucking application in about a week if someone grows some fucking balls and schedules me some fucking time for it. STFU and stop interrupting my other work. Allocate some time or shove it up your ass so far until you regurgitate it then swallow it again and choke on it.
Update to this rant: https://www.devrant.io/rants/210575
Now, roughly one week before the revised delivery date, they realize that we won't be able to finish the workload on time and they are thinking about moving the due date...
by two weeks 😒2
I have so much work to get done I don't even know where to start anymore. I've got 6 sites in development, 20 sites with continuing maintenance, and I'm in charge of everything IT in my office.
Today I asked if the other developer on our team could help out and take a few maintenance clients off my hands so I could work on getting builds done.
We called a team meeting where I explained my workload and pointed out that in order to make the deadline of next week on two of these builds our other developer is going to have to help out with some of the work on my plate.
Other dev: Well I've already got 3 sites that still need maintenance this month and I'm still working on $client site.
Me: Ok well today is only the 3rd so you have all month to do the maintenance on those sites, these two have to be online next week and I still have 100 hours of work to do between the two of them.
Me to CTO: can I get some backup here? Or can we hire me a monkey (my term for interns) for a couple weeks so I can focus on building?
CTO: We'll have to talk about that at our meeting next week. In the mean time, just do what you can to get the sites done and let me know if you think we aren't going to make the deadlines.
Me: That's what this conversation is, I'm telling you now, and I've been telling you for 3 weeks that we were getting close to my limit for my workload. We have approximately 175 work hours in a month, maintenance contracts alone accounts for 120 of those hours.
CTO: Alright, well if after Monday you don't think you're going to make the deadline (Thursday), then we'll see if we can find a solution.
Fuck this shit, I get paid the same whether the client is happy or not, I get paid the same whether we reach the deadline or not. I asked that salespeople stop making deadline promises before developers get to look at the scope but that's not the way we do things here. At least one of these sites is not going to be online Thursday, probably both.2
Okay i am torn here.
Specifically for Indian devs(better if you into android)
Would you be willing to work for Rs 10k per month for 6 months at a startup as your first job?
- nearby job. Its like 20 minutes metro ride
- known people and code base. I had worked with them last summer and know all their codebase. Its very large and will make me learn lots of new stuff.
- nothing formal: its a startup, they don't have any bonds, they don't give any equity, any bonus, any compensation stuff etc.
- Too less salary: lesser than that of a delivery guy or auto driver
- Too much work load: they are going to fuck me up straight in terms of work. They got only 1 super man sikh who made the whole stuff and who wouldn't be there most of the time. I have to read his code, understand it , learn all the libraries and then make new features all by myself
- Too much pressure : they are going to take away my 6/7 days and then may call for update on sunday. Plus they will be expecting me to complete a task(which includes all the stuff i added in the workload point) in like 1-2 days
- better options available (i guess?) : If i don't go there, i would either continue to apply for more Android related jobs, or would start learning more on competitive i.e changing the whole path stuff,etc.27
Wondering if anyone can give me some advice regarding stress management.
I am a sys admin of a continually amount of growing servers (now at over 130) and I do coding when I am not busy being screamed at by users. The stress is coming from the workload, but also the way that the workplace is running. The manager left, and now I am handling all his shit, and my own shit as well, and all his accounts have been handed over to me (accounts being clients here). The other IT guy who is supposed to help out with the server admin just finds other work to occupy himself, and I am losing my mind. There is literally an insurmountable amount of work that needs to be done, and it just cannot be done in the time that is allocated in the working hours. I am working overtime, unpaid overtime by the way, until 9/10PM at night to try and get through everything (*cannot apply updates and work on the app server while the users are live) and I am just starting to lose grip. I am taking my stress home with me (not taking it out on anyone), but I am not sleeping, not eating properly and even starting to dream about possible ideas to fault resolution when I sleep. I find that I am constantly tired, and it feels like a world is about to cave in on me. There is literally too much work to be done in too little time, and although I am more than capable of doing it (and will get it done, or the director will physically assualt me and accuse me of being useless, again) I feel that the struggle is just a bit too much.
Can anyone give me some advice on how to "wind down" or to "let go" just for a few minutes a day at least, so that I don't feel like I am on the job 24/7.
Manager brings up an idea, asks how long it would take to build out. I tell him a couple hours. I can be nice sometimes when the workload is light.
Build it out, make some improvements at home, create a dashboard so he can make small configuration changes.
We never use it.3
My biggest dev epiphany was also my dumbest one. We were working on a payment system for a roadside rescue company where an employee would register payments "in the field".
The challenge was automating input with typeahead and autocompletes in order to lessen the workload as manual input had to be an absolute minimum; this will be used by truck drivers/mechanics as they are trying to hurry to the next customer who has been waiting for 3 hours longer than we said we'd take.
We managed to make the invoice path first (customer has not paid, employee logs personalia needed for billing), but when it came to "paid on site" we almost upended the entire system trying to find a way to fetch user personalia outside of the invoice path.
Neither of us realized it during the days we were banging our heads against it. Realizing we don't need to make an invoice for a job that has been paid for was equal parts relief and utter embarrassment.
Probably my greatest lesson in how important it is to pull my head out of the code once in a while, and to ask myself what I'm trying to do and why.
So, a few days ago I went on an interview for a position as a web developer, and during the interview they tell me they are thinking about getting into hosting, and that if they decide to do so I would be the one responsible for managing all of it.
I have no idea how to set up web servers, let alone make sure they can handle heavy loads and so on, so I'd be taking on a huge responsibility and workload, along with the task of making websites.
The company consists of 5 designers, and at the moment, no developers, and they have about 30-40 customers, all with sites that would need to be moved to the new hosting platform.
My question to you all is this:
How much does quality hosting equipment cost, and is it really worth it for such a small company to get into hosting, or should they rather look to make a deal with an existing host for some kind of monthly kickback/rebate?
I'm thinking they should find an existing host and enter some kind of partnership, as that would be easier and safer than doing all the hosting inhouse.
What do you guys and girls think?5
2 AIX workloads got messed up during patching. Apparently they had a local database and they were in PROD env.
"Not a biggie - there's always a netbackup to restore the whole workload" - I said and reached out to netbackup folks.
Turns out even though netbackup was configured properly it had never even initiated successfully bcz backup NIC was not whitelisted in network layer. Never ever in 3 years.
Service guys were piiiiiiiiiiiiised big time1
I can cope with the workload and the silly client requests but I think my bullshit-threshold is very close to being breached.
One more thing and I'm not sure my brain will be able to act fast enough to stop my mouth shouting a horrible string of profanity.2
I started cleaning out the recruiters and headhunters from my linked in connections ... And I highly underestimated the workload of such a task ... FML3
Currently sat waiting to go into a 11am meeting where I will be told something is wrong even though I've completed a workload of 2 weeks in 3 days. If any PMs are on here, no appreciation sucks.5
As a dev, not a manager, what's the maximum number of projects you can handle at once?
I know it depends on the workload but wanna see how others do on average.
Literally fried up with so many projects put on my shoulders after the exodus from my company since they f-ed up bonuses and hikes.
Also, why does every manager think their project is The Priority one? Selfish assholes.6
I thought it worth repeating the wisdom I spotted there:
"That's what the Test Track at Velim is for"....methinks that modern managers, project managers and beancounters need reminding of this.
My experience lately is that when folk of their ilk hear 'apply all the edge cases', what they hear is 'blahhhhh blahhhhh blahhhhhh un-necessary time and cost' and promptly chop those 'edge-ish' bits out of the test and/or approvals plan.
I'm lucky enough to have had a diverse and very enjoyable career testing things for a living, in an organisation where you were *expected* to try and break the thing you were working on (within sensible limits).... the rational being that if it went wrong in-service, it would be seriously inconvenient for users, if not downright Goddamn dangerous (Think national-scale 'phone infrastructure - no 112/911 service=big problems!).
We were well paid to have a negative attitude towards 'Product Whatwever' in those days - actually a realistic attitude from a Systems point of view - which was endorsed by the C-Suite as necessary for product quality. The attitude was that if Joe Public doesn't have an issue then we've done the job right.
Most of the time, we would end up fixing an issue, even the 'Very Low Probability, Medium Impact' ones on the (proven!) assumption that if Mr. Sod can stuff it up, he will.
With this modern 'continuous delivery' way of working, I find the 'edge' cases get ignored as a fix is seen as 'only a software update away' - no matter that the poor sap trying to use the thing has to wait weeks/months/forever for a fix.
Nobody wants to take the time and trouble to create a robust product any more, and it's hard to take pride in your work (About 50% of my output at the moment is crap, because 'timescales' and workload).
The world is increasingly run/managed by people who have absolutely no idea of the technicalities and complexity of modern systems.
Here endeth this rant.
Game title: Vacations of an engineering student.
Aim: to utilize 60 days of freedom with something worth useful in future career.
Game Modes: (1) Sit at home. (2) intern for some company
Mode(1) Sit at home.
>>Villains : Games,Netflix and movies, food, friend parties, late night sleeps, afternoon wake ups, trips (random villains)
>>Boss Battles : laziness, procrastination, loosing of interest in stuff you wanna do
>>reward on completion: more knowledge increase, better resume ,$0 earnings
Mode(2) : intern for some company
>> extra level before starting : apply for 100s of companies,interview rounds, test
>>villans : no self choice, work with shitty code, too much workload, less time for outside-work life
>> Boss battles: do stuff that you didn't agree to, less stipend, unwanted scoldings from boss
>> reward on completion : more work experience , lesser knowledge, more $
What would be your mode of playing this summer?3
Learn git! Git and GitHub basically opened up my eyes to so many more possibilities and helped me manage my workload between two workspaces. It turned me into a person who sshed into a server someone lent him to code into someone who uses github for everything and who can manage between two or three workspaces efficiently
Ever find something that's just faster than something else, but when you try to break it down and analyze it, you can't find out why?
I decided I'd test it with a typical discord bot-style workload (decoding a JSON theoretically from an API, checking if it contains stuff, format and then returning it). It was... 1.73x the speed of python.
(Though, granted, this code is more network dependent than anything else.)
Mean +- std dev: [kitsu-python] 62.4 us +- 2.7 us -> [kitsu-pypy] 36.1 us +- 9.2 us: 1.73x faster (-42%)
Me: Whoa, how?!
So, I proceed to write microbenches for every step. Except the JSON decoding, (1.7x faster was at least twice as slow (in one case, one hundred times slower) when tested individually.
The combination of them was faster. Huh.
By this point, I was all "sign me up!", but... asyncpg (the only sane PostgreSQL driver for python IMO, using prepared statements by default and such) has some of it's functionality written in C, for performance reasons. Not Cython, actual C that links to CPython. That means no PyPy support.
Took an extremely hard 3d course during my exchange. We started 40. 6 finished the course. The workload was big , but not difficult.
But I lost my virginity and then personal projects made me improve the skills 😊2
Ability to find jobs with better salary and less workload. I am tired of working 2 hours and pretending to work 6 hours mire.
Our client supposedly managed our Jira board yesterday in preparation for the release to live.
It was a mess. We have two people on this project - so our effective maximum workload is 10 days worth of tickets.
The current sprint plus the next have over 60 tickets in them, with the other "light" sprints having about 15 days worth in them.
I know you shouldn't get caught up over estimates too much, but they're in place for a reason.
The client really needs a reality check, and to be reasonable. When looking from a macro perspective he loses sight of all reason and scope, trying to grossly overfill what the two of us can handle.
A junior and student placement dev can only do so much.
I guess time will tell how realistic 16th April is..
Oddly enough, i have simultaneously been less busy and more productive since working 66% remotely.
I find myself with more time that feels "wasted" or not busy, but my metrics show that I have more production, better results, and far nicer documentation. A bunch of us also sat down and did a bunch of coursework on really putting together a domain script library for one click onboarding of new servers or new client setups. We spun up a bunch of new virtual environments that literally solved headaches that had existed for years that never got dealt with because of too many other tickets.
Some of our web clients freaked out at us because the business is moving away from doing maintenance of legacy web work (small to midsize businesses). But it didn't matter. Rather than respond with a "make them happy," the response was "well, we will get rid of them as clients. We need to focus our energy on the essential service sectors we support."
Hell, we even got an automated test that has been broken apparently since 2018 to work again.
Granted, the incoming workload has slowed down. But it's still interesting to me to see that despite the slowdown, there isn't any concern; its still paying the bills and we are getting rid of technical debt everywhere. Tbh, this has really been a good reality check.1
When you're in a two hour status meeting where you only had 5 minutes of work on the project -_- the workload was far overrated2
I really need to but a new laptop, my current 2012 MacBook Air with 4gb of ram can’t take the workload anymore. But it’s so hard to find a good alternative ! The new MacBook Pro sucks and it’s so fucking expensive (and I don’t want the silly touch bar). The competition isn’t much better, most laptops with the same quality doesn’t allow you to upgrade the ram and are about the same price range than the MacBook. Really , I miss the days we had good, affordable, upgradable choices (RIP MacBook Pro 2012).17
I've experienced it many times before but it's a really refreshing experience every time it happens. Motivation. It comes in many forms and means a lot of different things directly but an unchanging attribute of it is that it makes things way too easy and your work becomes enjoyable once it comes into the picture. Even dive into a dumpster of legacy spaghetti and dishing out nasty code review feedbacks feels GREAT when you're motivated. Context: I've spent like several months low on motivation, and it was one of the least productive times I've ever had, and now I just feel nice, y'know, able to actually do stuff and do it right.
Anyway. Rays of motivation to you, reader. Balance your workload so that you don't lose it like I did a while ago, and stay safe out there. It matters.1
I’m working on a side project just to not die from the repetitive college workload
I want to public the GitHub page so I can get more feedback then when I occasionally can show my teacher. As well as get advice and ideas from a larger group of people who all have more knowledge and skills than me.
But every time I think about pressing that button to show the world, I get worried about embarrassing myself, like this is my first large scale project all on my own. Using tools and a language I’m teaching myself in my free time with occasional advice from my teacher. What if it’s so horrible I just make a fool of myself
What does devRant think??1
Tldr: fuck me!
Ok this is only marginally dev-related, but I need to let off some steam as if I was valve. And this is, as I understand, the general purpose of this app.
So: fuck my university, I really love what I study, but the over all circumstances are far from ideal. In addition to that the pressure from the exams and the workload that is expected really stress me out to an extend where I suffer from anxiety and stress related health issues, which again makes me less able to do a good job, which again stresses me out more. This is an incredibly hard time for me but I am sure I will make it. Thanks for listening.3
Tired of seeing people showing off their bootcamp certification on LinkedIn as if they had just climbed Mount Everest, and as if they were about to enter the most glamorous field of work one could imagine.
OK I went through a bootcamp myself but I certainly knew I was still a baby upon completion of the journey and still consider I have a veeery long way to go today after two years of dev work experience. Also I knew working as a developer probably wouldn’t be as awesome as these bootcamps make it out to be. In fact it’s everything but glamorous when you take into account the stress, the dynamics with coworkers, POs, PMs, shitty management, wacky clients, weird demands, deadlines etc.
Don’t get me wrong. I enjoy being a developer and have more or less been able handle the workload and expectations. But for goodness sake stop drilling into bootcampers’ heads that it’s gonna be amazing and that they’re doing incredible things. Congratulate them for their hard work and then wish them good luck because they’re going to need it. Bootcampers, stay humble. Be prepared for the worst while hoping for the best3
What the fuck does Spring Break mean?!
A: Spring has begun.
B: Here's a break. Go have some fun!
But no, here in Buffalo, the snow doesn't give a shit, it keeps falling!
And no! You want a break? How fucking cute! Here are two projects for you to work on that you gotta submit , the first day after spring break ends! and a midterm exam the day after!
Stupid timeline, there is this company I was working for. It was sub-contracted by another company to do a government project. Government only pays after you deliver in my country. It was a complex system I must say. We were to work with my buddy on this project...now the timeline we were given were not feasible since another company had been given the same project and were not able to deliver. We had a meeting and discussed with our CEO about the project timelines. From the workload the feasible timelines were around 8months if we were to work as two devs. My CEO said that was not going to happen.. The only timelines that was allowed was not more than 3 months. So we suggest use an existing system to customize. .The meetings with the clients were to be weekly demos. So we choose to go with google docs api for the document management part. We were working around 20hrs a day to be able to achieve the target deadline..we management to complete the project within the given timeline..on the commissioning date of the project we faced a government panel and this was my worst disappointment. At the point of login we had to use Google email for business to obtain the API. Just as I was logging in the guy noticed and yelled. "Is that google account ?" and I replied yes..and he said "no need of proceeding since it will be of no use and they won't approve the system". That was my lowest moment in programming. I thought I had done the best project in my life as a programmer only for stupid man to declare my project as null. I felt like calling him son of a bitch but I knew that would have made me more angry...i just walked out. I went to the toilet and all I did was cry for the first time as I can recall.. My question was I was doing weekly demos. Why didn't they raise any questions by then so as to change the entire system??? Later after that demo we went and discussed about the issue and there was time extension. I redid the project using 'open office' but just before deploying the system I got a better job. I wasn't feeling like working on that project anymore. I want to release that project as open source. Recently after one year they haven't yet deployed the system. They are calling for my help. And I don't feel like helping after the humiliation...
Me: Yay! I’m getting more clients which means more income which means my accountant won’t look at me funny anymore when I say I’m still running a business and not a hobby! Go me!
Also me: I need $1400 worth of project management software subscription for 2 years (to get a discount) so I can manage the Agile workload among the developers and writers. I also need to recover $700 of accidental ad spend for that stupid Yelp account I forgot I had a “free trial” on. Guess I’m still running a hobby for a bit.1
Trying very hard not to slam down my shitty monitors in protest.
Was just informed by my manager that all coursework has to be directly related to my present role. Since I am not a developer than my classes will no longer be covered.
Same company that spent 15 grand just for the food at last year's company xmas party.
Even though I have already used my skills to revamp the company intranet, created macros that halved my workload and now able to understand the developer docs for 3rd party software we implement.2
Be honest. Given that you're not in crunch mode. Do you actually work 8 hours every day?
I have had some days but usually it's impossible for me to do actual work as a developer for 8 full hours, 5 times a week.
I feel that (without meetings), my ideal schedule for days of normal workload would be 5 hours a day. I'm strictly speaking about focused work, actual programming. Meetings don't usually rack up more than 2-3 hours per week for me.
I do my best to be in the office during the expected hours but I can't help but feel that everything about my engagement, focus and contribution at work would be better if I could just stroll in around 10, well rested, do some actual work, take a short lunch break, go at it again and go home around 15:30...
Because I feel like this I quickly get judgemental about myself if I come in at 9 and leave around 16:30 too often during a work week.
What are your thoughts on this subject?4
Having to relieve 50% of my boss' workload in DevOps. I'm 10% in, I don't know how this guy is still mentally sane.1
How pervasive is underestimating project/sprint work to land contracts and expecting devs to make it work in time?
How often are you expected to work more than 8?2
Today, I found out that the webmaster for the organization I volunteer at is using a security-by-obscurity PHP implemented design for the private data of our members. I've talked with him about it, but for a variety of reasons to do with organization and workload, it won't be changing.
This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...
Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Infra Guy: u trying to get set of specific folder for set of specific components?
Infra Guy: bash script with cp or mv will not work for you?
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place3
(imagine all of this said in Undoomed's "hey moron" tone)
Hey, moron, fuckin moron! How about if you're a noob with no actual programmer on your side, you just tell me so we can work it out together, instead of sending a moronic 4page "acceptance criteria" that pretend you know what you're talking about, and then bury me under loads of moronic noob questions that reveal you as thenmoron you are, all of that for a fuckin 50 quid?! I thought it's me being an idiot, not being able to do the task within two days timeframe, but now I see you're just too much of a moron to have any idea how much these things take. And now you nonchalantly mention a one-line one point from the four page document full of drivel, which (loads of moronism credit for me here) i didn't notice amongst all of that other mundane drivel, which actually like doubles the whole workload on the task, but your moronic document, which makes 3 parts of the same algorithm into three separate MILESTONES, makes this whole thing that nearly DOUBLES the workload into a shitty SEVENTH SUBPOINT of the completely unrelated first "milestone"?
FUCK YOU, YOU STUPID ROBBERY CHEAPFUCK, and fuck me for letting myself be tricked by all your fancy wordings that pretend you actually know what the fuck you are asking for, so i assumed you did, so I missed THE POINT, WHICH ACCORDING TO THE SEGMENTATION LOGIC OF THE WHOLE REST OF THE DOCUMENT SHOULD BE 3 SEPARATE FULL-SIZED MILESTONES, NOT A SINGLE SUBPOINT, YOU FUCKING FUCK!
... so much for still trying to at least a bit trust people.
FUCKING DISGUSTING MORONIC CHEAPSKATE FUCK.
and I can't even tell him to fuck off through the rectum he came here because he's all nice and polite so I would be the asshole!
"hey, please, can you build me a house?"
*house is basically finished*
"oh, great job, i love it, but i think you might have missed the fineprint in our contract that says that the house is supposed to stand inside an entry hall of a multibillionaire-sized mansion, so could we please sort that out and add it to the building real quick before i pay you the toolshed's worth we agreed on based on the contract? "
i thought i can be a shitty liar and a con man, but this is some next level shit that would be totally beyond my abilities to pull off...
YES I KNOW IT'S MY FAULT I DIDN'T COMB THROUGH THAT BULLSIT "SPECS" OF HIS LETTER BY LETTER TO MAKE SURE THERE'S NO CON BULLSHIT LIKE THIS HIDDEN AMONGST ALL OF THAT MUNDANE SELF-EVIDENT PSEUDO-TECHNICAL DRIVEL, SHUT THE FUCK UP.
fucking disgusting moron, pretending all nice and innocent probably even to himself because he HAS NO FUCKING IDEA WHAT HE EVEN ASKS FOR.
i bet it's one of those pukefucks who get an overpriced contract for 50k without even knowing or caring what programming is, because "i'll just outsource the core functionality of the app for 50 quid to some naiive idiot who lives in the illusion that people are not diarrhorea-worthy pieces of feces, and this other third of the app to some other moron for hundred quid and then i somehow outsource gluing it together to some third poor sod, and that's 49.8k quid of pure profit for me, yay"
and now i'm torn between three options, just cancelling the "contract" with a comment saying "fuck off, you con man", or cancelling it with a lengthy explanation why he's a know-nothing piece of shit who conned me already into having done something worth about 5x more than his shitty "acceptance criteria" requests, or just start conning and bulshitting him back, which won't net me any money, and waste my time, but at least will also waste HIS time, which might be nice because he seems to be on a tight schedule so if i play this right i might have the chance to sink his whole contract which might be mighty nice satisfying...
FUCK THIS, ALL OF THIS, FUCK HIM, FUCK ME, FUCK ALL OF YOU, I SHOULD HAVE STARTED FUCKING OVER EVERYONE RUTHLESSLY A LONG TIME AGO BECAUSE FUCK THE WHOLE WORLD, WHY SHOULD I CARE WHEN NOBODY ELSE DOES, WHY SHOULD I BE DECENT WHEN NOBODY ELSE IS, AND IT ONLY ROYALLY BITES ME IN THE ASS.
stupid fucking lobotomized fuck, IF YOU DON'T KNOW HOW TO DO SOMETHING, DON'T OFFER YOURSELF TO DO IT FOR MONEY AND THEN CON-SOURCE IT TO OTHERS YOU SHITTY BARFPILE!
Paycheck currently isn't compensating the current workload anymore.
I feel like we are missing 10 couple of hands while only three people are on vacation1
My employer is a subcontractor on a big and rather complex project, that already is way behind schedule and over budget (as these monsters tend to be). To get back some confidence from the client our principal moved an important milestone up two weeks. Which we protested against vehemently because the projected workload was already a very tight fit for the original timeline, without any reserve to speak of left. They wouldn't listen though...
The result? The whole team has to work the next weekends to have even the slightest chance of making the earlier timeline. Which is exactly what we told them would happen when they moved the milestone.
The worst? This isn't the first time this has happened while I worked on the project 😑5
Hey DevRant Fam <3
Hope everyone is doing very well as always!, i want to say sorry for my recent lack of activity in our community, i absolutely do miss communicating with everyone here as always dearly! there has just been too much going on within my life recently and i personally just needed a good break from everything , though to be honest more work was done than what i call my 'break', but guys not too much to say, about a week ago i turned 23 and things are finally starting to get a little better for me :-).
i'm also nearing the end of my degree in IT which this sem I've actually been working on a project for my first ever client with two other team mates, though i honestly feel that two of us are mainly carrying the team and the workload of course, but even so i must say i love learning all the time and its a real honor to do something i love and of course do with all of my heart :D.
as always everyone once again from the bottom of my heart i hope everyone is doing very well, and wish the best for you guys !
Milo <3 :D3
Hey i want to make a chat application for production workload with more than 100000 simultaneous connection and more than 1000000 daily active user which will scale 100 times in coming 1 to 2 years for Android. I have oauth based user authentication. This chat should be able to authenticate and verify authtoken generated using the oauth. What should i use? Xmpp, mqtt or something else. Can anyone who has worked on chat application help me.6
A lot of people have asked me to do their coding assignments for them. Ignoring the fact, that this lack of knowledge will not give good results in the next exam, i have done that a few times for my relatives.
So, being asked by externals I wont do that for free. (7-10h of workload) My question, what would you guys demand for such tasks. Is it worth the effort (students are poor)?3
Amazon what the hell.
You provide a cool RDS proxy which can be used to manage connection pooling which is especially useful for concurrent Lambda invocations.
But if you have an Aurora cluster and a read-intensive workload it is basically useless because it only sends traffic to the writer instance.
WTF?! Literally the one use case we have is the one thing it doesn’t do. AAARRRGGHHHH2
A new version of a service request queue processor was deployed to test. It was supposed to have a performance boost compared to the previous version. The performance is so good that the new transactions are still locked when SRQP attempts to process their workload, so it ends up issuing empty transactions in another module. Artificial delay time...
So I start listening to songs on a local platform in the morning while coding, switch to youtube playlists after lunch and have a developed a habit of switching to yet another platform by evening. It's not just switching genres based on moods and workload anymore but also having preferences between various music streaming platforms. Life is great with so many options available.3
A question to all the guys and girls that launched a startup: How powerful was your infrastructure at the beginning? How many requests per seconds did you encounter after the first few weeks after the launch? Did you distribute the workload to different systems in the first place or was that something that was done later?
I am currently working hard in my freetime to get my first project done. As it's still a side project, that I am working on in my freetime, I want to make the launch as smooth as possible. I imagine that it's really hard to make serious changes to the whole design, just because the initial approach doesn't scale well enough. So I am currently in the process of stresstesting the whole infrastructure. But during the stresstest I realized that I don't really know what I should aim for.
What I also want to avoid is, that I am wasting my time on creating a large infrastructure of database servers, caching instances and load balancers that isn't really necessary for the initial launch.
Would really love to hear your experiences on that.3
Have a question for more seasoned developers/techies in the industry. I started my first software development job 7 months ago and I am contract to hire. There’s only two developers (including myself) on my team and we’ve been working on two separate projects that’s apart of a bigger system. He was a contractor but because our company took too long to get back to him about converting he interviewed and accepted an offer at Amazon (don’t blame him). Now I have to take over his project as well as mine which would be overwhelming to say the least... our team is almost entirely remote so it can be difficult to communicate sometimes and our company is heavy in process so development moves slow. Should I start looking for other opportunities or should I stick it out and gain experience even though the workload is unrealistic?5
Started my internship last month. It's been alright although quite disappointing. I expected to be developing more but they have me doing website management using their CMS. I know it's needed for websites and all but is this really it?
Hope my workload picks up soon..3
Having a dilemma... I need help with my gaming projects. I know a guy who I could train since he has lots of potential but Im having trust issues. Its because I invested around 10k into my codebase and Im afraid to give access to that guy since I suspect that he might use files and some day run away to make his own project. So im back to square 1 again which is loosing my mind with this huge workload. What should I do? Should I just say fuck it ant make him sign some air tight NDA agreement? Even then he could stand up and leave 2 months in and open a competitor project if he doesnt like my management style...3
Ending my internship this week. Past couple of months have been really stressful. Being a startup, I assumed the workload would be high but never guessed it would be this much. They make the interns work just as hard as the full time employees for less than 1/4th the pay. Is it always like this at startups? Man, never worked for more than 8 hours before but 12-14 hours of work is normal here. I just want to survive the week. Wish me luck!1
I hate it when I'm knee deep in projects that need to be done before the new CI strategy starts two avoid a three week long full test every two weeks and then my dear boss comes up with having me do the planning for the next testphase while my coworker is scrolling through 9gag. I mean, sorry old man but either I automate this monstrosity of thirty million layers of 'naturally grown', ill documented, identifier lackimg piece of shit or I can do the fucking schedule. My mother isn't an octopus, i've got only two arms...
Tl;dr: Why do non programmers always heavily underestimate the time shit needs to get done?