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
-
Client: This new feature is not working on Internet Explorer.
Me: Do you have enough oxygen in the cave you are living in?7 -
EDIT: since this announcement, collabs have been made free to post for all devRant members!
Introducing two big new devRant features!
First, the one @trogus and I are most excited about - Collabs!
Collabs are an easy way to start projects or work on existing projects with the awesome members of the devRant community. You can post a collab listing for the awesome open source project you started that could use some more contributors, that fun idea you have for a brand new project, or really anything you want to gather some fellow devs for. We think it will be a lot of fun.
Collabs also is a devRant first - it's our first paid feature. For each 2 week collab posting, we're charging $14.99. But we wanted to make sure to thank devRant users who have been with us for a while and anyone who contributes often, so anyone with 2,000 points or higher (now or in the future) gets one free collab listing!
The main reason we see collabs as a great first paid feature is because requiring payment or 2,000 points serves to be a slight barrier in posting a collab. We think for collaborations to be successful it's important to have some way to keep out listings where the poster has no intent of following through and we hope this is a good start to doing that.
NOTE: if the collab you are looking to create is devRant-centric (ex. a devRant Chrome extension), we will give you a free credit especially for that so you don't have to pay or use your earned free one. Just contact us (info@devrant.io) if your project falls into that category.
In addition, after tons of demand from the community, you can now change your username and email address! One important note is that you only get to change your username one time every 6 months, so use it cautiously :) You can access this feature in the "more" tab, then settings, then "Edit username or email."
If you have any questions or feedback about any of this, just let us know! We hope everyone enjoys :)
52 -
Spends hours implementing a really cool new feature.
Feature gets deployed.
Client flags the new feature as a bug :'(
FML10 -
1 week ago my boss forced me to ship a new feature on friday afternoon. The feature broke our application for about 2 hours. After this I bought him this cup.
9 -
- Free app:
"5 stars - OMG this app is awesome!!!"
- Add new feature with In-app purchase:
"1 star - App sucks balls. Why we must pay? Make free and I rate 5 stars"
I call them The Rating Terrorists.8 -
Learning a new technology:
1. Denial
2. Anger
3. Bargaining
4. Depression
5. Acceptance
6. Ohh, cool feature~2 -
You might know by now that India demonetized old higher value notes and brought in new one. The new ones easily tear off easily and generally feel cheaper and less reliable than pervious ones.
One interesting thing people discovered is that rubbing it with cloth makes the ink transfer to the cloth. Sign of crap printing. Here's government response:
The new currency notes have a security feature called 'intaglio printing'. A genuine currency note can be tested by rubbing it with a cloth; this creates a turbo-electric effect, transferring the ink colour onto the cloth
TL;DR: its not a bug, it's a feature7 -
Apple at WWDC 2018.
"Now we added this all new feature!"
"Gallery view on finder"
Sheeps: YAAAAAAAAY
Wait! Whaaaaat! This shit was back there in Windows XP. People, this is Filmstrip view!!! 😂😂😂
4 -
So Facebook announced a New Feature which lets you upload nudes which get hashed and on a Blacklist so they can't be uploaded to facebook. And in Order to prevent abuse, a human Reviews the pictures. Genius idea19
-
When a system-breaking bug ends up fixing a different bug and actually produces a new feature we didnt intend but actually love
5 -
Business: How long will it take to add that feature to the legacy system?
Programmer: When will the new system be implemented?
Business: 6 months
Programmer: The new feature will take 7 months3 -
That moment your javascript has a bug but its a cool one so you decide to leave it and call it a "new feature"
2 -
As most of you already know, the mentioned users in a rant don't receive a notification so you have to mention them again in a comment.
After a suggestion of @Cozyplanes I decided to implement a feature that make this automatic.
Just check the box and forget about it.
It will be available soon in the next update of devRant unofficial UWP!
7 -
Our product owner's equivalent of "It's not a bug, it's a feature" seems to be "It's not a new requirement, it's a clarification."
:-/2 -
how to make a feature request
1. dump Db table with 153 column to Excel
2. print!
3. circle column 47 on page 3, scribble feature description
4. scan! remember to use proprietary file format no one has
5. new e-mail, add "VERY URGENT!!!" to subject line
6. write "will call, discuss details monday"
6.a. attach proprietary-scanned-excel-dump-feature-description (optional)
7. postscript: deadline wednesday!!
8. wait for tuesday
9. send!
...3 -
Boss: Have you finished that feature?
Me: Almost there, i'm refactoring some classes...
Boss: What? Refactor? But thisnis a new feature, it does not need refactor! We don't have time for this!
Me: 😵🔫
This is what happen when you care about code quality.5 -
How to politely tell your client that their request for the new 'little' feature is unrealistic and fucking absurd?14
-
Tried browsing reddit on my new feature phone today, was not disappointed.
It has a surprisingly feature rich browser
http://html5test.com/s/...
10 -
Quote by my non-techie co-founder: when a developer says a new feature takes X amount of time, you always have to multiply X by PI to get the actual duration 🤓8
-
Like the new feature on Google Play Store where the changelog can be directly seen in a dropdown on the updates page.
3 -
Nice new scrollbars feature Spotify, but
1. This song isn't 05:34 minutes long
2. That position hardly seems like 05:01/05:34
3. The point is stuck at 05:01 while the song is playing
19 -
Get assigned ticket.
Finish the most of the feature. Finish most of the specs.
Push.
Second dev wants to own accounting half of the ticket.
Rip out half my changes, rewrite specs.
Push.
Code review asks for minor changes.
Finish them.
Push.
Product creep creeps the scope.
Finish the feature again.
Push.
Product creep creep-creeps the scope.
Finish the feature again.
Push.
New release happens.
Merge in master; fix conflicts. Run specs; random unrelated specs fail, some fail intermittently. Rabbit holes of complicated, unexplored, obviously-flawed code.
Fuck that. Push.7 -
When you don't have new feature to add to the app but need to keep updates.
"General bug fixes and performance improvements."3 -
I HATE when a request for a change or a new feature comes like a bug feedback, as if it's your fault
"I clicked this, but this behavior that we didn't agree on didn't happen!! Fix it!"
😡4 -
That moment when you listen to your boss' lies to a client when presenting a new product/feature.
I am like: damn, this guy is a talented actor!3 -
Bugfix I am most proud of?
The ones where I dont just fix a bug, but refactor an old (possibly shitty) feature thanks to new knowledge, making the next person's job easier in the process :)3 -
6 months ago I had to implement a new feature and realized that a related uploading feature was broken if you choose a specific service to upload to.
I was wondering why nobody had reported this, so I took a look at the usage of said feature and it seems literally no client ever used it since it was released almost 2 years ago.
Only the product owner used it in the beginning... only for testing it...
2 weeks well spend.5 -
manager: Just create that new feature real quick... We'll refactor and make it a good feature in a couple months...
me: *see image*
2 -
"Shouldn't be a problem. I can get <insert new feature here> implemented by <insert wildly optimistic time>. "
What is wrong with me?! Why do I keep doing this!?2 -
It took me around 10 hours, but I finally got a new feature onto my discord-bot. Best thing about it is, that I can basically transfer it onto every meme format
4 -
Co-worker: "I made the UI for feature X you asked me for"
Me: "Oh great tha... Why is it on the same screen as feature Y? Those features are unrelated?"
Co-worker: "Yea it was too much effort to create a new screen."
Me: "...?!?"1 -
I always end up being too busy working on a new features that I forget git commiting every feature so I always end up comitting something like "lots of new stuff idk lol"7
-
Manager: "We're gonna have to work over the weekend to add this shiny new feature!"
Me: "Peanuts and Incentives included?"
Manager: "No, but you get job satisfaction!"
Me: 😒4 -
Finally program running perfectly 👍
But wait.... Lets add another feature...
New feature needs updated matplotlib...
Update matplotlib😒
Lost support with numpy😫🤔
Updated numpy 😫
Run program again...
Core dumped (segmentation fault)😶😶
Time to leave this planet10 -
Holy fuck this new GitHub feature is amazing!!!
It's called GitHub Actions and you can easy automate your work flow using a simple graphical editor!
I need to test this out right fucking now!4 -
Even though I haven't had such an experience yet, I can assume that this is what every dev sees when he lets the client play with a new feature
-
A client, who don't know about programming. But only wants to finish the project ASAP
Me - It's complicated to implements this new feature.
Client - It's easy!3 -
Fuck all managers who expects us to deliver a completely new feature before the holidays when in reality it would take thrice the time left until everyone is on vacation. Fuck them all with a cactus.5
-
PayPal.
Found a nice method that does what you want? DEPRECATED.
Finally got that adaptive payment workflow all figured out? BREAKING CHANGES.
Want to use that new feature with your langs library? UNSUPPORTED.
Braintree isn't much better.7 -
Friday 4:59pm
PM: hey, we need to add this new feature to the project.
Me: no problem, I'll take a look on Monday.
Monday 8:01am
PM: how's that new task coming along?
Me: 😩4 -
The last person I used skype with loves the new Signal video calling feature! I can finally say goodbye to Skype now 😍 (if you'd ever read this, thank you!)15
-
Today it was decided that we would hide a bug by making a new feature that only hides the bug
I don't like it, but it needs to be done for actual reasons5 -
New feature on the Cuntbook. Want to write a post to a page? Poof, and it's gone! BILLION DOLLAR FUCKING FEATURE!!! BILLION DOLLAR FUCKING COMPANY!!!
CERTIFIED MOTHERFUCKERS!!!!
Oh and just to load our pages it takes 20 seconds. Because fuck you, this is Web 2.0. FUCK!!!
9 -
*Presents finished product to client
Client: We won't pay until you add this new feature that was never in the original specs.
*One week later after adding new feature
Client: Uhh, actually there's something else we want, do that then you get paid.
😬😬😬😬😬😬😬9 -
> ticket comes, new feature is requested
> create the new feature from scratch. Code is neatly splitted in files and methods, each with clear responsibilities
> every method is documented, there are clear service layers for the business logic, which resulted in controller having 10 lines of code, give or take
> commit the whole code, everything works
> check the develop branch today, team leader littered business logic in the controllers because "the codebase is a mess anyway"
15 -
Spent a couple hours writing a new feature yesterday, and finished it only to discover that somebody lazily wrote the global method that my feature was utilizing. Emailed them and told them that I completed the feature and asked them to fix the bad method. Figured that I wouldn't commit my code changes until he fixed his method. He proceeds to fix the method, and then completely redoes the feature I ALREADY TOLD HIM THAT I FINISHED. He removed me from the backlog story that I was assigned to and did the feature the exact same way I did. Motherfucker I already told you that it was done, you just needed to fix your lazy shitty global method. You did twice the work and wasted my time. If you wanted credit for your work, that's fine -- you could've created a new story to fix your method. Now I've wasted hours of my time writing a feature and then reverting the changes because you couldn't follow directions
-
How’s this for a horror story? Adding a new feature to a 6,000 line and 100% undocumented stored procedure in a 20+ year old Oracle database.2
-
to all those smart-asses who kept praising Windows for the new "active hours" feature as opposed to forced restart when updates are downloaded.
I work more than 14 hours a day, WILLINGLY!
21 -
When you spend countless hours working on a new feature and realize that there was this google API which could do the exact same thing the whole time..... -.-6
-
New ticket: Add Feature
description: (will be updated)
Last famous words before the creator went on vacation until app release1 -
Producer: "We need this new feature by next Wednesday's release. Enter estimates into the task, ok?"
Me: ಠ_ಠ
hint for the estimate: by next Wednesday1 -
Subject of message: "Important: New feature for all 000webhost users." Thanks, 000webhost, an hour of downtime a day was exactly the feature I wanted to be implemented. P.S. if you have OCD, don't look at how many unread messages I have
10 -
See another of this git commit message :
"Fixed bugs and added new feature"
Fixed what bug?! Added new feature what?!4 -
Time to add a new feature in an Android app:-
Java code with basic layout to implement the feature - 1 hour
Polishing the layout - 30 mins
Time to fucking make the scroll view wrap around the text and not overflow in the dialog so that the buttons below are visible - 6-10 hours!!!12 -
Me asking my boss some deadline information through email: "Should this feature be added ASAP or delayed until the new year"
Him: "Yes"
Which one damnit?!6 -
I think this is both a blessing and a curse for me.
Whenever I'm developing something, I ALWAYS keep coming up with new (good) feature ideas WHILE programming. Now, this isn't as bad because they enrich the software/service mostly but goddamn, it's so fucking annoying when I'm working on a certain function/feature and I change stuff three motherfucking trillion times before finishing it because I keep coming up with fifteen billion new ideas.
In the end it's all worth it but at some moments it gets really fucking annoying.9 -
**idea** => implemented.
An android application which aims to track Emergency Response Vehicles(e.g. Ambulance, Firetrucks) nearby.
Any suggestions, feature ideas are welcomed.
If you wish to contribute:
https://github.com/MakrandBhale/...
P.S. I'm new to Git.
21 -
Going to bed like... I can't wait to continue this new feature I'm working on. But I need sleep. Decisions, decisions... ,,🤔
-
How I want my Git history to look like:
New Feature - Step 1
New Feature - Step 2
Adjustments
...
How my history looks instead:
Super massive Mega Feature
Fixes
Fixes
... -
That moment the sales guys ask if a humongous new feature is doable. And doesn't wait for your answer before adding: "Well so you know, I'll already promised it to the client for last week"2
-
Sprint planning:
PO: I have a great idea for a new game changing feature
Team: cool, let’s talk requirements, etc
PO: nah, I trust you can come up with the best implementation possible
Sprint demo:
Team: presents the feature
PO: Why are you guys always doing it your way, instead of following my vision?!
Every single sprint...3 -
Maybe not a new rant but: When someone asks you for a feature and always says "its easy and simple" ... Yeah right... 😡2
-
!rant
@dfox
Many people use snippets of code in their Rants, so it's maybe a nice feature to be able to add codeblocks to rants..8 -
When you've written out a grand and glorious rant or maybe an idea for a new feature, you're about to hit Post, then suddenly you realise - "Nah, that's shit" and close the modal.
-
Client sends several emails requesting a new feature. Not a single reply when you email them about said feature.
-
I just fucking love the feature of "click outside the textbox and lose all you wrote" on devrant, keeps my blood boiled just right. I am counting every second until the new webapp is supposedly coming 😢7
-
* 1 day of requesting the feature, deadline not for a while*
switch{
case 1:
Manager: How's the new feature going?
Me: I've done a bit of the front end. Here's how it will look.
Manager: Oh great it's done! Does it do ABC as the client requested? Does it also do XYZ that I just thought about this second?
Me: eh this is just part of the front end, I haven't even connected it to the backend - I haven't even started the backend.
case 2:
Manager: How's the new feature going?
Me: I've done a bit of the back end.
Manager: ok. Can I look?
Me: we'll it's just code... *shows them the code*
Manager: oh... so it's nothing really. Call me when it is done
}3 -
Client writes a bug report: This and that doesn't work.
Me: This functionality never was implemented. Please open a feature request.
Client: But this is a bug. Without this feature, the service won't work as we expect.
Me: But this wasn't in the requirements for release. So you have to contact the PM for a feature request.
Client: THIS IS A BUG! FIX IT!
Me: GO FUCK YOURSELF! THIS IS A NEW FEATURE AND YOU HAVE TO PAY FOR IT!
Unfortunately, I never sent the mail. But I kept it in the drafts. Maybe someday...1 -
Guess who implemented a whole new feature in 3.5 lines of code and a simple CSS class.
This awesome guy.
Take that, frameworks.6 -
Added a new feature. Saw no traffic. Removed it thinking no one liked it. Receive a bunch of angry emails.
I forgot to tag shit properly. FML. -
Probably gonna leave devrant until we get a working block feature. Or like. Any new feature at all. The last was pixelated fucking icons in april. Feel like david and tim kinda burned out or gave up or something which would be fine if the opensourced devrant but no i guess. See ya later fuckers.23
-
Do you think refactoring code adds value?
Pick one:
1. Hard No (Only refactor when there is a dollar value associated with it, i.e new feature depends on it).
2. Somewhat Yes (Futureproof your code, anticipate easiness to build feature requested in future).
3. Yes (Developer happiness, retention and for point 2)27 -
Expectations VS. Reality : A new Software Project (After all designs and requirements are clear and fixed.)
EXPECTATIONS:
Day 1: Create workspace, Configure tools
Day 2: Implement high priority Feature
Day 3: Write UT and peer review
Day 4: Push first feature to Prod.
REALITY:
Day 1: Create workspace, Setup configurations
Day 2: Still setting up configurations
Week 1: Almost done setting up configurations
Week 2: New migrations issue, again reconfigure before coding starts
Week 3: Take a vacation
Month 2: Finally things are working but God knows what was the issue...1 -
When they announce a new feature in a video that goes live today, but the feature isn't build yet. It isn't build yet because they never told the IT department that it should go live today. So now I'm stuck hotfixing it.1
-
How I felt after spending an entire afternoon planning and designing a new feature for a project only to realize half of my design was wrong after I started implementing it
1 -
For fucks sake...
If it is a new feature, out of scope for the next release ...
It is OUT OF SCOPE FOR THE NEXT RELEASE, MKAY?????4 -
Sat for hours programming in a great new feature. At the end I tested it... and nothing happened. It didn't even have any effect. It just continued as normal. Talk about deflating enthusiasm...2
-
The newest version of MacOS has a new feature: dark mode.
Um, do you really need to update the entire OS to change the color of the UI? Why is that news?5 -
>site is production ready
>client requests new feature by end of week
>add feature and then site breaks on last day of week
>client freaks out even though we warned this is what happens when you add new features DURING LAUNCH WEEK1 -
New dev at our company. After two weeks he has finished a feature for a project. Want to merge it into the dev branch ... he worked in the master branch.2
-
Beware of scope creep. If it's a bug, fix it for free. If it's a new feature or changed from the original signed off scope, charge for it.1
-
Hmmm. @dfox, there seems to be a problem. I click on a rant, and it takes me to a collab page. Is that a new feature? :)5
-
PM : Develop this new feature. Client needs it tomorrow. And be sure it works perfectly well.
Dev : haha how can it work without bug if it's developed in a day ?
Poor dev got transferred to support department :(
4 -
Just checked my work email to see what's coming in today....
And see someone on the London scheduled a 9AM meeting with me at 5:30AM my time.
Yes thanks for the advance notice...
Not going to be in the morning though and well the whole thing is BS based on some stupid new requirement that doesn't make sense.
Basically asking to migrate a while application to a new platform that no one understands yet.... Just to add a completely unrelated be feature...
Feature: 1month
Migration: 1 year based on the pre-reqs needed5 -
I have a built in NLU and NLP feature for English language within me.
And when I learn a new language, I am basically installing a new adapter.11 -
Google's new feature is to show you a quick overview of a medical condition and it's so cool, I'm having a little stiffy as a medical IT student 😍
7 -
colleague: *does 2 months over making a feature and still didn't get it to work*
me: "this is taking too long, we want to get our new version rolling"
me: *gets it working within 2 hours*2 -
>Adds new feature
>New feature works fine on dev
>New feature works fine on staging
>New feature doesn't work on live
>You can't easily figure out what is wrong because you need to wait an hour for it each time :|5 -
Some feature suggestions:
- Customise order of tabs in new UI
- Highlighting of a rant's OP when browsing comments
- Update screenshots on Google Play & App Store2 -
The face you make when you see the code of the personal application you made but want to add new feature.
-
Oh my god, this client. Everything is equally important. When finishing a feature halfway, a new future gets priority. Nothing is finished, this whole app is a bunch of loose ends. FML.3
-
When you're in a rush to write a new feature but your compiler keeps nagging about not handling exceptions
2 -
After the CTO's Skype call with the top bosses... I embrace my self for new app feature the bosses saw on the some website..during there coffee break.
-
So I showed a prototype of a new feature to my colleague and guess what !! He took the entire idea and implemented it. 😡4
-
Wow!!! I just saw the new devRant upgrade in the App Store. Unbelievable new feature. Can't wait to setup tonite!!! Thanks @trogus @dfox !!!1
-
How far off can you implement a feature?
Task: Update add one feature to this endpoint and add test(s) for the new feature
What happened
* Correct endpoint
* Add 2 wrong features
* Remove one important feature
* Do not the requested feature
* Write a test that doesn't actually test the feature for the wrong endpoint
Intern be like: looks fine to me. Pls review and merge3 -
DevRant needs a save for later option... I see lots of long interesting posts, I start reading them and then something comes up (like a phone call or I need to do something). Then by the time I come back the post is gone, and I’m sad...5
-
Client calls me requesting a new simple feature.
Connect to FTP server.
Edit some PHP pages and upload them back, check if the changes actually worked.
Basically implementing and testing a new feature on a live production website...
PS. It didn't work the first or second time -
The new devRant long story feature is great! Very nice to have them in one place. Thanks devRant team!
-
I am bored !!! No feature request and No bug was reported from last 2 days... Nothing to resolve today.. I am thinking should I create new bug and release it as feature??5
-
devRant should add a new feature to create polls
e.g. 1: What OS do you prefer?
- Mac
- Linux
- Windows
e.g. 2: Which programming language do you prefer for web dev, mobile dev, etc.
- Java
- PHP
...
I bet after a while a cyber war would commence. And that would be devRant's fault because it gave developers a reason to hate each other.
So devRant please disregard my request for the new feature.
Narrator: And then he laughed sardonically.4 -
Producer meets designer.
Monday, 10am email "new task added: implement this new feature. Priority: can wait forever"
Tuesday, 4pm email "change on task: implement this new feature. Priority: urgent, it's a must on wednesday's build"
2 -
That moment when agile means "I will sneak in new feature requirements in with your bug tickets even though our sprint is supposed to be only stabilization". Thanks PM Lord.
-
Uranus never looked so good!
https://nasa.gov/feature/goddard/...
I love the new images of everything they are getting. The people getting pictures at home are also amazing.6 -
Shit. I've fucked up. Will have to rewrite ~20% of the new feature tomorrow :(
I should not have trusted him....2 -
When I realized that programming is the greatest way to make one's living, that I will never love anything more than programming, and that every feature and quirk in a new language is like a new friend.
-
The feeling, when you learn about a new feature of the language, you've used for over 6 months.
The joy of learning something new,cool and useful mixed the pain, of knowing, you could have written your previous projects easier.2 -
!rant
So on the last day before launch our latest feature I'm informed that a requirement was missed and it had to be implemented before go live otherwise the business didn't want the feature. The feature in question was pretty drastic and basically required a scheme rewrite, new tables, etc. So I spent the entire day making the change.
Thankfully I pushed the whole project for good code coverage. Therefore, all I had to do when I was done was run all of our tests and make sure they passed. *warm fuzzy feelings* -
Spotted a new feature that had just recently being completed: "Disable all Logging due to noise". What.
Us on the Ops team just died a bit inside... -
I'm doomed.
My first production worker script is making multiple active attribute of a user. My script should be able to deactive the old attributes if there is new one.
Months ago, this issue occured. My teammate from team A take over the script to investigate since I am busy working with team B.
Yesterday, I found out that I, myself, overwrite the fix my teammate made for that because of a new feature.
I have to clean up the affected records on production on Monday..and i have to explain to my manager. T.T
LPT: ALWAYS PULL REPO before developing new feature... -
loop {
So I want to write a simple program in language X. Create a new project. Language X does not have this feature. Okay, Let me write a library that does that for language X. Create a new project. What was I doing again?!
}1 -
Windows 10 doesn't to let me use my wifi.
*sighs*
No way to solve it.
Is this a new Windows feature?11 -
When you're at the end of a sprint, implemented a cool new feature and only the garbage issues are left over -.-
-
upgrade to the latest pre-release of Xamarin forms for a shiny new feature, now nothing works even after reverting. You'd think I should know better by now.2
-
Was just asked to review a new set of libraries that the "experts" from our contracting wing created.
I opened one and the readme lists its features as:
Features:
- Feature 1
- Feature 2
- Feature 3
and the Faq is:
- Possible question 1
- Answer to question 1 -
Backend : *breaks feature in prod by changing api*
Me: Feature is broken in prod. Please fix. I was told that the API will not deprecate the old use case.
Backend: ... Fixing it in the backend will take time. Add support for it in the frontend.
Me: I'm not done with the new feature just yet. And it will take some time to have it reviewed and fully tested. Please fix the API.
Backend: .... Well, make a new PR and add support for it first. The new feature can come later.
Me. (-_-) Okay
Sometimes it feels like I'm a code janitor rather than a frontend intern2 -
When your new feature works (and you installed a new package from Nuget) on your and your co-workers environments. And then you push to the build-QA-server and it breaks...4
-
So apparently Skype has a code editor for interviews.
Would you use this tool?
Source: https://techcrunch.com/2017/08/...8 -
I am fucking dumb, why I've created an empty project to implement the new feature instead of making a fucking local branch. Now I need to merge this shit manually. fuck fuck fuck5
-
To you, who use Windows 11. Is there at least one feature that makes you glad you switched from 10 to 11? Or maybe not necessarily glad, but it would make you appreciate the new OS? One thing that would make the upgrade worth it... I myself can not think of a single fucking thing. (Please don't say better HDR support, that's the one most often mentioned feature. Definitely not good enough reason to have a new OS)11
-
Honestly,
Netflix you should add toggle option for series like feeling.
mhm hrm with that I mean:
It would let us to watch an episode only once a week, based on how it came out.
no more binging on the same shit like crazy.
Someone needs to be first with this,
Also everyone is doing this self control alert like behaviour in/through apps cause we all tend to forget it when we have a lot of availability to overeat ourselves.
Rant end1 -
A new project kicked off, where a new feature will be added to our app. The mythical creature called "Project Manager" asked us to take OT's and weekend work to rush and finish it. Aaaare you f*ckin' kiddin' meeee??!2
-
Aye, new speedcoding video, this time its a 2 line BASIC program rewritten in js
https://youtube.com/watch/...
also thanks for following my github, i feel famous whenever i see a new follower i dont know personally -
TFW the mock class has way more code than the real one.
Testing big infrastructures can be a pain...
Or maybe my team is just not so good at it.
My time spent:
Adding new feature to the real class 15%
Extending the mock with the same feature 55%
Writing tests 30%7 -
When backend is slow to add fields of data, and product manager is after you, the frontend dev to add the new feature.
-
When you are new to a technology and language, but have to make full use of its feature.
You know, make tests, implement production code, planning deployment, build a CI. All by myself.
No regrets, though. Challenge accepted!1 -
The mechanical team once told me, hey I want this feature on the software - sure it will take approx 1 week. Yea I know, but I want it without any bugs.
WTF?? They sure got some f words from me. 😅1 -
When will a client finally understand I can't just 'implement a new secure chat feature but only for these people' before lunch2
-
I don't think it should take "years" to develop a card sorting mechanism.
Android devs do you agree?
( This is picked up from the release notes of Trello. )
6 -
My boss will complain about the missing comma in a sentence before he appreciates the new feature added to the app or how fast the app loads.....2
-
When you spend months putting together a major update for the original scope of a project, release the update to a client, and the first thing they say: "Where's that new feature I asked for last week?"
-
That moment you realize you're starting your shiny new feature by searching the Wayback Machine (web.archive.org) ... because the company you're integrating with no longer exists.2
-
When client for past few days tells you how important that new feature he wants is, and you should get to it asap.
But then when you actually start working on it after discussing it, specification creation and preparations, with mind set and focused, he tells you:
- 'Know what? I will need that change in the old feature before that. You can postpone the new feature by one day.'
So... How was it the most important thing in the universe again? -
Holy balls, autofill is my favorite new feature of Android!
My keepass, which I've been using and been hopelessly dependent on since 2002 or so, is now compliant with autofill through keepass2android. Cackling with glee over here.1 -
Test A succeeds when run solo. Test A fails when run in conjunction with Test B. Obviously, some kind of messy state that isn't isolated per test.
I realize what it is, so I add a new feature to address it.
Test still fails, it had nothing to do with that.
I finally realize what it was. One liner fix.
Yay for a new (useless?) feature that isn't getting backed out. -
I just blew up at my boss again.... I'm doing something and then he asks about including a new feature and figure out if it's doable. A quick question is ok but an analysis of a new feature.... NOT WHEN I'M IN THE MIDDLE OF RESOLVING A MORE IMMEDIATE ISSUE.
OPEN A FUCKING JIRA, SEND ME AN EMAIL, AND I'LL TAKE A LOOK ONCE I'M DONE WITH WHATEVER I M DOING.8 -
What do you guys think about the new "type inference" (var type) feature that will be introduced with Java SE 10? I know that C# already has that construct. It's pretty controversial among my peers... 😅4
-
Please please stop asking me every time I present some new feature if this is something we can patent - I have no f*cking idea and you’re missing the point!2
-
Waiting to merge the rest of the team’s new code because you don’t want to deal with migrating your test account to a new backend until your feature’s ready, finally finishing your feature (!) and then seeing 100+ merge conflicts and realizing you‘re better off just re-implementing all your feature code into a new branch, & deleting every trace of your old branch so nobody sees the 1000+ merged commit mess you’ve made -_- today was supposed to be easy...
WHY WOULD ANYONE NEED THREE DEPENDENT SUBMODULES ANYWAY?!?! 😩1 -
My new feature has a bug in it, but not in Internet Explorer..
Huh? This is new! I know this the other way around! -
Adding a new feature to a mobile app that has a bunch of classes for getting URLs! Want some examples?
FallbackUrlProvider
CompositeUrlProvider
CompositeRouteUrlProvider
CompositeBaseUrlProvider
RootUrlProvider
I was half expecting to find FallbackRootBaseCompositeUrlProvider!
Not only that, but there were a load of interfaces that sometimes didn't match the name of the class!!!
For example,
class RootUrlProvider : ICompositeUrlProvider
Ugh! But I managed to get the new feature in... Somehow... After trying something... Throwing it away... Trying something else... Throwing it away...
😭😭😭3 -
It doesn't mind WHEN you'll complete a job.
What's really matter is WHEN your client will call for a new feature.1 -
>add new feature, push to seperate branch
>ask other dev to have a look at code
>other dev completely rewrites the feature and pushes directly to master
please1 -
Current deploy process on the legacy project I'm on right now: ssh to server, check out branch with new feature, test on live, if it works then merge to master and check out master.
Oh... Oh no... -
System architect make feature to print password, when you create new client. It was architecture for backend server. Just why and how?!5
-
Wanted to remind you Americans that it's too late to start on a new feature, function, or debug. Go to sleep after leaving yourself some notes. You'll be better off in the morning.3
-
Finished my work on analytics and ads feature of the project.
The urge to push it under a new branch with name "AnalAds" is real xD2 -
Hopefully at work we have successfully migrated from a combination of MySQL and Mongo to only Postgres. Also we finally split up our monolith into medium sized services, so we can actually do something interesting and update our dependencies.
And port one of the services from Java Struts to Django..
..but that is only if developers were to set the plan...if sales/management: new feature here! new feature there! sell sell sell! No time for maintenance! -
When you add a feature to your app, test quickly and see the new feature works, so publish to play store, only to discover you have broken core functionality 😭.
This just happened to me, I discovered it not log after the update and had to rush to fix it after discovering the play store has no "roll-back" feature ☹️.3 -
Customer calls
Talking about some new feature he haven't totally thought about. so i tell him to think about it.
Talking about a bug, but can't reproduce it.
Talking about another enormous new feature but halt it after hearing the initial estimation.
Total time waster = 1.5 hours for every day.
DON'T LET CUSTOMERS WASTE YOUR DEVELOPMENT TIME.
instead of talking - use project tracking software (i.e. JIRA) -
So I just got an email from Github, saying they created a new package for Atom called Teletype.
I quote: "Teletype (beta) for Atom lets developers share their workspace with team members and collaborate on code in real time."
Wondering what the devRant community thinks about this new feature!
https://teletype.atom.io/1 -
Sitting in a meeting discussing writing end user docs on a new feature and one of the product managers literally said "we'll end up picking a number out of the air."
-
Iphone 8, 8+ and X. Rants anyone🤷🏼♀️🤦🏼♀️? I'm just pissed they're trying to imitate Samsung and still claiming "new feature"😒
Drop yours👇👇6 -
I fucking hate how big companies advertise their BIG NEW FEATURE as innovation and jump two major versions because of this...
New update:
UPDATE FROM 2.1.1 TO 4.1!!!
YOU CAN NOW ROTATE THE DISPLAY IN THE OPTIONS SCREEN AND IT ALSO ROTATES ITS VIEW.
WTF?!?!7 -
What do u guyz think about Amazon Key?
New feature that allows delivery personnel unlock ua home door?4 -
Google Keeps new "subtasks" feature is soooo bad
but atleast they are multiplatform: its shit both on Android and in the webapp -
>People ranting about Whatsapp not adding features
>Whatsapp adds a feature
>People ranting about the feature whatsapp have just add
And this happen all the fucking time. When the double-check turned blue and in almost all major improvement they've made
Am I the only one who likes the new feature?
Peace guys, I don't want to start a telegram vs Whatsapp war here :P3 -
What if one day you wake up and surprisingly you find new feature by Github called Github stories.
What would it be....
Go ahead improvise.6 -
Meet up with a new client, everything looks good feature wise and planning. Then the $ hits & I get hit up the fucking ass again.3
-
When a client keeps asking about how a new feature works...
Have you even bothered to read the fucking concept? IT'S ALL THERE!!! -
PM: let's show customer the new feature while it's still in the develop branch
Me: no fucking way this could ever happen -
Sometimes I genuinely wonder what the thought process of some people is...
git checks out feature-X branch
git creates new branch off of it to work on something that has absolutely nothing to do with feature X
then opens a PR back into feature-X
Me: this has nothing to do with feature X.. i think you meant to branch off of develop and PR back into develop, no?
Them: no it was intentional .. feature-X will eventually end up on develop so I thought we'd get both features on develop.
I'm not even mad and this isn't a rant, I'm just really confused 🙂4 -
Everything was good. We were a very sophisticated agile team. We knew our work very well and we were proud of it. Every new feature was implemented in matters of hours. Everyone happy. Me, other developers, managers, customers. Until the other team felt a bit bored and decided to build a New Deploy System!
-
New strategy to combat managers:
If you claim we can't afford the additional time for the tests that come with the feature, I won't build the feature.
If you claim we can't afford the additional time for the proper API versioning that comes with the feature, I won't build the feature.
And finally, if the internationalized texts, designs, and image assets are not complete when it comes time for development, I won't build the feature.
It's time to rise and stand against the "You're an engineer! do it all!" notions. I'm not a designer. I'm not a translator. I'm not a by-hand manual customer tester. And I'm certainly not going to take any more of your shit.2 -
I was about to implement a new feature (which I will call feature X), but I was not sure which branch feature X should be implemented on. Because of different products, there are a lot og branches around.
I was going to implement feature X on branch A, but that branch was currently not working, and someone was working on fixing it.
I was told by my boss to branch out from branch B as feature X would be merged in there later anyways.
And so I did.
After I am nearly finished with feature X I discover I need feature Y from branch A. Feature Y is not yet on branch B, but is scheduled to be merged in some time soon.
So I can't really finish feature X before that point, and I am told by colleague 1 I should have implemented feature X on branch C, because feature Y is there and branch C will be merged into branch B soon.
However, I found out that this has happened before.
First, colleague 1 was told to implement feature Y on branch A. This is the real implementation, the one I need. After he had spent a week implementing feature Y, he was told by colleague 2 that the feature should be implemented on branch C, which is branched off from branch B (I think). So he had to spend a day or two to move feature Y to branch C, but he still kept feature Y on branch A, because all branches will eventually be merged into branch A.
After a week or so, colleague 3 asks about feature Y and is told that the feature is on branch C. But colleague 3 need the feature on branch D, which is branched off branch B for some weeks ago.
I don't know all the details here, but colleague 3 ends up implementing a version of feature Y on branch D and he is happy.
I don't know how much time was wasted because of wrong information from management, but I have no intentions of wasting more time. I'll wait for the merge of branch C into branch B.
If this rant makes no sense, that's just my reflection of management some times.
I love management.4 -
That feeling when a new feature works on a local build, works on the development server, and works on the QA/UAT server, and then still breaks production when deployed.2
-
My model for one part of my project has become so crazy big I’m become lost every time I add a new feature or debug :-/
-
Spend two whole days solving an exception in a new feature, then the client decides that the old version is the way to go..1
-
When a junior developer forks new feature branch from his old feature branch and not from develop branch causing merge conflicts later!1
-
...when your project TODO list is growing exponentially and you just give up tracking new ideas/feature requests
;(1 -
I started using Gmail labs canned response feature. Access it from gear / settings / lab / canned responses. When composing new email or responding its in little dropdown next to trash can icon. Might save you time.
-
Has anyone noticed after the subscribe feature, they check Feeds less and just look for new Notifs?
Or is that just me?6 -
Bugs: These are not bed bugs. For programmer they are a nightmare, to customer we introduce them as a new feature and say, “My software has no bug. It just develops random features.”
-
E-mail the supervisor saying I'm prioritising this new feature because it's more important. Not because it's currently broke and I'm stuck.
-
-New feature ^^
-Test broken!
-Fix test for the feature!!
-Test suite broken!!!
https://video.fbts1-1.fna.fbcdn.net/... -
When oracle employees decide to add new "feature":
How can we add feature X so it can be the user new most terrible nightmare?
When oracle employees decide to update an existed "feature":
We have discovered that the users of feature X have found a work-around to make it useful, we need to update that feature to make it the users most terrible nightmare ever, and we would like to make the upgrade/installation process break everything else installed on their machines without possible way of recovering, and if it worked by any chance we would like to make that process frustrating as fuck.7 -
The ability to make developers improve existing libraries/frameworks wherever possible instead of creating new ones every time they encounter a 'Feature X does not exist in library Y' type of scenario.
-
I had a branch <refactor> where I changed the structure of some folders (and did appropriate changes in imports) for organization of the feature I'm developing; I then merged <refactor> into <feature> and created a PR from <feature> into develop. I let the PR be known in Slack.
Yet nobody reviewed the PR.
Whatever. I created <new-feature> from <feature> locally, and started working on it. Then I merged <new-feature> into <feature>, and pushed it into its remote counterpart... well, only now have I realized I haven't merged the remote <feature> into develop. Now I have a PR in which the documentation doesn't tell all the changes anymore. Because nobody reviewed it before and I couldn't merge it. Now instead of keeping on working I gotta come here to vent my frustration before I can do anything.1 -
>new feature in application uses external API
>external API has unreliable response times, requires polling to get results, no way to set up webhooks or whatever
>tech lead proposes asynchronous system which will queue up user requests for processing and use websockets to warn frontend clients of finished query results
>higher ups say it will take too much time, make tech lead cut back in scale and treat external API like a regular synchronous REST API
>team dutifully implements feature within the constraints of the new smaller scope
>higher ups try out the feature, find the usage experience is extremely shitty, but don't back down, they only let tech lead scale back to original scope in small increments that still allow new problems to show up
>feature takes up same time or longer, but with more damage to the mental health of developers
At least I'm not in that team1 -
All day working on a new feature for a React application, on the bus thinking about how to continue working on it tomorrow (Saturday) just to realize that I didn't push my branch. :(2
-
Those of you who wants the bleeding edge of technology, here's the one for YouTube:
https://youtu.be/addme/...
This unlocks the sharing tab on YouTube's mobile app, like in the screenshot below. Make sure you are on your mobile device.
Enjoy sharing! :D
//Oh right, it's supposed to be a rant -
Gosh I hate when I ain't in the new technologic stuff already 'ghah 😡 😋
1 -
Three possible strategies for adding a new feature. Not sure which is the best, so I'm going to go with the one that's least invasive to the existing structure of the database.3
-
I have a git feature branch with my commits but also have merged the changes from the main branch to resolve merge conflicts before PR.
But now need to create a special release with just my changes.
So I think have to cherry pick all my commits on my branch some the last Release. How can I do that?
Develop (others) + Feature => Develop
Want to create new branch
Last Release + Feature (but only my commits since last Release)4 -
@dfox
first, avatars are a great idea!
BUT I dont eant to wait until i have "n ++" to change the what computer (mac/non mac) is on my avatar/profile image. [the thing with the desk and watch is ok, but i think unnessesary. I wear a moto 360 every day so why schiuld i have none or another one that dose bot look like the one i am wearing on my profile picture]
COULD "BADGES" BE A SOLUTION ?
3 -
The fact that it sometimes makes me wonder "Why am I learning this? This feature seems better implemented in newLISP." when I am learning a new programming language.
-
Getting a pretty big project for a new feature on the main site, and getting called to change stuff on the existing features every day....
-
Google: "Your update is now live"
Me: "Excellent! Time to start working on that new feature. I guess it wouldn't hurt to make sure the new live update is working fine"
*uses new update*
*realises I have to fix something in the new live update*
-
Friday morning's meeting:
CTO: Ok guys, deadline is next Friday so today we close the last big issues and next week no more new features, only bug fixing.
Monday morning's meeting:
Business: So here is the new mock-up for the search feature (basically they changed the whole behavior).
😐1 -
Finally got the next part of my new feature working. So much rework has gone into this due to miscommunication. Now comes the fun task of a mass of unit test writing!3
-
Finally got the data from my API and displaying in my app using RxJS, so I work on getting user data read in after passing through an SSO page. Now that works but the original stuff doesn't.1
-
I must deploy a new solution today so my product owner came to ask if I finished and asked a new feature for today asap.
-
Hate when a new feature requested by betatester require to change the datastructure. Those feature that force you to start a refactoring while u still in betatesting. Are good in a way, but so much frustrating to get back to alfa or in dev phase while u were just happy that this project came to an end and delivered2
-
Great feeling when the pen testers couldn't find the "unfixable" vulnerability your new feature created, and you go on holiday soon.
-
It sucks when you are unable to work on any new features in forever and mainly spend time updating the existing code base, doing visual designs & documenting the application.
Let me please work on a new feature that the clients will use instead of meaningless busy work2 -
Google is all about bringing new features, which are normally good ideas. But did why don't make what they already have?
You are normally operating with a beta tested base and some new alpha feature. -
ES(afaik)2020 has a new private field declaration proposal feature in classes. I made a gist to try them _when they are implemented properly_.
Gonna test on chrome lolz.
https://gist.github.com/fbarda/...5 -
Every time we ask the directors what they think about the design. They introduce a new feature...
Can't you just decide what color will be the plane without changing the maximum speed???? -
@dfox i like the new stories feature. would be cool if there were another section that only showed posts with pictures. kind of like imgur is to reddit
-
@dfox I am not getting push notifications on my new oneplus 3t.... What to do?
I used android migrate feature to auto login apps from my last phone...9 -
so we started new branch to develop new feature. then merge to staging. then from staging merge into master. master means production for us. this is website so this means continous integration. how you deal with versions? what i do wrong?
-
When you have just made a new feature and you rebase to master, and the project won't compile because someone else pushed something which doesn't work...2
-
The new feature on Stack Overflow tells me that I'm way underpaid. Guess I should ask for a big raise or start doing less lol
-
Working all day long on a new feature to resolve a perf issue but realised at 6pm only that everything was pointless. I love my job
-
Creating a new class to help implement a new feature. Start with my tests (going full TDD).
Feature gets more urgency given to it, write slightly less tests as deadline approaches (half TDD).
Out of time, any future tests are burnt (no TDD) as I frantically wrap up the class with not even the time to write down a plan, it's live coding at this point. -
Multitasking is never easy. I can't debug code on one codebase and write new feature for another codebase at the same time.
-
Investment was lost because we didn't have the AI feature yet. There go the new programmers I wanted.3
Top Tags
Weekly Rant
View