Me and my wife are software engineers
Started dating while doing a project together
I guess you could say that we...
MERGED WITHOUT CONFLICTS

The most stupid question you can ask at an open source software event?

"So, this system, is it open source?"

I asked this to a guy at a stand about the system he was presenting (forgot the project name).

He stared at me with a wtf face and then replied with "....yes.... of course.... this is an OPEN SOURCE software event?!"

I felt quite fucking stupid.

I always like to approach a new coding project by concentrating on the data model first. I've seen a lot of projects built on extremely convoluted database structures and it really hurts because it makes it hard to add new features to the project.

So I look at the requirements of the new project and try to come up with a basic data model. Then I like to think about what logical future additions to the project could be. And using those, I try to see if the data model is flexible enough to be able to handle those additions fairly easily or if complex migrations or hacks would be needed to account for new use cases and features.

I think once you have a solid data structure and database technology, planning out an API or rest of the software is pretty straight forward. I like to create reusable pieces of middleware early on in the project which makes it easy to apply consistent functionality with ease to different API endpoints.

My last internship. When acquiring a new project and having to give an estimate the boss/sales guy always went to the programming team first to ask them what the estimate was and then communicated that back to the client(s).

Asked him why he does that because many companies don't:

Well, the programmers are going to write the software so why the hell would *I* be the one who gives the fucking estimates?

Yes that was a good boss.

Let's get rid of the developer training: Pair Programming

Let's get rid of the software testers: Test First Programming

Let's get rid of the project managers: Agile

Let's get rid of the project planners: Scrum

Let's get rid of the system admins: DevOps

Let's get rid of the security guys: DevOpsSec

Let's get rid of the hardware budget: Bring Your Own Device

Let's get rid of the servers: Cloud Computing

Let's get rid of the other scruffy guys: Outsourcing

Let's get rid of the office space: Home Office

Let's get rid of the whole fucking company: Takeover

Almost every really successfully project...is open source.

Some Examples:
- Linux
- PhP
- Node.JS
- The Chromium Engine
- All the Apache Stuff
- Unreal Engine(WAS closed source)
- nginx

and so many more

Open Source is the best way to build known, stable and useful software

True..

A fresh graduate software engineer applied to the company and passed the coding exam.

Manager: Wow you got a very high score. Good job.

Applicant: Thank you sir. So am I hired?

Manager: Yes of course. You will be the team lead for one of the project.

Applicant: Wait wut????

I just quit my job!
The company I worked for is a small company founded in Jan of this year and I was there since the early days but wasn't a founder nor a partner.
It was me who decided on which tech stack we should use, which languages, what servers to use, best practices and almost anything related to development. I was the lead developer and project manager for the biggest project they had.
But they decided that I don't deserve to be a partner. I was making more than 50,000 SDG per month for the company but only paid 6,000. The worst thing is that the partners don't know shit about software development. They have no vision for where should the company be in the future.
I just had enough. I already had my own software dev business before joining them, and it was successful.
I am going back to building my own company with my own vision.
I know I made the right decision, but it still hurts leaving a company after u made it what it is today. It is like your own baby and you are abandoning it.
Hopefully, it is for the best.

You know you're not going to have fun when you get assigned to a project which required to install this software...

My sister's college is making them do their Final Year Project in VISUAL BASICS 6.
I mean WHY !?!?
Why use a software that's discontinued and they'll never use?

So as quite some people know on here, I am strongly against closed source software and have a very strong distrust in it as well.
So next to some principles (and believes etc etc etc) there is one specifc 'event' which triggered the distrust in CSS (No not Cascading Style sheet, I mean Closed Source Software :P). So hereby the story about what happened.

