Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "disorganization"
Four meetings today.
Legal was not involved in legal agreement changes until I refused to make them without Legal signing off. Legal changed several things, leading to:
Project scope changed size from large to minuscule to small to medium.
Details changed at every step.
Despite being incredibly structured and process-heavy, people at this company are so disorganized. 😕4
They gave me a file, .php, that was the entire webapp. THE ENTIRE THING IN A SINGLE FILE. It's frustrating that I have to organize this before I even start working on my tasks.
I guess its not super horrible since it's a rookie project but it's still horribly and unnecessarily time consuming.6
So, the uni hires a new CS lecturer. He is teaching 230, the second CS class in the CS major. Two weeks into the semester, he walks in and proceeds to do his usual fumbling around on the computer (with the projector on).
Then, he goes to his Google Drive, which is empty mostly, and tells us that he accidentally wrote a program that erased his entire hard drive and his internet storage drives (Google, box, etc.)...
I mean, way to build credibility, guy... Then he tells us that he has a backup of everything 500 miles away, where he moved from. He also says that he only knows C (we only had formally learned Java so far), but hasn't actually coded (correction: typed!) in 20+ years, because he had someone do that for him and he has been learning Java over the past two weeks.
The rest of the semester followed as expected: he never had any lecture material and would ramble for an hour. Every class, he would pull up a new .java file and type code that rarely ran and he had no debugging skills. We would spend 15 minutes trying to help him with syntax issues—namely (), ;— to get his program running and then there would be a logic issue, in data structures.
He knew nothing of our sequence and what we knew up until this point and would lecture about how we will be terrible programmers because we did not do something the way he wanted—though he failed to give us expectations or spend the five minutes to teach us basic things (run-time complexity, binary, pseudocode etc). His assignments were not related to the material and if they were, they were a couple of weeks off. Also, he never knew which class we were and would ask if we were 230 or 330 at the end of a lecture...
I learned relatively nothing from him (though I ended up with a B+) but thankful to be taking advanced data structures from someone who knows their stuff. He was awful. It was strange. Also, why did the uni not tell him what he needed to be teaching?
Don't get me wrong, I am a huge fan of disparate microservices when building applications. I started 4 years ago building monolithic applications on symfony, laravel and .net.
SPAs have not only made my applications more flexible but have allowed me to build more flexible front ends. But I almost ALWAYS have this dirty, unorganized feeling when working in this microserviced approach.
My data always feels scattered. Because my backend doesn't have as tight of a grip on what view is being rendered and what data it gets, I am always left with a sense of disorganization and lack of security. I have more anxiety that my application will unravel at any given moment then I've ever had and that keeps me up at night.
Does anyone else feel this way when working with disparate systems?
And dont even get me started on mongo. Again, I love it, but the feeling of disorganization is intense when using it.4
I hate my company more and more everyday. 1. Release on Friday afternoon. 2. I should be home but that bitch decided that she wants to change something now, because she forgot to do that before. Of course, this shit cannot wait until Monday.4
So, I just finished a semester project on Software Project Management, and this was my self analysis and my conclusions, along with my analysis of my team. I think some of you will relate. Hope you enjoy the reading!
My main contributions to the project were helping reviewing the documents syntax, to make sure it was smooth and easy to read with a good english level, working on the systems architecture, coding the application, helping measuring problems within the project and putting people to work by distributing tasks.
I tried to help whenever I could with things that were not assigned to me, even though we are a team, everyone must do what they are assigned for, otherwise disorganization will be installed and everyone will derive from what they are doing to focus on a single thing or point and that would cost us time. I tried to avoid that to see if people could be capable enough of fixing the problems presented to them with the least help possible, making that an example for future use so they don’t always rely on others to get tasks done and to be more independent. Also, helping others figuring out what they were supposed to do helped the team wasting less human resources and consuming less time, which lead to some faster developments on specific tasks. Making the impossible possible was kinda of a weekly routine when the deadline approached because time was short and sometimes tasks were not finished when they should be, so, in a way I helped speedrunning documents to see if they were close to presentable to the client.
As the overall performance, there were highs and lows, where some members worked more than others and that is not fair for everyone because that kept happening again and again, so, my point of view performance wise is that we behaved wrongly when it came down to it. Some of us kept on pushing tasks to others and continuously criticizing over other people’s work without having a logical background to motivate those critiques neither providing solutions to the problems encountered. Well, that couldn’t end well, and it didn’t. It brought our performance down and ended up causing a lot of damage on the project itself.