Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "scope creep"
-
"Here's the sprint, it's well defined. fullstackchris, can you do this in two weeks?"
"Hmmm... nice work, looks well defined. It'll be tough, but sure, I can do it two weeks!"
Two days before sprint ends:
"Can we quickly duplicate n number of features from apps with literal armies of devs like whatsapp, airbnb, and Instagram?!?!?! We NEED these features to be polished and work perfectly!"
Scope creep will be my ONLY feedback in this retro.2 -
Manager keeps fucking changing the requirements on me.
All day yesterday I couldn't even do any programming because I was so fucking tired. It wasn't until 2 pm and physically removing myself from my office that I finally could think about the problem I was having and move on. I was seriously really annoyed with myself and annoyed that scope creep keeps fucking up my shit.1 -
Scope creep and hidden requirements. Project seemed to get bigger every week. 4 months salary for 7~9 months of actual work.
-
Anyone ever stay on a set of projects they knew were going to fail? I got pulled off of 3 major projects to help another team that was failing at their very high visibility project. I got that back on track, but then they needed to keep me on for stabilization work and to onboard some folks. Then they still kept me on and my projects all suffered. I was very vocal to management about my concerns. Finally, management recognized that my projects weren’t getting done so now I’m back on them. The thing is, now it’s probably too late and I’m pretty sure I’m going to fail to meet deadlines on all three (plus there’s scope creep of course). I want to just walk away from this hell hole, but I’ve made some promises to folks that helped me get the job that I wouldn’t be a job hopper (been here 4 years, and each year is worse than the last). I think I’m just going to do the best I can and see what happens - and try not to have a heart attack in the process.1
-
How can a novel emerging challenger software (written in Rust) take me 4 hours to install (still ongoing)?
Today I have decided to give Pijul a go. Pijul describes itself as a theory-sound alternative to Git, which I have wanted to get away from for a while now, due to various reasons -- many of which I saw Pijul advertise to have solved on design level.
So I set away a day to learn Pijul, today. Well, 4 hours after I sat down -- after a number of hilariously wonky failures of "Rust ecosystem" to do the right thing as I had to install Rust with some shell one-liners those insane wizards recommend for installation process (all in the name of "stability but not stagnation") -- Pijul has now been installing with the blasted `cargo` for an hour now (that's after 3 hours of getting to the point where `cargo install pijul` stopped exploding in my face) -- telling me I only have 40 crates more to install. Are they throttling me, perhaps? I don't care -- I should have been installing Pijul from a repository in accordance with my Linux distribution, or -- at worst -- download a BLOODY COMPILED PROGRAM IMAGE.
What is it with the hipster developers today? Everything they get of tools, they subsume and churn out intricate complexities the likes of which we hadn't seen yesterday. Tell me fellow developers who think installation of your software has to require three and a half novel "installation solutions" to which I can't be arsed to be made privy -- do you think your life today is easier than, I don't know -- wrangling with a Makefile and a C compiler (which today thankfully can do rather good job of standards compliance)?
I mean I wouldn't mind Pijul being written in Rust -- but it turns out Rust's advertised elegancy in practice is wrapped in so much "giftwrap" I feel like what desire I had to learn Rust myself, I'll stear well clear.
Here's an advice for developers in general -- an advice continiously ignored for decades -- stop blowing your original scope of delivery in auxilary packages you think you need to reinvent just because you can or because your mom is out of town! For programming languages like Rust this most certainly entails NOT writing your own package manager, with its own package delivery mechanism that has its own configuration file format and virtual machine to configure dependency resolution or what have you!
You wanted to write a programming language that has novel features you think we need? Fine -- write one and stop there. Watch it grow, and watch people who are busy working on other parts (scopes) of software to integrate your offer.
What a shitshow. Stop smuggling alternative package managers, installers, and discombulators with your actual product -- I only want the latter, I don't want the rest of your damn piping, walls, roof and a cathedral on top of it!
Don't be that guy starting with a pin, and ending up with a fucking diorama miniature of a pig farm in Netherlands. Jesus.8