I think it was about 5 years ago when a guy joined my programming class (I wasn't in uni although I studied but for the sake of clarity, lets just call it uni for now (also, that makes me feel smarter so why the fuck not!)) in uni. He knew a shitload about programming for his age but he was convinced that he was always right. (that aside)
Anyways, at some point we had to work in groups on this project (groups for specific tasks) and he chose (he loved it, we hated it, he had the final say) Trello for 'project management'. He gave everyone (I was running Windows for a little bit at that moment because the project was in C# and the Snowden leaks had not arrived yet so I was not extremely uncomfortable with using Windows, just a lot) this addon program thingy he created for Trello which would make usage easier. I asked if it was open source, he replied with 'No, because this is my project.' and although I did understand that entirely, I didn't feel comfy using it because of it's closed source nature. Everyone declared me paranoid and he was annoyed as hell but I just kept refusing to use it and just used the web interface.

*skips to 2 years later*

I met that guy again at the train station at a random day! Had the usual 'how are you and what's up after a few years' talk with him and then he told me something that changed my view on closed source software for most probably the rest of my life.

"Hey by the way, do you remember that project of a few years back where you didn't want to use my software because of your 'closed-sourceness paranoia'? I just wanted to say that I actually had some kind of backdooring feature build in which (I am not going to say what) allowed me to (although I didn't use it) look at/do certain things with the 'infected' computers. I really wanted to say that I find it funny how you, the only one who didn't give in to my/the peer pressure, were the only one who wasn't affected by my 'backdoor' at that moment! Also your standards towards the use of closed source software probably played a big part probably. I find that pretty cool actually!"

Although I cannot confirm what he said, he was exactly the type of guy who would do this IMO (and not only IMO I think).

So yeah, that's one of the reasons AND the story behind a big part of why I don't trust closed source software :).

Crawling through some old code and asking myself:

-Who wrote it?
-When did he write it?
-What did he think then?

-Me
-Last week
-I have no idea

Am I the only one who hates it that everything needs to be done in JavaScript nowadays?
Why can't you just start writing native software again? Why does every program need its own fucking browser engine and at least 200MB of RAM to do nothing but show and edit text?
I want to have fast and streamlined software again and use my resources for important things. So much software that is called fast or lightweight isn't either. It's just a little less heavy and slow than the software it tries to replace.
I don't use C all the time, but maybe looking into Qt instead of electron might be a start.
I had a project where I could convince my tutors to let me use C++ instead of JS and they were surprised how fast my application started even though it only consisted only of a empty window with a status bar. How far have we come that we even need to think about performance when opening an empty window on modern hardware?

rant

The Java course at our Uni requires us to do an end semester project - A Java App with Swing for GUI and some Multithreading code in it.

They asked us to upload the code to drive. I was bored and was checking out my friends' projects.

The code below is what I saw in one of the projects. They have simply called a thread with an empty run method because the project required to use multithreading concepts, wtf.

But then, It is no surprise to me cause these are the people who memorize code and vomit code for marks.

I am worried that people are going to be awarded degrees and called software engineers.

God save the software industry!

Software engineering and developers and life cycle of Project 🤣🤣🤣😂😂

FUCK VISUAL STUDIO ANBD EVERYTHING IT FUCKING STANDS FOR. PIECE OF SHIT IDE CANT HANDLE MORE THAN THREE FUCKING WINDOWS AT A FUCKING TIME WHY CANT A BILLION DOLLAR MOTHERFUCKING COMPANY MAKE COMPETENT SOFTWARE FOR ONCE? WHY IS MICROSOFT SO FUCKING AWFUL IN EVERYTHING IT DOES? WHY THE FUCK IS THERE NO AUTOMATIC VERSIONING LIKE EVERY CIVILIZED BASIC FUCKING IDE THAT EVER EXISTS? WHY DO I HAVE TO FUCKING MANUALLY VERSION MY FUCKING FILES? WHY THE FUCKING FUCK IS VISUAL STUDIO FUCKING GOING TO A FILE I USED 300 YEARS AGO WHEN I DEBUG AN APPLICATION? MOST USELESS, UNINTUITIVE PIECE OF SHIT SOFTWARE IVE EVER USED. IF YOU ARENT USING SOME GODDAMN SERVER SOLUTION TO KEEP TRACK WITH YOUR PROJECT VERSIONS, GOOD EVER FUCKING LUCK RECOVERING LOST CODE BECAUSE FUCKING MICROSOFT CANT DO WHAT FUCKING INTELLIJ DID 5 MILLION FUCKING YEARS AGO

That time I joined the robotics club and made the pid loop for the robot was one of my favorite projects. I learned ROS, and I created the entire chain of software and hardware to control six motors. That one project set up my experience for the next 4 years and led to a few jobs. I miss robotics.

One of the dev in my team literally asked us (other student devs, professor, and a guy from the company we were working with) this question during a weekly scrum meeting:

"Who is this Jason you guys keep talking about? He never showed up to any of our meetings!".

A bit of context: we were 6 weeks (halfway) into our FINAL YEAR PROJECT for a bachelor in software engineering...

I thought at first he was joking...

TL;DR: a good friend recently finished building an electric car from scratch with a team and I bought him a C++ devDuck as a congratulations gift!

one of my best friends recently presented at my colleges capstone rollout, and his teams project was to literally BUILD AN ELECTRIC CAR FROM SCRATCH. all the circuits and everything, designed from scratch, and nobody else on the team was very good at software, so he pretty much wrote the software himself. I just ordered him a C++ devDuck as a congratulations gift!

It happened 2 nights ago.
We had a whatsapp project for the distributed application programming class, my project mate and me were coding for 2 weeks whole day to finish it, especially with the end-to-end encryption feature that teacher asked, till 2 nights ago the project was trash, the private chat wasn't working and and nothing else is done we had only the UI, we was really doomed especially we had 1 more day to deliver the software, and we decided to deliver the project as a trash and get marks from the UI and the presentation.....
Till the night before deadline at 8 pm
I wanted to try fix some interface pictures and to make it better......
The next thing it was 6 am and the project is full working..
When I told my project mate he was not believing, I had to swear multiple times fot him and hat to go and show him the project by the eye.
We delivered the prohect and got 22/25 😁😁😁
It was incredible I didn't believe my self at first place.
Sory for the long story 😓.

I remember my first "Software Engineering 2" class at University. The teacher, a pompous son of a bitch that later on gave proof of his vast ignorance, greeted us with
"so ... You call yourselves programmers, right? What's the biggest program you have ever wrote? Something along the 100, maybe 200 lines of code? ..... If you've never written at least a MILLION lines of code software, you're not a software developer"
Even at that time, with my lack of experience in software development, I had that feeling in my guts telling me "writing myself a 1M lines of code software .... Brrrr that's something I hope I'll neve have to do in my life"
Turned of he was one of those dinosaurs stuck with the love for gargantuan monoliths of software like they used to do.
Just to dive you the whole picture, the course had ZERO software development and focused only on how to manage wonderful waterfall projects, how to write all types of software documentations and the final project was ... Writing a ton of documentation so boring and useless that even he didn't care to read through.
we still laugh at the episode when another group asked us to borrow one of our documents and after one day they asked "hemm ... Have you really sent this to the teacher?" "yes, why not?" ".... at page 23 someone left a comment saying 'what the fuck is this shit?'"

TL;DR: Tech companies. Don't ask for loyalty if you don't care about your people.

> I'm a gud Dev (and a gud boi).
> The company assing me a cool project.
> The company promised pay me the training. about that suite. They didn't.
> I finish the project and i'd accomplish the task with more effectivity than excepted.
> My company won an interview about "the success case of the implemented software and its integration with our software". They denied me the chance to fly and go to the meet. Instead they will send another guy...
> I asked for a "salary adjust" cos I'm finishing my engineering degree and my good work. They declined.
> Next day I'd present my volunteer job resignation within 15 days (because laws demands that). I have a better job option with +20% my actual salary and a lot of benefits. And they needs me ASAP.
> Everybody look at me shocked and if I am a traitor.

What the f!$-k they did expect?
My unconditional loyalty?
🤣🤣🤣

I was engaged as a contractor to help a major bank convert its servers from physical to virtual. It was 2010, when virtual was starting to eclipse physical. The consulting firm the bank hired to oversee the project had already decided that the conversions would be performed by a piece of software made by another company with whom the consulting firm was in bed.

I was brought in as a Linux expert, and told to, "make it work." The selected software, I found out without a lot of effort or exposure, eats shit. With whip cream. Part of the plan was to, "right-size" filesystems down to new desired sizes, and we found out that was one of the many things it could not do. Also, it required root SSH access to the server being converted. Just garbage.

I was very frustrated by the imposition of this terrible software, and started to butt heads with the consulting firm's project manager assigned to our team. Finally, during project planning meetings, I put together a P2V solution made with a customized Linux Rescue CD, perl, rsync, and LVM.

The selected software took about 45 minutes to do an initial conversion to the VM, and about 25 minutes to do a subsequent sync, which was part of the plan, for the final sync before cutover.

The tool I built took about 5 minutes to do the initial conversion, and about 30-45 seconds to do the final sync, and was able to satisfy every business requirement the selected software was unable to meet, and about which the consultants just shrugged.

The project manager got wind of this, and tried to get them to release my contract. He told management what I had built, against his instructions. They did not release my contract. They hired more people and assigned them to me to help build this tool.

They traveled to me and we refined it down to a simple portable ISO that remained in use as the default method for Linux for years after I left.

Fast forward to 2015. I'm interviewing for the position I have now, and one of the guys on the tech screen call says he worked for the same bank later and used that tool I wrote, and loved it. I think it was his endorsement that pushed me over and got me an offer for $15K more than I asked for.

Why THE FUCK would anyone make a totally free (in the sense of price; gratuit) software project, and then not make it open-source?

What is the benefit of stifling the development of your own project when you have no monetary gain from doing so?

We made a software for hospitals in my old department. The senior Dev kinda gave me the software, because he thought it sucked and was perfect for a newbie like me. I really loved my work and gave everything I had to improve the quality of software, introduced tests, refactored old smelly code and talked with the product manager to overhaul the ui. Several months later this little shit project the senior gave the newbie, was a huge success and better than any thrash that the senior has created. The senior was really pissed, so everytime I had some days off, he tried to sabotage me in any way. I couldn't take that and many other things anymore, so I left the company. The most tragic part is, that my software could become a massive foundation for the company, but after I left they abandoned it. I still had some good contacts within the old company and they said, that the senior dev told everyone how bad everything was, that I have done through the years and that they can't even describe how bad the architecture of the software is. tl;dr fuck off!! I've done so much things for the company and they never appreciated it. I'm glad I quit that job. Best decision ever!!

Fucking finally. I got a job... No one is probably gonna give a shit because it's your average governmental drone position but I wanted this for a very long time...

** drum roll **

Customs and immigration officer!!!

Thats right! Deported! Deported! Deported! *hot chick* welcome to our country!

Best thing is... Now every project can be a side project... I can chillax and build software in my spare time... I love it.

I started to work in a new project for a house architect, basically a management system for his studio. Well, guess what? Twenty years ago he programmed some sort of software using BASIC, and of course that means he knows exactly how software works!

Worst kind of stakeholder, like going to the doctor and telling them how to diagnose, because you used a thermostat once.

I started a hobby software project producing TV graphics for eSports racing events.

At first it really only was a hobby without getting paid at all. After a few years we got our first customer for whom we build a fully functional TV graphics package for their broadcasting network for about 350€ for roughly 80-100 hours of work total.

This was the first time I was getting paid for my own software and since it was just a hobby, it was nice at that time.

After a few more years in the business, we are lucky enough that our software is used by the game developers themselves and big car companies for their eSports events and we are able to make a decent profit from our small hobby.

Took only about 5 years. So never give up, I guess. :)

I just lost faith in the entire management team of the company I'm working for.

Context: A mid sized company with
- a software engineering departmant consisting of several teams working on a variety of products and projects.
- a project management department with a bunch of project managers that mostly don't know shit about software development or technical details of the products created by engineering.

Project management is unhappy about the fact that software engineering practically never sticks to the plan regarding cost, time and function that was made at the very beginning of the project. Oh really? Since when does waterfall project management work well? As such they worked out a great idea how to improve the situation: They're going to implement *Shopfloor Management*!

Ever heared about Shopfloor Management? Probably not, because it is meant for improving repetitive workflows like assembly line work. In a nutshell it works by collecting key figures, detecting deviation in these numbers and performing targeted optimization of identified problem areas. Of course, there is more to Shopfloor Management, but that refers largely to the way the process just described is to be carried out (using visualisation boards, treating the employee well, let them solve the actual problem instead of management, and so on...). In any case, this process is not useful for highly complex and hard-to-predict workflows like software development.

That's like trying to improve a book author's output by measuring lines of text per day and fixing deviations in observed numbers with a wrench.

Why the hell don't they simply implement something proven like Scrum? Probably because they're affraid of losing control, affraid of self managed employees, affraid of the day everybody realizes that certain management layers are useless overhead that don't help in generating value but only bloat.

Fun times ahead!

I’m a college senior now. The best CS class I ever took was in high school. Our teacher didn’t know how to write software, instead he went around on day one and has us submit proposals for year long projects.

With each project, we had to find mentors in the industry who could help us if we got blocked. Every other week we meet with the teacher (who was more a facilitator) and described how the project was coming.

The results? We had final products that were well beyond the expectations of a high school and more impressive than any project I’ve seen at my university.

Why can’t all STEM programs be like that? Students have incredible ability, but are blocked by traditional education. Let students set the bar.

Software engineering project discussion:
Boy: Sir, my project is a client to manage files stored on different cloud file storage systems at one place
Faculty: Boring idea. Very easy to implement, No scope of scalability, etc
Girl: My project is an app to display the weather information
Faculty: Omg! What an innovative idea! I'm surprised how no one though of this before!

No, I do not wish to work on your Scrum-managed project.

I do not wish to contribute to the Taylorism of my profession.

I do not wish to be an interchangeable cog in your software sausage machine.

I do not wish to be tracked by some pointless metrics like a call-centre worker.

I do not wish to bust my tight, cute ass to sprint after some idiotic management request that could have been factored in earlier.

I do not wish to obtain some piss-ant qualification that "authorises" me to do my job.

I do not wish to be party to your lie that technical debt will be avoided by refactoring---whatever the cost.

I do not wish to contribute to the death of software engineering to have it replaced by software development.

Agile? Sure. I can pick up the phone and talk to the client, users and fellow devs. After all, that's what it FUCKING MEANS. Communi-fucking-cation.

See that burndown chart? See your anus? Know what's happening next?

Fuck Scrum and every fucking bottom-feeder that is scamming a living by promoting it. You're killing this business.

Hugs and kisses,

Platypus

this happened in the first project of a small software company.

the contract said: project will be finished only until customer satisfaction

the customer was never satisfied. So, the company had to close and open with a different brand name

!rant For my uni project I have been developing a anti ransom-ware price of software which had a main purpose of damage limitation/containment in a business environment.

Some course mates were critising it saying yeah when is ransom ware ever really looked at these days, (they developed a chat app), then the news struck about the Nhs hack and now my Lecturer can't get enough of the project and suddenly the marks for real world application seem to be in my favour 🤘

Again not a rant, just a nice feeling after spending so long on my work.

That glorious moment when you realize that the toy project that everyone scorned you for wasting time on three years ago has become a central building block of your company's software lineup.

In 15+ years of full time work as a C++ software engineer there is one tool that I always hated: CMAKE. What a fucking pile of shit, seriously, every time there is project that uses it I simply cannot build said project with one click. In all these 15 years working in different companies the only reason people speak about cmake is to avoid adding source files to multiple projects (VS, XCode, Android).

I'm not some kind of newbie: I've make cmake projects myself, I've build hundrends of projects that use cmake and I even contributed fixes to their code. I still believe that cmake is garbage that should stop to exist.

A misconception that software engineers just sit in front of their laptops and code 40 hours a week, with no social interaction.

A software engineer’s job is actually pretty social. Personally, I probably spend around half of my time interacting with people. This could be partially due to 1:1, team, and other meetings. But a large part of it is spent in bouncing off ideas about your project with your project mates (especially during the planning phase), chiming in the conversations about some recent or urgent problems to help find or propose solutions, answering others’ questions, organizing some events, etc.

Of course, I do need some dedicated uninterrupted time to focus on programming and to get into the zone, but it’s certainly not the only activity I do at work. The main point to understand is that the software engineering is not a solitary, but a social job.

Overall, I’m very happy with my profession. The enjoyment I get out of my work vastly outweighs all of these points combined.

I have some how managed to put my self in a Software Architect role with a salary of a Junior developer, My team, who are even more junior as a swath of fresh grads are looking up to me to design this project. I am doubting my abilities and am worried I am going to under deliver, how am I ever going to learn this. Stressed.

Manager: Hey software engineer, how's the project going?

Software Engineer: Good, just debugging my code.

Manager: Debugging? What kind of bug are you trying to fix?

Software Engineer: The ones that make my computer turn into a lava lamp.

Manager: Ha ha, very funny. But seriously, how can I help?

Software Engineer: Well, I need a bigger monitor. My current one doesn't have enough real estate to display all the errors.

Manager: How about a second monitor?

Software Engineer: No, I need a bigger universe.

Manager: I'll see what I can do. In the meantime, keep coding. We have a deadline to meet.

Software Engineer: No problem, I have all the time in the world. I just need to find a way to slow down time.

Manager: I wish I had your optimism. Just let me know if you need anything else.

Software Engineer: How about a unicorn? I heard they're good at coding.

Manager: I'll see what I can do, but in the meantime, stick to using a keyboard.

He was a nice guy, skilled, reasonable, a lot of knowledge.
Until he said "I'm going to assign a girl to your project, BUT don't worry, she is very good"

I was about to jump, but handshakes and further jokes went on and I wasn't able to speak up.
Plus he is the CEO assigned by the investors to be our new software provider.

Puking.

In school we had to create a project using Java and SQL we created a library management software.

In India a teacher from other school comes to check your projects and allot marks. (They just take a viva and give a marks)

Out of the whole class he asked me to present my project (they usually don't look at it ) and he checked each and every file asked a lot of questions.

Viva went on for 45 mins (usually 10-15 mins) and when the whole class is looking at you like what did they make.

Yeah that made me feel like a badass dev.

Got a client who Always delays payment (~2weeks) and is rude and ignores me after I deliver. As a freelancer and Student I rely on the money and on my time. So I will deliver tomorrow the next project, guy promised he will pay on monday, but I count with weeks again. I have developed a locking mechanism so I can lock the whole Software from my Cloud in case he wont pay on time. What do you guys think?

Hey I have an idea ! Why not we developers normalise the IKEA way of delivering project to customers? Let me introduce the DO IT YOURSELF software .

Here's how it is done , we set up environment for the client , write manuals , design and pass it over to the customer , let them DIY it by code for themself!

Found this in my Software Project Management textbook. Seems right.

Do these NPC devs even read the README of a project before spewing some dumbass stackoverflow like garbage in an issue thread?

Do your damn job. Being a good software engineer is not like TiKtOk or cHaTgPt where some "magical" answer or entertainment is spoon fed to you, do your absolute best to solve it yourself first, before causing more chaos out in the opensource world.

I walk into the kickoff meeting today. The first part of this project had 5 developers and a project manager. Former project manager handled communication and sheltered us from bullshit. We built an amazing piece of software in a very short time. Customers were so amazed that they decided to reboot the project, boost the funding by several million, and let us go again. They specifically requested the same team.

Now the team looks like this: the neediest tester guy, a UX lady that doesn't have any UX background, an agile "visionary", a project manager that doesn't understand how development works, a solutions architect, 3 COTS platform specialists, a devops specialist, and an account lead. They have booked all kinds of workshops and other shit to kick things off.

So development capacity is only 60% of what it was. Management ratio was 1:5 before. Now the management ratio is 9:3. The new project manager thinks developers should be on more customer calls and responding to all customer emails during sprints. We already built this system and devops pipelines end to end. The COTS people, solutions architect, or the UX person can't program. They want us to magically convert this custom application into one based on COTS. What we need to do is make the rest of the business processes that we omitted, integrate known feedback, rework the backend, build better automated testing, improve logging and reporting, add another actor to the system, add a different authentication method, and basically work through the massive backlog.

How do they think this is going to work? Do they think we can download a custom engineered enterprise grade software system from Microsoft and double click all the way to customer satisfaction? The licenses alone are too much for the customer on an ongoing cost basis. I guess we can discuss it during the agile team-building weekend at some remote lake that the team "visionary" has set up. For the sake of fuck.

Like development isn't hard enough. Hire two more developers and lose all of the dead weight. Get a project manager that won't let the trivial shit roll down on us. What the fuck.

On my last project the customer gave really high reviews and asked me back as a senior engineer. First day back I meet the new PM and ask what I'll be working on.

He responds, "We have a printer that's not working..."

Of course I'm like wtf but then it quickly becomes apparent I'm writing the interface instructions between the software and printer....

Still, I'm back as over priced tech support to fix a printer!

Every project ever :
Initial plan :
||===================|| 100 %
Actual submission
||==|| 13%

- Not enough money!
- Not enough people!
- Not enough time!
- Not enough resources!
- Hardware not supported
- Software not supported
- My team are useless
- God didn't like it. :/

Words of wisdom

First year: intro to programming, basic data structures and algos, parallel programming, databases and a project to finish it. Homework should be kept track of via some version control. Should also be some calculus and linear algebra.

Second year:
Introduce more complex subjects such as programming paradigms, compilers and language theory, low level programming + logic design + basic processor design, logic for system verification, statistics and graph theory. Should also be a project with a company.

Year three:
Advanced algos, datastructures and algorithm analysis. Intro to Computer and data security. Optional courses in graphics programming, machine learning, compilers and automata, embedded systems etc. ends with a big project that goes in depth into a CS subject, not a regular software project in java basically.

"Adding more people to a late software project will make it later." - Fred Brooks

Dear Client,

You said it was of paramount importance that this software work flawlessly. I've worked hard to make it so, even when your indecision and lack of attention to detail indicate you don't care as much as you say and have made the project late.

Yesterday when I handed you a step-by-step user acceptance test plan, you delegated it to someone not as familiar with your specific requirements. You said you don't have time for such things.

I will remind you of those words when the project launches and you find something you dislike.

Sincerely,
Me

Murphy's law is completely true.

Deployed my own software the very first time on a customer system on monday.

Today I'm at a job college class when my boss calls me: "...Hey yeah (unrelated) (yadda yadda) the software does not function for anyone").

I fucking knew it.
We don't have a proper project planning nor a real project manager/lead, we don't do QA, and now it's gone to shit.

I did my own testing extensively on monday & Tuesday, everything looked alright and worked like a charm.

I'm looking forward to the weekend already...

As a software house, we have many teams on different projects. One project was due to a Thursday, and the PM asked the team 1 week before if they could work over the weekend since there's a lot of things to do.

On the Friday before, one of the devs showed up a bit later than usual (around 10am), but ok...

After lunch he asked to talk to HR and also the boss. They talked for around 2h, then he started to say "goodbye and good luck" for everyone.

The project was on fire and he just... leave.

On the next 2 months another 4 people leave the company. All from the same team/project (but not with a big surprise like him).

Apparently, the team was constantly complaining to PM and boss about unrealistic deadlines and constant requirements changes, but they didn't did anything about it. Just when more than half this team had left the company they started to rethink this actions to this project and the others on the company.

Decided to start a new project tonight. A `brew upgrade && brew update` here, a software --install --restart` there. An hour from now I'll be ready for bed and have yet to punch a line of code.

Always best to start tomorrow anyway.

Code fuckup day or what?! After two weeks where I wasn't on my project and a co-worker handled it, I came back to my project and reviewed what he had done so far.
Me: "I don't understand how this new code part here can work?"
Him: "Uhm, actually, it doesn't, somehow."
Me: "..."
Then he had checked in his stuff with spaces while the whole project is with tabs. And variables that were used in a different way, but still under the old name, now completely misleading. Bypassing existing infrastructure and defines with "just for this case" hacks. But the best was tracking higher level state by peeking into lower level data buffers, even pulling out their data definitions into global header files - instead of using proper states in the higher layer itself.
NOT! IN! MY! FUCKING! PROJECT!!!
So I spent the day cleaning up the shit to fight off software rot right in the beginning.

Proud moment this week. Have been making my first contribution to Open Source software. And a huge project too. I hope it will long continue :)

Working on a school project, a teammate created a git repo, gave us all the link, but no push access, told him about it, I gave up explaining.

I still dont have push access after half a day.

Also another team member doesnt know how to write code.

I assumed that people that got accepted in a master that has software development in the title have the basic knowledge or the background at least. Even though there is a separate master especially for that, to teach you software development.

My best CS teacher was the most passionate dev I've ever met. He is still teaching Software Engineering at 65, and he's reached that unreachable level of nerdiness, when you are more of a philosopher than just a coder.

Random anecdote: back in 2010, we both spent Christmas week playing and prototyping with Lego Mindstorms and Android, in preparation for my bachelor thesis project!

Does anyone else have this neverending drive for perfection in their software? One that has consumed every personal project, causing rewrite after rewrite so it would finally be perfect. Only to realize that perfection is impossible you are the guy who just wasted his entire weekend and has yet to finish a single project.

My uncle who thought me Computers and Networking ( I once worked with him on a project ) came by to my house today. He said that he created a software that automates his work on the boring stuff so when he has free time he works on his own company. My man!

Me: It's the weekend, time to step away from the computer for a couple of days, maybe get some fresh air

Brain: What about that bug in your personal software project?

Starting new game development project.

Coder:" ok guys, I think that this time we have to focus much more on sprints management and documentation"

Designer:"Ye, this time we should use better scrum software, like jira or youtrack"

Artist:"but Asana has the unicorns when you complete a task"

For the Project Management exam, my university requires us to install a program on our PERSONAL laptops that is meant to take over the control over the entire system during the exam, monitor any “suspicious activities”. The software is closed-source (it’s called Schoolyear Exams), does god-knows-what in the background, takes the control over the entire system and can be summoned through any Chromium web browser.

Don’t get me wrong, I get that you want to make sure nobody is cheating - but at this point, I’d rather write it with pen and paper. Or just provide us with computers for the time of exam.

I decided to whip out my old laptop instead, installed a Windows 10 on a separate SSD, and installed that software on it.

Also it’s very amusing that this software is also mandatory for the Linux exam… But the program can’t run on Linux (it’s Windows and Mac only and doesn’t even support M1 chips).

EDIT: typos

Another unrealistic deadline from our non-software developer PM.
He agreed to client upon delivery of a complete system consisting of 4 micro-services in Node and 4 front-end Angular application integrated with each micro-service accordingly.

Project Delivery date is December 31. I have told him It is impossible to deliver complete solution on December 31.
Now he wants me & my team to come to office even on weekends.
What an idiot !

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

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

Me: "Yea, sure"

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

Me: "😑 aaaaa the exact changes u wanted"

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

Me: Sigh....

My current situation:

Manager: How is Project A coming? Project A is top priority. I would like to see a PR today with fixes to the current tickets.

Me: Project A is priority! Sure!

*after 2hours*

Manager: How is project B coming along? I did not see any PR’s coming in?

Me: I am working on project A as it is priority.

*after 1 hour*

Manager: How is project C coming? There is one ticket pending. We need a fix for it today asap!

Me: Starts project C as project A would take more time. Starts Work on project C.

*after 1 hour*

Boss: How is project A coming? Where is the PR?

Me: As you said you need a fix for project C today, i started working on project C as it has only 1 ticket to be fixed.

Boss: I told you project A is priority, why are you working on project C?

Me: *doesn’t reply*

*after 1 hour*

Boss: There is a ticket pending in project D. Did you make a fix for it?

*This is my usual day at work.

*I am the only developer in my current company. It’s not a software development company.

*Note: I do complete all the work and create PR’s for all “pending” work at the end of the day for all projects and leave for home at around 10pm :)

What do you think? Lol

I like what I do for a living.

I build software, mostly from scratch or early stage products. Those are different industries, different companies, different technologies, frameworks and languages. Systems that impact economy in a different way.

When I develop software I am picking different parts of same project and try to understand how companies earn money and what are advantages of their software. What are required regulations and requirements to sell the stuff.
How the money flows from client and what they’re changing for. I especially try to understand stuff from business perspective.
When I pay my debts and luckily be still alive but unemployed and with minimum income from stocks / properties rental I will have plenty of time to duplicate many of those businesses.

I picked programming cause it’s touching all parts of economy basically without any skill requirements and certifications. It’s young impactful industry that is luckily not yet regulated. You just need laptop, like to solve puzzles and have plenty of free time and you can create everything. Never forget about it.

Cloud corporations try to make people think differently but it’s just that simple.

Project manager asked to "remove the debug breakpoints in Eclipse before checking in the Java file, so the client can't see them". Happened some years back. In an Indian software services co.

I freelanced for a company where I had to make an iOS app. The person who I was in contact with was a software engineer of that company. When i was asked to send them the final project code after publishing the app, the person was like email the project even after giving them the option of uploading to a private repo and sending link. It’s seemed like the software engineer didn’t know what GitHub was like how is that possible.

Pushed out a ridiculously complicated customization to our software with no errors, no user complaints and no needed modifications. Finally my 4 month long project is over.

12 years in the industry. For significant part of that time, I've juggled leadership roles, project management, customer facing role, testing, hardware debugging, marketing .......
Oh, I also code.
My designation is still a software engineer.

Whenever non-tech boss / client, dive into software engineering problem trying to micromanaging us, and ask how he could help to solve us hoping that the project could speed up in some way.

just stay the fuck away

One time in college we had an android project for one of our courses. Then this one member of my team didn't want to install Android studio because he didn't want to install any unnecessary software and libraries to his machine. We wanted to do his part editing directly in github.

*Releases software for State project comprising of a solution with 3 WinServices and 2 WCF Services*

*Literally 15 min after release*

Email from State: "Here is an updated wsdl schema that is going literally fuck up everything you have released, enjoy!"

Me: *starts convulsing*

I worked on a game jam last year, and for the first time I managed to finish a full software project that wasn't for a job or university. It was really fun to work on, and seeing my vision come to life, even if compromises had to be made, as well as applying all the programming and project management knowledge I'd picked up until then was an experience unlike anything I'd had before.

The community aspect was great too, everybody shared and discussed each other's games and were super friendly and encouraging.

Was working on a client's project. He had given clear specs. Work went delightful with less or no hacks. Then I get asked to add a extra feature which I had little thought about. Now I think it's a small hack and can be done. But here I am. One hack leading to another. I am too deep into ugly hacks. Maybe I should stop software development and join postal service to sort letters. I feel so incompetent.

When I started at my current Company and was put into my first Project, I discussed the Design Architecture with the lead Programmer in the Project.
Then he dropped the line:
"I don't understand why you were employed as Trainee instead as a Software Developer"

(The Reason was that I wasn't that familiar with Java aside from a little bit what I learned in University)

That gave me a big boost in Confidence ^^

I think my project manager has a diploma in software project mismanagement. :@

Freecad isn't open source software!

If it is impossible to get something compiled, it can't be open source.
When you can't compile it, all, that is left, is to use a binary.
If there is only a binary, it isn't open source.

Seriously: If you are participating in an open source project, please make sure, that compiling from source is a viable option for the generic gentoo user. Thank you.

Division of my 8 hour work day:

30% Answering Emails
20% Attending Meetings
40% Troubleshooting Bugs
30% Support Calls
10% Project Management
90% Software Development

Apart from the usuals like K&R, John McCarthy, Simon Peyton-Jones, Joe Armstrong, Bjarne Stroustroup, and so on, I'd like to mention one more, sort of different from the rest.

Ton Roosendaal.

He started Blender and oversaw its crowdfunded release as an open source project (look it up, it's pretty cool), provides excellent leadership at the Blender Foundation, is a crack programmer, very nice dude and down to earth. His leadership, vision, and handling of Blender's growth as FOSS software and artist-focused DCC tool is amazing. He might not be the brains behind Blender's technical advances all that much (now) but he's a great example of what one can do for software beyond just programming.

First course of "Software Engineering", it is full of project management ...
I'm so disappointed ...

ughh, studying about various software project management methodologies and lifecycles is so boring.

every different model looks similar, saying :
you got an idea?
- check weather its needed and if its practically / financially possible
- get investment and resources,
- design,develop, test, release
- repeat .
why name them waterfall or spiral or rad or agile or shit?

and we know how project go in reality: "fuck its 2 days to release and 5 features left? push to prod, make breaking features, leave the tests and release"

Some people get ego boost when they get positions like team lead or manager for software development team. In a nutshell you don't know shit about programming how the fuck you became tech lead? You fucked up the entire project that you managed and now shifting blame on someone else. Well fuck you!

A group of ten top software engineers is sent to a class for aspiring managers.

The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane).

One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands.

The teacher looked at the tenth and asked, "Why would you stay on?

"The tenth said, "if my team wrote the software, the plane would not get off the ground

A few months a couple of my colleagues, a business consultant and a developer, worked on a big project. The project capsized because the client is an A-hole and the developer was way over his head.

To save the project I was brought on board. The entire code base was a fucking mess of duplicated code. Shortly after, the developer called in sick with stress, simply because the whole thing was too much.

Fast forward to now; we just launched. The client is expressing concerns about the quality of the work because of the bumpy road (rightly so). I try to explain why my way of doing things is better, but to "paint the picture" I had to compare my approach to my predecessor. This results in the business consultant shooting me down, right in front of the client.

I fucking saved your job, your project, and about $1M in profits. I'm allowed to tell the story of why my incompetent coworker messed everything up.

I'm so done walking on egg shells because some just don't realize they are not cut out for software development.

Yesterday my boss forwarded a mail to me. A Senior Project Leader of a Software Company asked him if there is a library for filling out pdfs. Apparently, he can neither google nor ask their own developers... WTF?

University wants a final year major project which should give an output as a research paper published in some conference or journal. All seems great. Department rejected all web app related projects because it's too generic.. Still makes sense..
And then suddenly, department asks where are customer requirements, where is ER diagram, where are Selenium tests??????
And they still expect a research paper to be published....
Why do they don't understand the difference between software development and research works.. !!!!!!

Freshman out of the university started working for me as a php developer. Software Engineer from a major Australian university. First project, a WordPress plugin... Two weeks down the track I had to explain to him the concept of sessions and multiple visitors. WTF are they thought at universities these days?

Aaaaargh!! When your predecessor decides to incorporate (in an already technology too diverse project) another 5 new frameworks just to add an 'one pager app', that has a grid display of some data and almost no other functionality.. o.O FML!! Oh and also this page looks totally unlike other parts of the software.. yay!! :/

Why the fuck don't you provision and configure the cloud virtual machine yourself, "web lead" guy who uses fucking WINDOWS to develop software? Why don't you install Webmin and PHPMyAdmin in the VM yourself if you like GUIs so much? Why do I have to configure Apache and MySQL and fix all sorts of little issues for your project just so you can use some shitty CMS? I'm not your fucking IT support guy. Go learn how to use Unix, take responsibility for your shit, and let me spend my time actually developing software.

I'm praying for our newly hired Software Architect. Because He sets unrealistic timelines. He said that He will code, but yeah He just said it. Also, praying for our project. Coz it's really doomed!

Our Code everlasting
The all creating One
Coders Almighty

Through Our Holy Lines
Conceiving Algorithms
Konrad Zuse our Savior

I believe in Clean Code
I believe in Free Software
I believe in Open Source
Our Code is three in one
I believe in the bug-free project
That'll be compiled again
For I believe in the name of Alan Turing

I applied as a full-stack dev at a private company, they offered me the Project Manager role instead, I took the offer and after 1yr they gave me a choice to choose between staying as a Project Manager or switching to being a Software Engineer/System Analyst. I took the SoftEng position because project management isn’t my career choice for now.

Now people saying I not knowingly chose to be demoted. Is it a bad choice?

>uni project
>6 people in group
>3 devs (including me)
I am in charge of electronics and software to control it as well as the application that will use them.

2 other "devs" in charge of a simple website.
Literally, static pages, a login/registration, and a dump of data when users are logged in.

Took on writing the api for the data as well, since I didn't fully trust the other 2.

Finished api, soldered all electronics, 3d printed models.

Check on the website.

Ugly af, badly written html and css.
No function working yet.

Project is due next week Thursday.

Guess who's not having a weekend and gonna be pulling 2 all nighters

Friend has great idea for a software project built on top of OpenAI's API.

He wants it to be freemium, littered with ads.

He doesn't code. I think he's hinting at me to build it for him and I'll continue acting aloof.

I will not build software that's funded by ads.

Fuck ads. I hate ads.

So I have this "Software Engineering" course of this semester.

According to course curriculum we are supposed to taught "how to develop software for some real life problem".

Fast forward to this day. For FUCKING 8 WEEKS WE ARE GONNA JUST DO DOCUMENTATION(SRS, Problem description, features description etc) AND IMPLEMENT WHOLE PROJECT IN JUST ONE WEEK.

BURN IN HELL YOU FUCKING SHIT PROFESSOR....

How I learnt to Program!!!
Went for a University Project recruitment Interview in my 2nd year.
Senior: Which domain you wanna join?
Me: (as I was from software engineering Dept.) Coding domain.
Senior: Pointed to a table where 5-8 students were solving a coding question paper.
Me: (saw the questions and went blank. The questions were so tough, like check a number is even or odd.)I don't know anything in the paper.
Senior: why are you here then?
Me: (with full determination to join the project) Give me 2 weeks time, and I will learn all of it. (Didn't know learning all was never gonna possible, but that's how I started learning programming)
P.S. Yes, I got into the Project and was leading the Coding domain after an year.

First experience with Android: our professor of Software Engineering gave us a project about building an app for University indoor geolocation using BLE beacons.
Just found out that only a few PhD-level dudes did such a thing with much fewer good results.
Sounds like when your average-hedidnotrealizedwhataprogrammeris-friend asks you if you are able to hack Google Chrome.

// PSA //
Please everybody, go to your Project/Product Manager, Product Owner or whoever thinks it is a good idea to sacrify the usability and speed of the software/product for sake of faster updates, solutions that are easier/simpler to develop and implement, or new features not even the users itself could think of. Thanks.

I think software development would be immensely difficult if there were no internet and you would have to search everything in a physical library whilst left to your intellectual wit. That would require great skills.

I used to do it like that back in 1994, but of course now I don't have the time for that unless it would be on a hobby project.

Spent 1 month creating a piece of software for a school project and when I speak of it to someone on the IT business they tell me:
"Really? Once you start working you'll be using software that'll allow you to do something twice as hard in about 2 hours"

I just got a fucking job again after 2.5 months between jobs and the new place has been allowing (if not encouraging) the piracy of Windows Server in client environments... I thought this place had so much potential but I was wrong.

Going to start looking for another full time job or really buckledown and try to get my freelance project/business started.

BTW fuck microshaft for expensive licensing, but I’m not risking my certs and professional career for some idiots trying to pirate software.

Why the hell does it take twice as long to compile my software project under MSVC and Windows 10 compared to a GCC on a Linux *virtual machine* running inside the same Windows 10?!?

Rant: i have a software firm, recently got a new project, found a freelancer to work on the project.

He is a very good developer but he works on the project only when he wishes to work and I am left to answer the clients about project delays.

It's so frustrating that I can't get angry on him otherwise he will leave the project and on the other side I have to answer clients. I am stuck with all the tensions in the world.

I'm a .Net developer from Morocco, i'm currently working on an accounting software for this fucking company owned by an American boss. And i'm handling every single aspect of the project including the back-end (C#), Database (Sql Server), Reports (crystal reports, ABAP, VSTO), and design (UI, logos, animation...). For a salary of 300 USD/month, with no insurance, no transportation fees, and no fuck given about my health or my coworkers'. Not mentioning the shitty working hours and condition.
This is my first (job)

- Favourite pastime while waiting for your code to compile
- Most heroic/ingenuous bug fix
- Hardest to track down bug
- Worst legacy code you wrote and left behind leaving a job
- Weirdest project
- Last side project you actually finished
- Explain your job like I'm five/the way you do it for non-tech people
- That time your past self (almost) got you in trouble
- Software pet peeves
- Story about how you freaked someone out
- Feature that most certainly was a bug once
- Post something for your favourite previous weekly tag!

A software that would help me understand my dreams about my dream project

I am preparing for my exam in a software engineering course, where we discuss best practices for programming, testing methodologies and project management.
One of the topics is CMMI, and basically it states that organizations with mature development processes can produce exceptional software even if the teams involved are average.
Do you really think an efficient process can make up for lack of brilliance/ingenuity among the devs?

You know what's the worst in doing software?
being assigned that dreadful project, that's doomed and cursed just from the start. Nobody dared to try or touch it for 7 years, because it's destined to fail. You will never get the resources to do it properly, all the constrains are just against you. Even as the requirements bars are lowered and lowered you barely make it. You keep testing that shit with QA for like 8 months past schedule. Then before release some core changes need to be done. It passes QA, but you somehow now it's just a ticking time bomb. It will just crumble and fall somewhere out there, if somebody dares to use that shit for real.

And so it goes.

Bug reports coming in.

I'm writing a book that teaches everything I have learned in the past 20 years about writing small niche software and selling it.

Need some help from my fellow DevRanters.
Anyone who comments here with something constructive gets a free copy when it's done.

When I say:
"Why don't you just write your own software and sell it to end users"

What is the first thing that pops into your head?

Is it "I don't know how to advertise"
or
"that's a pipe dream"
or
"I tried starting my own business, but _______"
or
"I am doing that, i have this side project "
(how long have you spent on that side project?)

I need to know all your concerns questions fears, skepticism etc around the idea of writing your OWN software.

After 20 years I have like, so much knowledge, but it's sometimes hard to get it all out, UNLESS someone has a question or concern, then, out it comes.

So, I'm going to (hopefully) collect all the questions here ... and answer them, and it'll help me out a lot to extract this knowledge.

A lot of stuff I do without even thinking and realizing all the years it took to even know that.

What would you like to know the most?

You have the skills, you have the know how, you can probably see it in your head, so what's stopping you from making the leap?

Fucking german computer science classes

You get a few UML structograms and have to finish a half finished project. It's the most boring way to learn programming ever. Instead of giving us a task or a project to work on, it's literally translating UML to C#.

Is this what one is gonna do later as a software dev?

Software development lifecycle:
Step 1: Take shortcuts to get the project done in time.
Step 2: Wait for shit to hit the you know what
Step 3: Goto Step 1

While in Mec engineering university program I was in a robocup team (small robots playing soccer against an other team of robots using AI).

I designed the mechanical structure of the robots. After 2 years of development (while all those years our goal was to participate in the upcoming international tournament) we realized the software part of the project was mismanaged and really far behind. I couldn't accept that and learned how to code over night. Couldn't let the project I put so much time in die because of someone else.

With the help of others that came from other backgrounds than software, we made it the to tournament and the following two others after this one.

Now my job involves programming more than standard mec engineering. It also pushed me to do a masters in robotics in which I developed my coding skills even more.

For me it is not difficult to explain other people what I am doing as a programmer, but what company I am working for. We write software for the administration of cemeteries. People often look at me like I am joking. So I was wondering: What was your weirdest project/Job as a developer?

monday.com: our manager has been pushing for it for weeks. We barely got any time with the demo before it expired and the company took forever to get licenses.

Now that we're on it ... this thing sucks ass. It hijacks all the browser keyboard shortcuts. You can't use Ctrl+F or Ctrl+L .. you can't even right click.

This is the worst project management software I've ever seen. It's amazingly even worse that Jira. I wish we had just gone with Redmine. It's free and not garbage

We basically don't unit test at work. I write some tests for my code and honest to God people complain I'm wasting time saying a test bed and manual tests are good enough. We don't write test beds for about half of our production code and rely on integration tests for the rest. We only test release builds which have been symbol stripped, I get handed a crash report with no stack trace that I'm unable to reproduce and expected to stay late to fix it for some arbitrary internal deadline.

I've since moved to R&D where basically I'm left to do my own thing so it's better.

We don't project manage. Project leads take time estimates and double them so management might cut them some slack. This doesn't matter because management made up time estimates before the project started. Last project I was on had a timeline of 3 months and took a year.

We have released broken products. Not that any of the above really matters, our software products have made about 50k revenue in 2 years. There are 6 people on software. Fortunately hardware has made about 3 mill. That said our hardware customers are getting frustrated with us as we keep fucking up, shipping broken products and missing deadlines.

I've been working there about a year and a half and will be looking for a job at the end of the current project.

I joined devRant about when I was most pissed off with my job, my rant frequency has definitely gone down since I moved over to R&D.

Blender3D

Probably the most feature rich, frequently updated oss for computer graphics ever.

The project really captures the spirit of open source, most notably with it's open movie projects.

It does have a pretty steep learning curve, but taking the time to lean it is totally worth it. Not to mention comparable Autodesk software will run you thousands of $$$

// RANT

STUDENTS NEED MORE HANDS ON COURSES !

I'm doing a year abroad for the fourth year of my masters. I come from a school that really pushes projects, pitches and research forward while leaving in some theory.

Now that I'm at another uni in a different country I can't help but note how UNPREPARED students are for a professional setting ! And they are one year away from finishing their masters in Software Engineering...

Students should use version control tools, they should test their software, they should apply their knowledge to a concrete project ! A 3 hour course on software testing is only as good as its practical counterpart.

Is anyone else dealing with AD(H)D in university or while working as an software engineer. I’ve been diagnosed 3 years ago and I’m still trying to find a way to keep my focus. I start a new project every week without finishing it. Medication helps but not for 100%
Does anyone else experience the same or do you have any tips?

A software had been developed over a decade ago. With critical design problems, it grew slower and buggier over time.
As a simple change in any area could create new bugs in other parts, gradually the developers team decided not to change the software any more, instead for fixing bugs or adding features, every time a new software should be developed which monitors the main software, and tries to change its output from outside! For example, look into the outputs and inputs, and whenever there's this number in the output considering this sequence of inputs, change the output to this instead.
As all the patchwork is done from outside, auxiliary software are very huge. They have to have parts to save and monitor inputs and outputs and algorithms to communicate with the main software and its clients.
As this architecture becomes more and more complex, company negotiates with users to convince them to change their habits a bit. Like instead of receiving an email with latest notifications, download a csv every day from a url which gives them their notifications! Because it is then easier for developers to build.
As the project grows, company hires more and more developers to work on this gigantic project. Suddenly, some day, there comes a young talented developer who realizes if the company develops the software from scratch, it could become 100 times smaller as there will be no patchwork, no monitoring of the outputs and inputs and no reverse engineering to figure out why the system behaves like this to change its behavior and finally, no arrangement with users to download weird csv files as there will be a fresh new code base using latest design patterns and a modern UI.
Managers but, are unaware of technical jargon and have no time to listen to a curious kid! They look into the list of payrolls and say, replacing something we spent millions of man hours to build, is IMPOSSIBLE! Get back to your work or find another job!
Most people decide to remain silence and therefore the madness continues with no resistance. That's why when you buy a ticket from a public transport system you see long delays and various unexpected behavior. That's why when you are waiting to receive an SMS from your bank you might end up requesting a letter by post instead!
Yet there are some rebel developers who stand and fight! They finally get expelled from the famous powerful system down to the streets. They are free to open their startups and develop their dream system. They do. But government (as the only client most of the time), would look into the budget spending and says: How can we replace an annually billion dollar project without a toy built by a bunch of kids? And the madness continues.... Boeings crash, space programs stagnate and banks take forever to process risks and react. This is our world.

What can I do when my boss tells me to guide the “Senior Software Engineer” while I am just a “Software Engineer”?

Also, the SSE just asked me to help him/her with his/her project coz he/she forgot the skill that he/she was hired for.

I opened this up to my boss, he just told me to guide and not spoonfeed her.

So, questions:
I really find it unfair that we have different job titles, how can I tell my boss that the SSE doesn’t really have the skills to proceed with the project?

Second, do I also need to define and establish the criteria for Lead, SSE and SE within the company? (My boss scheduled a meeting for this exclusively)

So I had a piece of software crash on me earlier today...

I think "No problem, this was built internally and I saw the source code somewhere around here. 👍"

Locate source code...6 folders ("Project--v1.0--stable-2012", "Project 1.0", "Project 2.0", and a few others like it). Took me 20 minutes just to figure out which folder was used to build the project/exe. Turns out, none of the above. 👎

Had these people never heard of source control before?! 😣

Agile/Scrum is the worst project management style in software development.

Rather than focusing on delivering a feature or changes on the project, everyday there is always a meeting that you need to attend to, other than the daily huddle. And those meetings are none of your concern or why they needed you there

And my Product Owner and Scrum Master does not know even though how software development cycle works. When you discuss technical details or constraint to them, they either look confused or don’t know what to say and just say “If you need anything, always communicate or approach me” even you already told them the issue.

Or maybe we are doing it wrong. But it is been 5 years when they implement this Agile/Scrum and we are still bad at it.

Just ranting

Software project in technical college:
Expectation: Ok guys, we have about one month to finish our project. We have a lot of stuff to do, so let's start right away.
Reality: So we have one more day until the project needs be submitted. Hmmm... I guess we're going to start by tomorrow.

True reason of unemployment-

Firstly companies hire people to make their software automate and then after successful completion of the project, the company terminates most of the employees.

Hi there, First “rant” here, although it’s more of a question.

I have been working on a side project for some time and it has come to the point where I feel it might be prudent to protect my work with a patent or something similar.

The project in question is a multiplayer browser based game. The code is currently open source, but that can always change.

Given this is software people use rather than a service that developers might build off of, is copyright more appropriate than creative commons?

Based in the US if you can't tell and I'm above the age of majority luckily.

Thanks for any advice!

My most successful project was in the fisrt year of University in 2016. We had to build a robot from scratch with all the mechanic, electronical and software components, which could solve a given problem, in our case defusing a bomb, in collaboration with an other team. After a lot of frustration, late night debugging and many beers, our team managed to win the competition against 8 other teams.

Just finished writing a Git Mini Handbook for beginners. Plan on releasing it on Amazon this week and then begin finalizing the Mega handbook.

I just find it better writing my knowledge into books other than sodding around a software project.

Probably joining my first real project. Truly no amount of university education can prepare you for the sheer scale and complexity of an enterprise software project. 100+ git repos, 5 different services running just to run the project locally, with tunnels open to 2 different DBs. It was daunting to touch anything.

Why is it that every python project I come across seems to not even want you to use it.
The deployment always sucks, you get some random ass errors because some parts are in python 2 instead of 3 I guess. If there's a C library involved it most definitely won't work. What the fuck is conda and why do I need it to install software?
Where is the documentation to build a release yourself if the public ones don't work?

We use a open-source business management software (incl. crm, e-commerce, billing, accounting, warehouse, ...) that is highly customizable.

Previously we had "Company A" that customized it for my company. It was very expensive so they hired something to do the same but cheaper & inhouse. The codebase that "Company A" has written was terrible (confirmed by CTO & the new colleague").

Then the CFO wanted functionality A. Colleague said that this will take 2 weeks to implement. One week later, it was no longer needed & functionality B was now mandatory. Rinse & Repeat.

The CFO: "Why is nothing ever gonna get finished" or "why is the quality so bad?"

So they hired another person for the same position. This person has more experience so it costs them a lot more... And suddenly, everything works well

They contacted a few months later a consultant that analyzed the company. The consultant asked (for good reason) why such a small company has 2 people maintaining the in-house BM software. And suddenly, they wanted to get rid of the worst person. <enter my previous rant>

He is thrown out. Now the head of Operations wants to remove that software because it was not "sexy" enough (her words). So they introduced a glorified spreadsheet with less functionality. That new colleague was offered to take the lead on that project... And thus he fled to another company.

That project failed and now everyone is fired... And they hired back "Company A" to maintain that BM project.

When I was younger I had a decision to go into hardware or software. I chose software and have loved it.

Recentily I just spent 5 hours trying install a Linux distro on an old server. I made no progress.

I made the right decision. Hardware freaking sucks! You spend hours working on outdated pieces of crap and find that to fix your problem you need to sell you kidney to finance your project. Not to mention you have to wait for literally everything! It's like gradel builds everywhere! Want to install a new distro on your USB? Bam, 5min gone. Want to boot into bios and change one setting? BAM! more time wasted...

A note to the sysadmins out there: thank you. I love you. I am so happy you do this kind of work so I don't have to.

Should i be posting on devRant to hire a fellow devRanter for a project in my company? (temporarily but may become constant if we click well)

More info:
Looking to hire a mostly frontend react dev.

The project is about graph visualisation and traversal.

Our stack is python (flask, appbuilder, SQLalchemy), react, react d3-graph, jest.

Must know how to use git and pull-requests.

(The software is based on Apache superset)

The code is a bit of a mess. But let's be honest, which big project isn't?

Would you rather make every software you want but give up coding, or keep coding but always for somebody else's project?

My colleagues work on our project files with unstable software for hours on end without saving their progress. Honestly, the balls on them. One of them just closed their Laptops to put it in energy saving mode without saving 2h of progress. Why are you doing this to me?

Actual question: Tell me which project management software you use and what you hate about it. What do you like about it, if anything?

Demoing our product at the customer's site by remoting into one of our internal environments. Their internet is slow so product looks slow.

Project manager after the demo: hey, next time, think of yourself as the tech lead, not just the software lead. Next time hop into the command prompt and do whatever you guys do, check the bandwidth or something.

Me biting my tongue: so I can tell you the customer's internet is too slow?

I was brought into my new position as part of an transformation of waterfall to agile methodology.

We are now running 4 while projects and need to restart the remaining 29 projects using agile principles. The business management type people love agile, but somehow the people inside the current waterfall practices doesn't.

They are afraid their silo work will either expand or not exist thus making it hard to transform the company. Also the company have been subjected to the dead sea effect.

Therfore, the project that is currently in the space of transformation is making my blood boil because people just ain't passionate enough about software.

Either you craft software, or, well you sit and suckle other's money. People suckling should please grow up and start venturing beyond there cozy 9 to 5 and transform to be a professional software doer rather than a BA, DEV, IT GUY.

YOU BASTARDS GET A SHITLOAD OF MONEY AND DON'T DESERVE IT FOR THE EFFORT YOU BRING.

It is your software, own it, be proud of it. Read up to make it better. And as always, the people debugging your code can be a violent psychopath

Manager: make some AI for this project it is simple.
Me: what are we talking about?
Manager: I want to get a report about any topic in our ERP just by talking to the software.
Me: 😓

I've always thought that in order to become a project manager it was necessary a period as programmer (as it was a sort of promotion).
But according to what I read here it seems like a lot of pm have no idea how to/how long it takes to develop software... Am I wrong or what?

Trying to understand why do I have a course on Software Engineering which consists 80% of lectures on what Agile and Scrum mean.

Why can't we get to implement a project and work on agile as we go? 😐😣

Large majority of rants is about incompetent project managers.
No matter where you live the problem stays the same. Most of them have no clue how software is being made and how dev/qa work looks like.
I frankly do not understand this phenomena. I have friends in automotive/constructions industry and theirs managers are engineers too in that field. Why it can't be the same in software development?

Developing the front end and THEN developing the back end is a horrible idea, right guys? I've been placed on my first big project with my employer and this is the way the client is deciding to do it (my employer is not making the backend). I just need to know that I'm not crazy and that this is usually never the way people go about software development. Right guys? Please send help.

Marketing department sometimes are so Fucking annoying in the context of they " just found out certain technology" and try to enforce us to implement.

For example recently this guys just found out firebase(Firestore thingy ) and keep asking us to implement into the app (E wallet app) which our software architect refuse to use firebase( I agree with him) because in the long run , the project will definitely get surprising prices in the invoice.

Also, our DBA had started to implement Apache Cassandra .....

So dear marketing department, why don't you guys shut up and let us do our job and let our software architect do his job? Fuck off!

Our help desk person set up our software in a virtual machine on some cloud provider and you know how they give you a drive labeled temporary with a text file in warning you how the files will get deleted? Well for some reason they put the database files on that drive.

Luckily the server was for a small internal project and restarted a few days in so the users didn't loose too much work.

Sr Engineer says "I'm not sure how this project is deployed".

You're a software engineer. You solve problems all day long. This particular engineer has worked here for several years and is well aware of the fact that we use Gitlab to run deploys.. If you want to know how it's deployed... look at the pipeline definition...

I don't understand how people, especially those with several years experience with our stack, can't solve basic problems on their own.

Anyone in here have experience with UML in the real entreprise world?

As a student I've learned a lot about documentation and software architectural design, I've worked 3 different places and worked with customers that were developers and all of them seemed to not really do architecture and documentation that well. Personally I find having an overview/guideline for bigger project really helpful

how come you don't see better software documentation and UML out there?

Maybe I just haven't found the right place yet

What's your workspace setup?

Curious because it took awhile and a lot of experimenting/thinking to get mine setup the way it is, but now I can't even think properly unless I have things setup that way after booting up in the morning.

Here goes:

Workspace 1: General stuff, personal email. social media, random research for non work related things, etc

Workspace 2: My main project local development, includes terminals, database, browser research for bugs, debugging software, error logs, etc.

Workspace 3: My main project, production workspace, consoles, browser, etc related to production server, you get the idea

Workspace 4: local dev on my side project

I found it crucial to setup workspace 2 and 3, it has helped me avoid countless stupid errors, like, for example, accidentally working on production terminal and wanting to rip my hair out wondering why the fuck _____ isn't working, then realizing, oh shit, i'm on production, not local. Huge brainspace bandwidth saver when I setup like this.

How about you?

Uhmm. How do you guys write your resume? I mean, there seems to be a lot of ways and taboos on writing one, some say it shouldn't be more than 2 pages. But in some domain, the longer the better. As a software developer how should it look? Some are project-oriented others opt for work-company-experience-oriented.

One of my really good friends met me today and she's become a project manager in a big firm and has been asked to manage a project and get it delivered.
A bit of history first. She and I graduated from the same college and got into different firms as software developers. We and our dev friends used to bitch about how PMs don't know anything and don't give a fuck about the quality of project. She moved on to pursue MBA. Fast forward 4 years.. it's today and we are in my apartment having dinner. She's going on and on about how bad the project is, how mess of the project this has become and how she doesn't care at all about the project and doesn't know anything but wants devs to finish the job no matter what. She knows the deadlines are aggressive but has directions to shit all over the devs and get the work done. So she's just doing that.. giving them an earful and asking for daily updates and questioning them about delays without even knowing what the project is about.

When I try to tell her that it's not the right thing to be doing, she's proudly admitting that's she's only going to manage the project for a while and doesn't really care what happens to it.

I have lost some respect for her now.. :(

As a developer I never understood the intended benefit of standups. Issues + a scrum/kanban board like trello or GitHub project + a chat for quick questions or to schedule an ad-hoc pair programming session should be enough to make everyone know everything they need to know about the project status at any time.

Obliging developers to talk in a group session to reiterate in a more verbose way what they already wrote down when working on it, will make a lot of people uncomfortable. Talking too much or not complying to the talking rules is an expected side effect besides anxiety and reduced productivity.

If you want a talk show, hire talk masters.

If you want software development, hire software developers.

Don't confuse one with the other!

Finish my only pet project;
Learn a new compiled language;
Get better at functional programming;
Read more books about networks and software engineering;

My Project Lead got me to work overtime, I was doing 150% of what I was supposed to do.
After 4 months of tremendous working and smart planning, I planted a small bug in the software we build, and used that to exploit the Software yesterday morning, and today by 3 PM (Our Usual. Lunch Time), He was fired.
Finally, that donkey is fired and now he must rotten in hell, yeah, he got that stamp on his resume for being fired.

Now I am feeling guilty that I have almost ruined his career (30%), but I am happy, that rascal got what he deserved (70%). Yay!

Opinion | What kind software project could be submitted to college as a supplement ... Like a scripting language build from scratch?

When I was in school days I didnt like computers that much. I knew how to use them but thought classes were lame.

It was a couple of years ago, in the last year of my first computers-related career (here there's no computer science like in USA). It was in the initial stages of my graduation project and our teacher took a look at our database design, fixed it all. And explained:

"The better you designed your database, the easier it'll be to code the project" Explained to us the importance of database normalization and all that.

I really understood it all and discovered finally what was the thing I was studying and how to do software.

From that day, in my early 20s, I've been loving software and knew this is my thing.

Same feeling 6 years later.

Is it just me or do software developers get the shit end of the stick in absolutely every project?

It's all based on the dev's experience. A beginner always faces trouble estimating a feature/project, but seniors don't, cuz they have the experience to get over the hurdles in software development.

My family had a very good understanding of what I'm doing.

My dad is working at a big software company as project manager (he himself did code years ago, but it's actually a physicist).

My mum is a language teacher, but has taught herself web design while she wasn't working in her job (taking care of us kids) and was working as self employed web designer from home for some years.

My youngest brother is studying business informatics.

My other brother is not studying anything technical, but very open minded towards these topics and has good knowledge about it.

My grandparents believe what I told them: "I (read as: software developers) create everything that happens in your computer after you've turned it on."

Sometimes completing a software project is like experiencing Zeno's paradox.

The typical university project as a group:

- Discuss/Make somebody create the items in Jira: 2 days
- Implementation: 2 hours
- Tests: What are tests? Do I write them in my main method?
- Review/Someone sees the code: 9 hours
- Staging/Production: No one is ever going to use the "software"

How is it called when I rant about something my colleagues experienced and I just supported his debug session? Third party rant? Anyway, here's the thing.

Other team built some project specific code right in the heart of their software, which in itself would be worth a rant. But as you might guess, it's getting rantier.

For a new project the same code is used, but needed some tweaks. Now guess what happened:
1) Someone took the code, refactored it, made project specific stuff configurable, everything works fine now
2) Someone changed the code completely for the new project, everything seems to work fine for 5 months, then the old project needed a new release 💣

You should have a giant snapshot of your software at the beginning of your website.
Even if you're an open source project. Some linux DE don't do this!
We're not in 1995.

I've been working on a side project for a while(many months) and I'm at my 3rd refactoring and concluded that the greater service I want to achieve the more complex the project become, nothing exceptional, except I feel like doing the effort of an entire team of software developers.

Someone else has/d such a feeling/experience? If yes, I would like to hear your thoughs/story(just curious ;)

Ps: soon I'll reveal some screenshots here :3

I have been working on a project for few weeks now. I've found collaborators willing to test the software until "official release" when they'll sub as my first customers. I am a couple of days away from releasing the early version and my laptop desides it won't turn the fuck on.

FML.

So, we're apparently going to build a sort of social media(with competitions) for our software engineering project. I thought of a productivity app that would follow the GTD methodology (with my own additions), but my team mates thought my idea wasn't big enough for a team of 10. One claimed that he would do it all by himself in a week/month(Don't know what he said). Oh, well. Anyways, I'm going to build that software as a side project with a friend or two. I hope that goes well..

PS. We need a team name. Any suggestions?
I thought of Team Sudo lol.. No one liked it..

In software architecture definitely my own architecture in a programming project for uni
In building architecture the recently "modernised" Park Inn hotel in Bratislava 😅

My best experience this year was to be the project manager of a software project and my worst experience was to work alone on this project.

Successfully finalizing a software project & achieving set goals within a set time.

Applying for an entry level software job and having the "let's do a hackathon" project. It's super fun cos I know the effort I put in doesn't actually matter since you'll just choose someone more experienced. But I still have to go ahead and put in max effort or you'll have a reason to call me lazy :(

Absolutely hate it when my software engineering module project mate merge their own commits into the team repo without anyone else reviewing.

That’s it for you, branch protection ON. One more time and you’re losing push access

My work had Project Management software before to track tasks and issues, but the new boss wanted to switch to some new support tool. A bit annoying, but no problem.

After decommissioning the old (free) PM software, he decided to put off the new software implementation. Instead, he created a shared g suite inbox that we have to log in to and check for issues. No routing, no priorities, no notes section, no progress tracking, no tasks.

Now I have to give progress updates several times a day on my tasks because there is literally nowhere for me to report my progress. I have no idea what my priorities are since we have literally nowhere that specifies priorities. This is a PM and support nightmare, and as a former SCRUM master I'm about to lose it!

software development is a great thing... when you're the only one working on the project. otherwise everyone writes their part of the code, and you don't feel "in full control" of the codes and software. i hate that feeling.

A place where you can evolve your skills, competitive and that you're respected.

And NO FREAKING CLUELESS PROJECT MANAGERS that do not understand how software is "born" and expect you to catch insane deadlines...