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 :)

I added a “shake-to-snow” hidden feature to an iOS app that worked only on December 25th. You’d shake your iPhone or iPad and the entire screen would start snowing for 10 seconds.

devRant should add a polls feature for simple questions with yes no answers or what version of linux people use etc maybe?

Hey everyone! As many of you have already seen, we just finished rolling out a new feature that allows you to subscribe to specific users! This feature sends you an in-app and push notification whenever anyone you subscribe to posts a new rant. You can subscribe to a user from the button in the top right of their profile or one of their rants.

Please let us know if you have any questions!

P.S. apologies to those who already subscribe to my rants and got a notif before for a test rant I created. I forgot we had subscribe now :)

How my birthday is going so far:
1. Dropped coffee on my shirt
2. Client is wondering why we removed a feature that he wants yet asked us to remove a week ago
3. Dev server is no longer working
4. Internet connection is shit
5. My VPN keeps on disconnecting (see #4)

Is this day going to end or what?

- Is it a bug or a feature ?
- Yes !

Fuck any dev who thought playing sounds automatically on a webpage or on a mobile app without user's consent is a good feature. Especially when you don't even include a setting about it.

Yes I'm directly swearing at any devs from Instagram.

carbon monoxide sensor was triggered when someone farted.

is this a bug or a feature?

Saturday late night wisdom.

Software developers you need to work on communication skills.
Everytime LinkedIn says need a problem solver. It means a guy who can understand what non technical guy is asking for and translate that to a software or at least come up with a example of why he is wrong. Explain them. They are not dumb fellows for asking that feature. You might think the feature is stupid. Don't assume this. Sit with them. Understand thier user flow, understand the frustration your software is causing them. Then you'll see why are asking for that X feature.

Every feature request made is basically my opportunity of understanding of product. Don't wait for users to tell you requirements. Understand and suggest, implement prototypes and show them, a causal question such as "Hey would you think providing a keyboard shortcut for this submission is great?"

Understand our job is not just to write software.

Our job is to solve thier problems using software knowledge.

Don't you agree ?

Swag store feature request:

I can't wear any of the shirts at work with current dress code rules. Any chance we could get some polos or golf shirts with a small, embroidered ":/" on it?

I'd buy a week's worth of those.

A bug or a feature?

PM: is this a bug or a feature?
Me: yes!

:P

I was able to subscribe to my own rants 😂
Is that a bug or a feature?

"Please add a feature to check the user's internet connection before the application starts."
-- THIS IS A GOD DAMN WEB APPLICATION, YOU DUMB MORONS! Maybe I should add a feature next that checks for the user's computer being turned on or what? How about making sure the application isn't run when the power is out?!
Jesus fuck.

My time as a Dev have given me deep mistrust of the following words;
Only
Just
simple
Quick
Easy

Any requirements, specs or feature files presented with the above words should immediately be deleted and/or burned if in hard copy.

Let's settle this:
Blockchain is just a dumb database, the feature that makes it amazing is trust-less ness.

Its not meant to make a decentralised uber or a Tic-tac-toe game.

Leverage the advantages of the system and solve real problem.

Client: "I did not receive the email that should be send after that event. Please fix."
Me:
* Checks code - ok
* Tests feature in locally - ok
* Tests feature in production - ok
* checks values in database - ok
* 2 hours wasted - ok
"Please help me dear CTO, idk what else I could check or how I should even respond to this."
CTO: "hmm, the clients account uses a adminstrative email address for testing. Let me just check if it is in the mailbox."
*checks* "Yeah, that's the email you're looking for, right?"
Me: *experiences relief, anger, blood lust and disappointment at the same time* "Could you please respond to the client for me, I need a break. Thanks"

iOS13...

No wifi connected icon
No magnifying glass when moving cursor
Random wifi disconnected

Did they even test this? Or this is a feature?

Managers: wE wAnT tO bE LeAn aNd MoVe FaSt As PoSsIBLe wiTh NeW FeAtUrEs

Same Managers: Can you make this icon 2 pixels smaller?! Shift this element left?! Swap out this icon?! Use a different color here?! A perfect feature and design is critical!!!!!!

FullStackClown: You can either be lean and fast, or be fucking nitpicking clowns 🤡 about this stuff and slow us all down. Choose one.

Managers: ...

FullStackClown: Sit down and shut up

Dear fucking boss,

If you want me to implement a huge feature which requires the creation of dozens of db tables, server side classes and front end pages, just fucking stop ask me every 2 hours if I’m done.

Best regards,
The employee that will quit in a week or two

Client : can you add a calling feature to our android app?
Me : Ok.

*** after updating the app ****

Client : what is this **** dialog (calling permission request for android)!
Users are complaining about it and refuse to use the app!!! Don't you know I can get into legal problems with this???
Me :But you just asked for this feature?
Client : I want this feature but remove the dialog.
Me : you can't that's not how google works.
Client : I don't care do something remove the dialog or edit it but keep the feature.
Me : 😑😑😑😑 nvm I'll figure out something.

Ended up with copying the number to the dial screen instead of direct call from the app.

Last week I had a presentation of a project (webapp) for a customer.

She: "Can I do {insert feature here}?
Me: "Is that a question or a feature request?"

Ticket: Add <feature> to <thing>. It works in <other things> so just copy it over. Easy.

Thing: tangled, over-complicated mess.
Feature: tangled and broken, and winds much too deep to refactor. Gets an almost-right answer by doing lots of things that shouldn't work but somehow manage to.

I write a quick patch that avoids the decent into madness and duplicates the broken behavior in a simple way for consistency and ease of fixing later. I inform my boss of my findings and push the code.

He gets angry and mildly chews me out for it. During the code review, he calls my patch naive, and says the original feature is obviously not broken or convoluted. During the course of proving me wrong, he has trouble following it, and eventually finds out that it really is broken -- and refuses to admit i was right about any of it. I'm still in trouble for taking too long, doing it naively, and not doing it correctly.

He schedules a meeting with product to see if we should do it correctly. He tells product to say no. Product says no. He then tells me to duplicate the broken behavior. ... which I already did.

At this point I'm in trouble for:
1) Taking too long copying a simple feature over.
2) Showing said feature is not simple, but convoluted and broken.
3) Reimplementing the broken feature in a simpler way.
4) Not making my new implementation correct despite it not working anywhere else, and despite how that would be inconsistent.

Did everything right, still in the wrong.

Also, they decided I'm not allowed to fix the original, that it should stay broken, and that I should make sure it's broken here, too.

You just have to admire the sound reasoning and mutual respect on display. Best in class.

Simplicity is a prerequisite for reliability.

I put those words on the wall in giant vinyl letters, and I point to them every time someone asks me "can you add a frontend button which checks this external API and stores the correlation between the amount of rain and the sales numbers of purple buttplugs inside the user profiles?"

People always ask for one more column in a table, one more paragraph under an image — they never ask for replacement or removal of items.

So I force them. Want a feature? Fine, if you point at something of equal or greater complexity to delete.

@dfox
!rant, it's the Feature request

Possibility to post `a code snippet with monospaced font` would be usefull.
Or even
```
def multiline_code():
from 2 to Inf:
"Lines of code"
```
Sth like in markdown.

semantically right, but syntactically wrong.

Bug or a feature? O.o

Deciphering 10-20 jira tickets that relate to 1 feature which aren't linked in anyway beyond titles spread throughout an epic or 2.

Ah the pain of having to go through 200 tickets to find everything you need for a single feature.

I just told my biggest client that they have to start changing things or they will need to find a different company to work with.

I'm hired to program what they want. They are suppossed to do all the concepting, functional designs, QA, testing.

So they tell me to program feature x, not realising that this interact with feature y. And then complain about the change in feature y. Make me do a lot of extra work and then complain that my estimates are way off.

So I told them they also need to hire my company for the software design and QA and prefferable testing because I'm done getting blamed.

So I remember this QA I had for our thesis and the panelist asked me
"So is it a bug or a feature?
i answered
"Yes"

Yo gods of devRant
Can you keep this as a feature? As a switch or something perhaps? This pixelated avatar is sick!

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!"

😡

During a meeting with the client

Client: I don't care how long it takes to complete the app, I want the app to be polished and give the users the best experience!
Us: Got it.
*Later that day*
Client: *wants to implement a new feature in the app*
Us: It'll take us a day or two.
Client: That long?! I need to get it to the market ASAP!
Us:.......

:D

Manager: Here's the design for the next feature, we're ready to hand it over to the consultant

FullStackClown: Uh... okay... is it spec'd out with requirements?

Manager: Huh?

FullStackClown: Well, already look at this design and user flow, did you consider what happens when <insert edge case X here>, <insert edge case Y here>, or <insert edge case Z here>? How is the consultant going to know what to put in for business logic if you don't even know or define it yourself?

Manager: Huh?

FullStackClown: Sigh... yeah, I'm too busy right now to be a kindergarten teacher, come back in a few days once you understand how your own feature is supposed to work

Manager: ...

Dev: ...

What do you guys think of having a "go anonymous" feature while ranting?

I was thinking when community will go larger and people who know each other in real life, start following each other, then it might become hard for them to rant about stuff or they might become hesitant in rantings.

The code is a freaking mess. Shared behavior, terrible variable/method naming, misleading module naming, dynamic polymorphic spaghetti, whitespace errors, no consistency, confusing even if you understand what the code is doing, ... . It should never have passed code review. It probably wasn't code reviewed.

The comments are sparse and useless. Quality level: // This is bridge.

The documentation does not exist.

Testing steps for QA are missing several steps, including setup, so actually using the feature is bloody challenging. If one thing is wrong, the feature just doesn't show up (and ofc won't tell you why).

The specs for the feature are outdated and cover only 4 of 19+ cases. And are neigh useless for those 4.

The specs for the report I'm fixing don't even check the data on the report; it just checks for one bit of data on each row it creates -- a name -- which is also the same on each row. gg.

The object factories (for specs) are a mess, and often create objects indirectly, or in backwards order with odd post-create overwriting to make things work. Following the factories is a major chore, let alone fixing or extending them.

The new type has practically zero test coverage.

The factory for the new type also only creates one variant -- and does so incorrectly.

And to top it all off: the guy who wrote the feature barely ever responds. If he does, he uses fewer words than my bird knows, then stops responding. I've yet to get a useful answer out of him. (and he apparently communicates just fine, according to my micromanager.)

But "it's just fixing a report; it'll be easy!"
Oh, fuck off.

sometimes I feel there must be a bookmark or favorite feature in devRant to save all those awesome rants

Making an Android app for a group project. Of course, no one besides me in the team knows anything about Java, or Android, or life, apparently.

A guy "worked" on some small feature for 90 minutes last night before calling me for help. He can't comprehend git so he sends me a message containing his spaghetti code. I proceed to bang it out quickly the right way with him on a Skype call watching my screen but he isn't asking any questions or contributing at all. We have an approaching deadline so I am beyond coaching this guy.

We go to test it out and I had forgotten a line. Simple fix, but it prevents the feature from working as intended. Rather than being remotely helpful the guy gets an attitude about how I write buggy code and that the feature should be robust. I fix it and he slinks back to silence.

Cool. Thanks for the help bro. Glad you could contribute.

Manager: Could you create the UI for the new feature? The client wants to test it. We need it in 3 days.

*1 week later*

Client: IT DOESNT WORK

Me: This is just a visual demo... but everything will work when we realse the feature.

Client: okay but can I see what it will do?

Of course you can! Just wait until we relase it!

*2 weeks later*

Manager: What are you doing?

Me: Working on the UI for the new feature.

Manager: Wait, hadn't you already done it for the demo?

Me: That UI didn't really work. It was basically a bunch of HTML, without reactivity or abstraction or any functionality.

Manager: Okay, how much where you able to re-use?

Me: almost nothing.

Manager: So... you wasted those 3 days?

Oh so I'm the one who wasted 3 days.
Me: Kinda, yeah

Manager: Why couldn't you have done this when I asked you to do the UI?

You can't expect good quality code in 3 days. Pls stop wasting it on demos.

I've been working on implementing a fairly large feature on a project at work--

**Sorry. I should rephrase that**

I've been *trying* to work on implementing a fairly large feature on a project at work.

It's slightly complicated because I'm not as "in the know" with the project as I should be. I get tossed around projects a lot as the only designer+developer so I've got my hands in a lot of buckets... Or git repos I should say... My source tree has a lot of tabs open and each project is run by someone with their own ideologies on how stuff should be done and laid out and what not. Basically jumping between these projects leaves you mildly capable on all of them but not amazing at any of individual one them--

--I digress.

There's a bug I've been trying to fix.
--Stupid simple bug, literally just a casting issue or something but there's so much data in this one object that it's taking a few solid minutes of concentration to figure out which variable is busting it all up. It shouldn't take long to fix...

But it has. It has taken 4 days.

FOUR. DAYS.

...To fix what is basically a null reference exception.

Every time I sit down to work on this bug real quick I get pulled away to do a wireframe or change a flow chart or diagram or colour or print styling.

Every. God. Damn. Time.
4 days. Soon to be 5.

My commits are real low at this point guys.

Please boss man, just let me code...

I feel like a stalker now... or I invented a better Algo. Just show me the rants from the people I've followed and also the ones they've +1'd.

Sorry @sirwindfield for making u the example, but hey ur on devrant.io anyway...

But I guess this was the Twitter feature that no one wanted... o well... that's why I program, I can do whatever I want :)

planned a project,
spent a whole day on a feature.

3 weeks later, i realise that feature i spent a whole day on wasn't needed at all.

i'm a fucking noob ape trying to pretend it's a developer or some shit.

I think I'm already blind. Or the liquor ate a chunk of my brain cells.

I just realized that devRant web version has different accent colours based on avatar's bg colour.

Earlier I realized I have disabled show hidden files feature on my file manager and thought there was no .htaccess file.

F@#$% ANDROID STUDIO! You should definitely add a feature of giving a Pop-up window asking if the user REALLY WANTS TO OPEN THE SOFTWARE OR NOT!
You should see my face when I click on android studio icon by accident 😩 on my Windows...

Marketing: so we want it to behave like this website, so it'll have to have feature A, B, C and D.

Me: okay that might take a day or two.

Marketing: what? can't you just copy-paste the code from that website?

How clients tend to not understand how much work developing a "simple" or "small" feature can be.

Hey add live chat, that's easy right?

> 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"

Microsoft Teams can burn.

Their latest feature ? Well, turns out that when I get notifications on mobile that I do not get on desktop BECAUSE I AM FUCKING INTERACTING WITH THE CHAT OR CHANNEL THAT SENDS ME MOBILE NOTIFICATION, the notifications do not clear themselves. Oh, no, that would be too smart.

So EACH FUCKING EVENING I sit and browse all the fucking notifications to see if there is anything noteworthy I need to act on, or if it is a dead notification from earlier today.

Dear Lord, Microsoft are fucking experts at TAKE A WORKING FEATURE AND BRAKE IT.

Today I learned that in Unix/Linux or most command lines, when user is asked to choose an option as [Y/n], the uppercase one signifies the default.

I thought they made it a little harder as a security feature to prevent accidental keypress, and I’m shift+Y ing this for the last eight freaking years!!!!! Every time!

I worked on a feature that included setting a cookie to expire in an hour.

QA: The cookie’s time should be set to my local time.

Me: What the—are you kidding me?!The cookie’s exp time is in UTC. Whether you’re in NY or Singapore, that cookie will expire an hour from when it’s issued. Now stop flagging non issues and beta accept my ticket.

This is the weirdest s*** QA has pulled.

Looking at git blame, I think I broke a feature 8 months ago. Not obviously broken, just one of the data fields is empty in one of our calculations.

I don't know if it's better or worse that nobody noticed...

@dfox just noticed a bug (or is it a feature?)

If you happen to double tap a rant slow enough that it doesn't +1 it. But fast enough that the rant view isn't opening yet it seems to register two single tap events and opens two views, needing to go back twice do return to the feed.

Not sure if that's important enough to report as a bug. :)

Ps: I'm on a LG G4, android 6.0

You know what really grinds my gears? When new employees start shouting out suggestions of what feature we should do.. and how stupid this/that thing now.. or how slow that page is.. or how there's a bug somewhere.

WHAT WOULD'VE WE DONE WITHOUT YOUR OPINION?! thank you so much!!!

+10 points if their job has nothing to do with product or development

SHUT. THE. FUCK. UP
please!!!

Feature request - auto play gif

It would be really awesome if the gif would play automatically and not by clicking on the rant's gif.

Of course we can keep a setting option to keep it on or off. What do you guys think?

-Is it a bug or feature?
-No.

!rant (kind of)

I have the bad habit of suggesting "awesome" and "cool" features for projects and stuffs.. (Mostly just for fun and won't give a lot of value to the project, but would be cool). The less fun side.. I'm the only developer (in most cases..)

Me: Hey, wouldn't it be cool if the user could do this or that, or if this was implemented etc.. ?

Boss/Leader: Oh, hehe yeah, hmm.. *thinking* [a bit later] .. You're right, go ahead, implement that feature..

Me: .. Damnit..

But hey, on the bright side.. It's an extra feature! :D

Last week's Android development time breakdown:

21.9% Managing state
17.7% Referring to lifecycle diagrams
15.1% Waiting for Gradle
8.5% Reading the official docs on how to use component x
8.4% Reordering auto-generated ConstraintLayout XML
7.5% Swearing
4.2% Googling “Stack overflow component x is deprecated”
3.9% Googling “Stack overflow implement component x on API 24 or lower”
3.7% Googling “Stack overflow implement component x on API 21 or lower”
3.2% Googling “Stack overflow implement component x on API 19 or lower”
2.9% Googling “Stack overflow callback y called twice”, realising its a feature and not a bug, swearing a lot
2.0% Checking if Flutter is mature yet
1.0% Implementing business logic

Fuck GoDaddy man... Paid extra for the privacy feature thinking I wouldn't get harassed by phone. Think again! Got tons of calls from India in two days. What a rip off...

I guess they're selling our info or something...

What service do you guys use? I want to move my domains, any recommendation?

Best: give him a GitHub repo and tell him to add a feature or change something

Worst: What are your greatest strengths and weaknesses?

I'm playing nowadays NFS Rivals, where I can be a racer or a cop. There's this fucking bug/feature that drives me crazy, so basically when I'm a racer, I'm a target for cops even if I'm just laying around, not racing nor crashing into things. My fucking mere existence triggers them.
Fuck you EA.

I think a "follow" or "add friend" feature here on devRant might be good (+direct messaging) 😆

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.

So the juniors finished a feature and it's okay, it passed all tests.

Now I'm cleaning their code and... I opened up a whole file with trash code that is either repetitive, or not even used. I decided to save it in case it breaks one of the features but... nope, everything seems to be running perfectly with just half of the code they wrote.

WhatsApp and Telegram should consider a feature to disable voice messages from all contacts or all contacts but close friends.

I'm getting tired of getting tech support requests from acquaintances I haven't hung out with in years but when these are too lazy even to type and I have to take type and listen to their muttered voice notes I get crazy

When sales starts selling a "concept" feature to a client because someone showed them a mockup of it in Photoshop. They say "don't worry they know it's going to take a month or two". A week later .. When are we getting that feature? 😑

Got a mathematics library I develop and maintain. Someone filed a feature request ticket for matrices of matrices. As in, each value of the primary matrix is another matrix. Not understanding why anyone would need such a convoluted concept, I asked for clarification.

Response: "This piece of shit library isn't feature complete without it, now stop being a lazy fag in your mother's basement and actually do something"

Lololololol. Sure thing. Let me go waste two or more weeks of my life developing something i've never seen used in math, without any justification beyond "feature".

// Feature Request START
Is it possible we can have some kind of markdown on posts and comments? Maybe not bold or italic, but because of the target of the app, some kind of one-line and multi-line code blocks that highlight from other text (for example: having a gray background, using a consolas font, etc)
// Feature Request END

Linkedin/Jura/Monster/[other job finding websites] should add a feature:
A button that reads "lying mofo or dumbass" on each job ad.

For those employers and recruiters who don't understand that neither a senior role nor any role that requires a PhD is classified as an "entry level".

Unfortunately there are so many such dumbfucks I can't blacklist all of them from my job search. 🤬

Is it a bug or a feature?

So a few weeks ago I wiped my MacBook Pro to regain some space and speed, it wasn't really that slow I just had the disk partitioned into two installments of MacOS. When I erased the disk I thought the secure thing to do would be to set the format to journaled, encrypted rather than just journaled. Everything was working fine, there seemed to be this weird step of login when I restarted but whatever, except iCloud Drive. On my iMac it works fine but for whatever reason my MacBook Pro doesn't want to download custom folders (ones that aren't created by an app and don't have an app icon on folder icon) from my account despite them being clearly available in iCloud.com. So after this much time of messing with it I'm wiping my MacBook Pro again and formatting it as journaled (not encrypted). Wish me luck...

When you estimate development time for a feature and management asks: "But aren't there widgets or sth that you can... [you raise an eyebrow] like... drag and drop or something...?"

(1) Datetimes. Seriously, fuck 'em.

(2) Everybody always thinking: Come on, that little feature is so simple. It couldn't possibly take a whole week to develop.

(3) Nobody really caring or understanding or forgetting after you've told them that if you cut corners and do something the dirty way, it adds to the effort and time needed to maintain or build new features.

I emailed a client with a question if they want option A or option B for specific feature. I got a one word response. "yes."

Witch one should I implement?

is this a bug or a feature?

I just want to make it clear for all the PMs out there...

If you don't put it in a fucking ticket, or don't mention a feature you want in a ticket, I will not do the work or forget put something into a feature.

Write that bitch up if you want it done.

Thank you unity, for not having an undo feature for files or something lice a recycle bin. You nailed it. You made this days work go wasted

Idk if anyone’s said this before, but it’d be a nice feature if we could swipe from the left or right of the screen to go to the last or next rant

Apple please... I just love physical keys, and you just make a pointless touchbar...

I really don't know the position of a macbook pro. I guess mainly graphic designer or programmer will buy macbook pro, and the touch bar feature is a completely pointless to us.

Not to mention that you replace all the USB port to a really "popular type C USB"

Does your team also tend to get stuck in the MVP Trap?

You ship a barebones version of a feature. Zero polish. That’ll be done later if it’s successful.

When the stats roll in it seems the feature got a lukewarm reception. A few users liked it, but it wasn’t a hit.

Next sprint starts and everyone asks if we should spend more time on it

The PM argues ”Why would we spend time polishing something no one uses?”

The designer argues ”Well of course no one used it, it looks like shit, we gotta spend some time polishing it!”

It becomes a chicken or the egg scenario.

Your product ends up with a bunch of half assed features. not bad enough to remove, not good enough to spend more time on.

This picture represents a whole lot of things for me in software development when it comes to bad design or security... You add a new feature along the way and it seems to work well - but basically you f-ed everything up.

I have a minor feature request for the android app.

I would love to swipe down to refresh the current view. The reason for this is that sometimes my Internet connection isn't great and a rant does not load (or any other page).

It makes the app feel slightly gimmicky while a simple refresh would suffice.

@dfox

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.

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.

Not planning ahead, just start at some point, adding just a tiny little feature after another, and then wondering why your to do app (just to check out a new framework or language) suddenly comes with Blockchain, a chatbot and a machine learning algorithm that (slowly) learns when the best time to show random cat videos is...

My new favourite commit message:

"All changes as of 18th Sept"

How tremendously useful? There I was looking to know what changes were made to enable a feature / service, thought I could look for that in the commit message, but no you've given me a much more efficient way of finding out.

I simply need to download the contents of your memory, find out what date you made a change, and then dig through the massive commit to find the piece of info I need.

Forget experience using Git features, managing merges, following Git flow, or even any other SCM ... how can people be so tick when it comes to recording what they've done.

Heres a little cheat sheet for those struggling:

- Commit message
Describe what you actually ****ing did. Don't tell me the date or the time, thankfully Git records those. Don't tell me the day of the week, if I need to know I can figure that out, just tell me what ... you ... did.

- Feature branch names
Now this is a tricky one. You might be surprised to know that this isn't in fact suppose to be whatever random adjective or noun popped into your head ... I know, I too was shocked. The purpose of this is to let other people know what new feature is being worked on in this branch.

- Reusing feature branches
Now I know you started it to add some unit tests, and naming it "testing" is sort of ok. But its actually not ok to name it testing when you add 3 unit tests ... then rip out and replace 60% of the business logic. Perhaps it would have been wiser to create a new feature branch, given you are now working on a new feature.

Rust: Unclear error output is seen as a compiler bug.
Me: 👏

SSIS & SQL Server: Unclear or absent error output is seen as an enterprise feature. It's so mature!
Me: 😩

Updated windows 10, was a feature update or something

Reboot and can't boot into Debian, grub error

oopsies

we had a front-end dev that needs to "re-architecure" his codes when we need to add a small change or a feature.
and im like: wtf is wrong with your code and you need to re-architect it every damn time?!

PS: that dev is no longer with us now. thank god.

Agree or disagree?

My friend said programming for fun is ludicrous... I program for fun...

Actually I was planning to use my comic reader I wrote but ended up spending half the night adding a feature to it....

Okay, we fucking get it guys, you wish that you'd get changelogs with every app update and they'd tell you everything and blah blah blah.
Fuck off
We're the only people who even check, it's not worth the effort. Unless a major feature was added or a well known bug was fixed, the "fixed bugs" is more than enough for the general public.

I don't know the current total number of daily active users and rants counts on devRant. But maybe it would be nice to have a group tagged/mentioned feature. Or something similar. Or subscription to a tag?

Like for example, when it comes to security and privacy and google-free-life all of us usually mentioned linuxxx and the gang. When it comes to server, if I'm not wrong Linux and electrical hardwares for Condor, etc.

But there might be (should be) other who should be mentioned and who would want to get mentioned as well.

Might be fun as well. All those Raven and clans can communicate easily with such feature.

Thoughts anyone? If I got positive responses here, I'll open a feature request on GitHub 🤔

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

When you work with other developers who would, for any feature, small or large, plop in a new library or framework of which they will utilize 1% of... I'm talking about things that we could develop in house in less than a day and have significantly less code bloat... and when you tell them this they smile, nod, and say yeah gotchu, and continue on... AND YOU HAVE TO MAINTAIN THE DAMN THING.

Why the f*** do people add their BD on LinkedIn??? Who wants to know when a f**** recruiter gets another year older??? If I am close to you I will know or have you on FB.... WTF, who anyway had the idea that would be a good feature to add???

Mozilla will update the browser to DNS-over-HTTPS security feature to all Firefox users in the U.S. by default in the coming weeks.

According to the report of TechCrunch : Whenever you visit a website ; even if it's HTTPS enabled, the DNS query that converts the web address into an IP address that computers can read is usually unencrypted. DNS-over-HTTPS or DoH encrypts the request so that it can not be intercepted or hijacked in order to send a user to a malicious site. These unencrypted DNS queries can also be used to snoop on which websites a user visits. The feature relies on sending DNS queries to third-party providers such as Cloudflare and NextDNS which will have their DoH offering into Firefox and will process DoH queries. Mozilla also said it plans to expand to other DoH providers and regions.

When a complaint form doesn't work on a website..
Is that a bug or a feature?

Oh and the online chat is a bot.

Coming to the end of a project and set up Wunderlist to do a snag list whilst testing, decided to involve my client, which worked out great initially but now they started adding features to it. Now in a situation of explaining that feature additions at this stage require a proper functional spec and costing as they may mean a rewrite of existing code and could derail the project. Are all clients dim or just mine?

Read it online today
"Hello Google,
You have made great maps. If you could only add one little extra feature which would tell if we should go on the flyover or beside it. How could a man see a half a milimeter deflection on a 5 inch screen.

Your's Truly
A guy who had to take a UTurn after going 2km more"

Windows updated yesterday and so I have a black screen.

Idk if it's a feature or bug. Linux still works

Client: "When will feature X be ready? How much time to you need?"

Me: "Well, considering the size of the feature it will probable ta..."

Client: "You have exactly 8 minutes to finish or I'll throw a tantrum."

A bit exaggerated, but it pretty much sums up my job.

"We are the great decision makers. We have come to a final answer. We have decided that you must implement this feature using the one way everybody agreed was the worst. The great decision makers will now go slumber for 200 years to leave this decision in your hands. Use our words wisely, or you will not have success in your career."

Devs! Heard about this thing called going to sleep without dreaming about ways to fix a bug?

Whenever I force myself to sleep whenever I get stuck on a bug or confused about the implementation of a feature and started dreaming about the approaches I can take. Most of the time I wake up around 2 or 3 am to try out an idea I had and most of the time it works.
Now I fear this is becoming a habit. Is it something I worry about or ignore since my problem is getting solved?

Started with some inspiration for making a 2d MMORPG.
These are how i make the world generator:
Decide you want to generate paths/roads.
Realize you need pathfinding function.
Realize you totally forgot how astar pathfinding works.
Search for implementation.
End up getting bored and implement other cool feature instead.
I literally made a bunch of stuff before writing a 20 or so lines long astar cause its boring.

Weekly Q: How do you keep yourself motivated?
A: No matter what - I allocate a little bit of time every week to something I really care about right now.

When I was green it was mostly learning. Now it's mostly codebase cleanup, dev experience improvement or dabbling with some feature that's not prio.

Might not sound like a lot but doing it weekly does add up.

A colleague came to me ranting about some feature marketing wants.
"Save whether the user accepted, rejected or ignored the TOS." They have to accept the privacy agreement first, so this feature is most likely about annoying users who rejected the TOS. Totally justified. Fuck that marketing team.

I've been writing tests all week.
I quite like writing tests in some respects, but I absolutely detest it if the thing I'm testing is a moving target! Stop changing your mind! Either we support the feature in it's entirety or we don't support it at all!

I find it funny that, one of the most expected features on Windows, is not even a Windows feature. The teams at Microsoft must be feeling the same way we feel when, after a huge project, the client gets super excited when we implement or change something really, really small, that we did in a couple hours, just for fun.

!$rant

Hmm.. I kinda want to add a terminal type feature to my portfolio project that let's you type commands to navigate the site or change some options. I could still keep the standard navigation elements for the people who get mini heart attacks when they even see a terminal xD

Wouldn't it be cool if you could add your favorite ranters as "friends" or something like that?
I also would welcome some feature like a personal chat personal with other ranters.
Just a few ideas.

If a frontend dev asks for screens, mocks, designs or whatever, all the company pushes for it and gives it to them, but if a backend dev asks for a set of input/output samples for a feature, the same people claim "its so hard to think about the cases"... Wtf are they thinking?

@dfox
No Loading window on Supporters and About us pages.
Or is it a feature for impatient persons like me??

I might have just git-committed the cardinal developer sin: not multiplying estimates by 3. Torvalds help me!

So a php app I developed a few months ago when I was first starting as a dev needs an upgrade. Pretty simple since I've known about said upgrade for a while, but the feature was never needed until today.

Told my boss it would take a day or two of refactoring and additions for it to work.

How screwed am I?

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

So I see this code:

class ViewWithDisplayLayer {
func viewDisplayLayer() -> CALayer? {
FatalErrorMustOverride()
return nil
}
}

If only Swift bad some way of defining some sort of interface or protocol with methods to be implemented by a class without using class inheritance and wouldn't it be great if that feature also gave a compile time error if you forgot to override/implement said method(s). If only.....

😳

My boss uses agile development so he doesn't has to think about use cases he wants to be covered by the application.

He's just throwing in a "design" (an image that is probably created with Paint) without any further specifications and inconsistent elements, let the developer work two days on it, see the outcome, complains why it's not how he wanted it to be and then starts thinking how the feature should be integrated in the app and notices that his "requirements" from the image could not provide any advantage or usage at all for the user of the application. Asking for clarification before starting to work just leads to spongy statements or silence when he notices that he didn't think through to the end.

Sad is that this has not happened only once but is usually the way a new feature is developed...

There should be dev equivalent to the expression "tip of my tongue". You know, when you're trying to implement a feature or fix a bug and you have a fuzzy idea of how to do it and only missing the final piece to put all of it together.

Boss tells me every other week to "set focus" on a completely different topic without loosing a word on the "top priority" the day before. Or he asks for the other (not finished) feature to be ready "in the next few" days/hours.

Yeah. A real sunbeam in dark times.

I was too concerned whether or not I should extend a feature, that I forgot to check if I could do so.

Now I've shot myself in the foot by breaking half of the feature and my only solution to make this work out as intented are quite ugly.

10/10 would do so again. Programming like a retard is the way hobby projects are meant to be. Best learning experience you could hope for.

Also, bless git for giving me a second chance in case I've gone full retard mode.

So I've spent the past 2 months or so integrating a payments provider with a terrible API, only to find that the provider is missing a core feature that they claimed to have in their sales pitch. I have no idea what will become of a large part of my work, it's so draining to work around a total garbage API

This is going to be fun. We are switching our phone system to use Zoom and the turn on date is sometime in October (couple of weeks away). I have a feature I'm working on (automated phone calls) that the salesman said was fully functional (jump through a hoop, stand on your head, turn around three times, type of functional). Tried the steps they gave me, got to #3 and there is no virtual agent API call I can find to hand off/transfer the call. Send our contact at Zoom some questions, responds "That is a feature we might put in a future product. Can't do that right now." WTF?!
Other developers are running into similar "How do we get there from here?" issues that features promised, either don't exist or don't work.

One feature in particular I'm receiving a 403 permission denied error.
K: "Feature X needs to be enabled."
Me: "It is."
<send a screenshot showing the feature enabled>
K: "Your account doesn't have permissions. Have the sysadmin elevate you authentication level."
Me: "I'm an admin"
<send a screenshot showing my admin status>
K: "I'll have to get back with you."

Its been 3 days and no update on my ticket. *sigh*

!rant
Hmm... so I was thinking...
What if devRant implemented a feature that lets you get rants into some kind of list, accessible via your profile? Kind of like the "Watch later" list on YouTube, or playlists. I know we have a "Favourites" list of rants, already, on devRant, but being organized about this might be a good idea.

What do you think?

Uhmm... anyone having the same picture Problem on devrant.io when using your mobile in landscape mode?

making a messaging app, can you guys name a feature that would be cool that you would like to have, one you must have and/or one that you would like to see in the messaging app you use?

Is it just me or does anyone else hate the "MORE RANTS" feature/option of Devrant.
Can't we simply have a scrolling featuring with never-ending set of Rants the same way as reddit does??
:( :( :(

I hate when companies use "hackable" as a feature. Pal, if my product was hackable I'd fix it ASAP.

They should just use customisable or something like that.

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)

Can someone relate to it? We have a very simple process:
1. Create a ticket 🎫
2. Specify the requirement 📑
3. Assign the ticket to a developer 👨‍🦰👩‍🦰
4. Optional: make a meeting with the developer and go throw the specification if it is a complex feature 🗓️

Under pressure it looks like this:
Someone tells you to implement the request as fast a possible, no written specification, in best case you get a brief email 📧 also the feature has to be available asap in production and they is only poorly tested...
Or they want to test in production because the data in test system is "missing" ⛔☢️☣️

It is so annoying that is so difficult to stick to such a simple process 😭 it really freaks me out 😒😫

Feature request: copy text on double tap or hold on Android. Wanted to save a few quotes, but not as a screenshot... Just an idea :)

Why the fuck is debit cards that don't need a PIN for transactions even a thing? What is so difficult to understand or implement in a two factor authentication? Like do these companies have meetings where some fucktard proposes removing a crucial security feature and the others just nod approval?

Do telephone conferences count ? Where you have to talk to 18 guys in the big meeting room via phone explaining a feature - never know who's talking to you or all talk at the same time and you can't understand a single word because of the crappy connection or the echo of death. Same rules apply to video conferences as well plus jerky pictures.

Oh the joy of enterprise software development in a legacy system. I just wanted to add a new checkbox with a small feature and now I'm balls deep in age old half decent documentation and just have to pray it works. Implementation time: about 2 days or so

The tags disappear from your drafts.
Anyone else experiencing this ?

Also I can't scroll through the tag suggestions.

Is it a bug or a feature ? @dfox
(This still happens even after updating the Android App)

I'm using a Lenovo device with Android M.

FML, somebody here or somewhere wrote that al customers lie..

Just been a witnes to that.. Over skype (mind I reminded them to write to jira on several occasions so others can help if I am out of office) feature xy is not working.. I log in to server, I see no logs of person a doing anything with our system, let alone use the xy feature... Well duh, of course it doesn't work, it's not a freakin mind reader.. :/

Next time no help, no log checking, no nothing until they provide ss of what exactly they were doing.. :/ Fuuuuu....

Dashlane is the worst password manager to use. I was trying to set up categories and since it does not have a simple selection box change feature I had to grab almost 100 at a time to change. Unfortunately after changing them I realized I had a duplicate and I clicked on that one to delete it. The system was still selecting all 100 (it uses a slightly gray color to show what is selected rather than a clear check box type feature) and it deleted all 100 passwords. It never asked me a question or gave me an undo feature. The interface is very difficult to handle.

Further, to set up a second user and grant them access to a large number of passwords (in this case my wife I wanted to give her access to 128 passwords), you must click them one at a time and then when you set it up they cannot get their own master password. Very cumbersome.

when viewing a profile and scrolled down enough to hide the avatar and the user description, it does not show up back again when scrolled up... is it a bug or a feature? 😂 @dfox

Does that look like a bug ? Or a feature ? It requires a considerable amount of time and effort to develop unattended remote access. How do these people develop such a feature as "mistake".

When working as a full-time developer
TGIF!, Its already 6 hours? YES!

Working freelance or on your side-project
TFIG?! What TGIF. This feature took 6 hours? FML.

@dfox I reccomend adding on devrant a thing calles hide read or similar feature. When I browse devrant there are times most of my feed is stuff I already saw. I want to be able to filter it. A good app that uses well the feature "Hide Read" is Sync for Reddit. Thx!(　^ω^)

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%

!rant
Bug (or feature ?) report
I don't know if it's a bug, a feature, and something that just happens to me.. When I view someone's profile and I want to scroll down to see the rants, the "first scroll" stops at the end of the profile. Then I can scroll down more. And after, if I want to see the profile again I can't scroll up. I ended up finding out that tapping the username lets us see the profile again. I'd like to point this out because the behavior seems kinda weird to me, I don't know what others think about it

This week I delivered a big feature (took me about 2 weeks), QAs tested it yesterday results in about 10 Jira issues. When looking at these 8 was fake issues (QAs forgot to configure some stuffs) and 2 was feature requests. I feel some stress, I'm not sure it's a great success or I should test myself to see if there is really no problem :D

This fucking company man. Implementing a simple feature (just a couple settings in the android app) is taking me 4 fucking weeks(feature was done long time ago, but not in the way that. they wanted, even though I followed existing implementations). I have like 60 comments in my code review from which half feels like it's just purely nitpicking. I already have 2.5 years experience and I just want to kill myself or quit the job if every code review here willl be like this.

Having no way to clear application data from an ios app means that I either have to uninstall and reinstall it EVERY TIME I make changes to stored data processes, or I have to build in a whole separate feature to handle clearing the data.

In Android, it's part of the OS.

Why again is ios considered so great?

Is it a Bug or a Feature?
Why am I seeing all the ++ scores in Binary?

(I Checked, those are up votes in Binary)

Devs are you drunk? Or is it April fools?

EDIT : steps to reproduce
1.open devrant app
2.click on any rant that appears in the feed

feature request / rant: there sbkukd be no posting new rants unless you have a minimum amount of +1. Maybe it's 10, or 25. but I've noticed the vast majority of people posting repeated memes, gifs, and overall irrelevant stuff are people with 0-5 +1. they should be required to post comments and be around for a bit to understand what devrant is before clogging up the feed.

What's your git style? Commit many times as a sort of change tracker/backup regardless of feature completeness or functionality, or only when something is complete and passes tests?

Today, for a feature that doesn't need to be released at all, we had to choose between delivering 2 months later so we could pay the technical debt, or release on time with even more technical debt, and 96% sure this will kill the project.

Guess what?

Hot take:

Want to bloat the shit out of your product and want to lose the core USP?

Want to stop solving the problem you set out to address?

HIRE A PRODUCT MANAGER.

PMs are expert at shit show. We fuck up everything.

God I hate my profession.

When I start my company, the mandatory rule for every PM will be that if you want to add or enhance a feature, they will have to remove a feature. Whoever fails to do so will be punished by having to clean up the code base and work in sales for a quarter.

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.....

PM: Can you help out writing a test suite for feature X? Really high priority!
Me: Ok, give me a day or so.

I get it done, and setup in CI-tool to test on the feature branch.

*Next day*

PM: It doesn't work! Can you have a look?
Me: Uhm yeah.
Only broken on feature branch of course.

Dev working on feature X: Ok pushed a potential fix, can you run test suite again?
PM: Yes, can you get on that asap?

CAN YOU RUN YOUR OWN FUCKING TESTS?

(╯°□°)╯︵ ┻━┻

Feature request
Could we have some kind of way to see who created the post in the comments? Like an OP mark or a different color of the name or something?
When reading long quality rants I tend not to notice the username, and then when I'd like to engage in the discussion I have to scroll all the way up to check it.

No QA Steve I will not insert a massive feature into the project no matter how high of an importance you deem it or how awesome you think it is.

Holy shit. I'm on the devrant app and I just noticed that the scrollbar on the right does this weird worm thingy.

As I scroll up and down, the scrollbar size keeps changing. It's a cool effect where it twitches like a worm.

Is that an android o feature or something or did @dfox or @trogus add that shet.

I see why dfox chose to hide downvotes...

My reaction: why the fuck would anyone even bother to downvote ...?

But now I have a dilemma.... do I keep this feature or not? I kinda get a tingly feeling being able to know how many ppl hate a post.... WTF right?

!rant (Feature idea)

Rant Rooms!

Each room has a topic as it's title, and this room acts like a group chat. Individuals can join public rooms and rant about the specified topic. Or, private rooms can be created and the creator can invite people to this room.

Perhaps timeouts could be set so that after a specified amount of time without activity, the room expires and disappears.

Probably a shit idea but figured I'd mention it 😂

I recently got a job as a web developer, they want me to add a feature in a particular website, i wasnt able to finish it so i decide to bring it at home , but i didnt even wrote a single line of code, i think im lacking motivation or just a deadline

Yesterday whole 12 hours we were working on deployment about a feature X that has deadline yesterday itself.
Everything damn perfectly running on Test env but not on Prod.
We made Prod into Dev/Test/Fucking garabage env. Haha.
I was laughing to myself at same time crying hard in my deep heart.

Business guys chasing PM
PM chasing us
And from morning till night we were in same room. Had lunch, and dinner only went out for toilet and to refil water bottles.

And found that feature Y is not working at same time that is related to our feature X. Fucking we have been wasted hours on it.

One of my devs got so fucked up emotionally that he messed up the code (not his fault) he didnt had his lunch and dinner. Had to console him later that its not his fault. Poor guy not sure whether he slept or not; will find out in few hours.

Anyways reported a bug.
But that bug assigned to us for fixing.
Are you fucking kidding me.
Anyways no choice. Had to do it.
Hope today everything goes good or horribly bad. FYI no deployments on Friday damn we are in stalememt till Monday.

Fuck that bug
Or
May be fuck our stupiditiy while makiing mistakes.

Off late I've been having a lot of debate with my friend about using Flask over Django for prototyping some feature. I side with Flask, since the development time is much lesser than Django and doesn't need to follow a lot of rules.

Issue here is, I prefer flask and he prefers Django.

Need opinion on this sort of problem, where a prototype for a feature in a product has to be built. It maybe integrated into the end product, which is in Django, or may not be.

@dfox
I recently posted a rant containing the tag "$" (php, you know).

But if I search rants with the search pattern "$", the search returns no results.

I guess this has something todo with $ as a special character ;)

Is it a bug or is it a feature? *g*

Working on a game in Unity for a school project, spent several hours trying to implement a feature... successfully implemented it... only to realize that the feature does something very different than I thought it did.

I thought LoadSceneMode.Additive loaded scenes into memory in the background so I could just switch to them for faster load times... nope, it loads the scenes and just stacks them on top of each other or something like that... Unless I'm still misunderstanding...

Wouldn't call it a feature. More like worst practice. Data manager (and my boss at the time) kept using our website as a way to host large files 3rd party vendors/partners could download instead of using one of the many secure transfer methods out there to send them data. This was sometimes extremely sensitive data. No authentication or security that I could find. I went ballistic on him after seeing that.

today i almost had my first intentional 'fuck it, i declare this bug a feature'-moment. then it suddenly worked. i don't know whether to be happy for it to work or to be annoyed not knowing what the hell happened.

So asked to help out on an extra project that another Dev ( who is a senior developer ) is working on and I go to clone the repo but find 15 or so commit messages on the master branch saying "Work on feature x" (not an actual x). This is going to be fun...

Writing code for software that was deprecated since 2015 it's a nightmare. More when the unit tests take way more time than the actual fix or feature. Just kill it with fire

I hate reactive management.

It's when your boss instills fake urgency every time a client asks for something close to impossible, or <x> competitor is doing something in a different way he deems the best.

Everything must be dropped, the sprint put on hold, fuck requirements, everybody has to do overtime, why are you not contributing?, why are you going home when you have to?, fuck do I care you have a 1 hour commute - this <y> thing has to be made by sunrise tomorrow or it's a showstopper.

And it's never a showstopper. 90% of the time the feature gets dropped one-two months down the line.

If I fork a repo should I create a feature branch from master or develop ?

Crying right now. Tldr, feature demanded, never used. 8 months ago, bosses demand two features. Disable sync of products they choose and set a reserve quantity on products they choose. Code is done and in production, but the only time that choice has ever run is in testing. With over 10,000 products, not one has ever had sync disabled, or a reserve quantity !=0. I need a new job.

Came across a new definition of the word "Implemented" in work today. As far as I can tell, it can be most accurately explained as:

When 1 or more people think about the feature and record a thought about it, without actually delivering anything.

Whenever you change your Instagram username it becomes unavailable completely even tho it's not taken. Not possible to get it back after changing.

Not sure if this a bug or a feature that they intended to have in their app...

is it necessary to have cherry picking a part of git branching/release process?

we have 3 branches : develop, release and master.

currently every dev works on feature as follows : they make a branch out of develop, write code, raise pr against develop, get it reviewed and merge back to develop. later the release feature list is generated, and we cherry pick all the release related commits to release branch, and make a prod build out of release branch. finally, the code is moved to master and rags are generated accordingly.

so the major issue with this process is feature blocking. as of now, i have identified 4 scenarios where a feature should not be released :

1. parallel team blocker : say i created a feature x for android that is supposed to go in release 1.2.1 . i got it merged to develop and it will be cherry picked to release on relase day. but on release day it is observed that feature x was not completed by the ios dev and therefore we cannot ship it for android alone.

2. backend blocker : same as above scenario, but instead of ios, this time its the backend which hasn't beem created for the feature x

3. qa blocker : when we create a feature and merge it to develop, we keep on giving builds from develop branch adter every few days. however it could be possible that qa are not able to test it all and on release day, will declare thaf these features cannot be tested and should not be moved to release

4. pm blocker: basically a pm will add all the tickets for sprint in the jira board. but which tickets should be released are decided at the very late days of sprint. so a lot of tasks get merged to develop which are not supposed to go.

so there's the problem. cherry picking is being a major part of release process and i am not liking it. we do squash and merges, so cherry picking is relatively easy, but it still feels a lot riskier.

for 1 and 2 , we sometimes do mute releases : put code in release but comment out all the activation code blocks . but if something is not qa tested or rejected by pm, we can't do a mute release.

what do you folks suggest?

So far, the largest hurdle for myself is realising that most people don't understand the struggle sometimes towards getting a feature implemented, or a bug squashed. In the end, it's all about the end product.

What a fucking boring day.

I had a heated argument with a fellow colleague because he wants us to add a feature to a certain product for free. He thinks am so money minded as I was pressuring him to charge the feature but he's defending himself that we are just a start-up.

Am left wondering if I was wrong or if giving free stuff will pay our bills or should start-ups code some stuff for free.....

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.

It would seem that "code freeze" has become a meaningless term to our systems engineering team. Sure we can sneak in another feature or eight that you felt it beneath you to negotiate on time. That you couldn't make the decision on until now, even though your job is to make these decisions so that we can stay on schedule. This is why systems is a fucking year behind.

I noticed a bug on devrant app on Android. Or is it a feature? Haha.

When you comment on a rant and then press Modify to change your comment, when you edit and save the edited comment you get to the updated one. If you press back you get to the previous one (not updated comment). If you try to reopen the rant you commented you see only the updated one.

So....here's a bug. What do I win?

For our product there is a common type of bug we get reported. It is not really a bug, also it is not a feature - instead it is a missing or incomplete feature.

For example to help users we add a search feature on one screen, but there is no search on some other screen. Now the absence of search on that screen is apparently a bug.

To make things worse to report the bug users try to trick us. They say something like:
"Hey can you help me? How can I find things in the abc screen?"

So I explain how to browse for the item or whatever.

Then they say:
"Ok now how do you do that on the xyz screen?"

Slightly suspiciously I now tell them how you can browse for the item like before or we have this new feature eg. search you can use if that is quicker.

Now they say:
"Don't you think it would be better to have that search on the first screen?"

OK now I realize this is just a trick and the person doesn't actually need help using the software. So I tell him how we only added the feature on one screen and if he thinks there is value adding it on other screens he can put enhancement request in and if wants he can talk to my boss about making it a priority.

Then they go on asking other rhetorical questions like:
"why was it designed like this?"
"Are you guys deliberately trying to make life harder for people by making them learn different ways to do things?"

I now want to delete the new search feature but luckily it is close to lunch time so I have a good excuse to escape the conversation.

Sometimes I wonder why Skype developers think it is okay to download files to a specific directory without an option to select a location at the point of download. Or is this yet another premium feature?

Question: How do you guys charge your clients? I have had an hourly rate for quite sometime now, but never have I been able to use it since I do not know how to calculate it.

What I usually do is charge a fixed fee and charge on top of a feature is requested,
or I charge a monthly fee for long term contacts and charge on top if any additional feature is requested.

I want to try out hourly charge but since most of my clients are online, I do not know how it will work since the client can believe that I am simply adding additional hours or delaying work causing the hours to increase. (Most online clients are new to my services, unlike clients I meet offline, online can be less trusting)

Question:
My application (web app & mobile app) needs to interface with a users email to read mails for further processing

Is there are library (py, js) or service that I can leverage that abstracts the access to the mail servers (IMAP, POP3, Exchange, Google API, Outlook API etc.) and provides a single interface (possibly REST API) to access the mails?

It feels redundant to implement each of the above methods of email access, as I see it being a feature in many applications out there, but I am not able to find a library or service that provides it.

Any advice or suggestions with implementing each of them is also welcomed

Thanks in advance

Explain why a feature or request is a shite idea to your manager but don't accept 'well that's what the client wants' as an answer. Insist the useless manager twat should earn his money and not ruin the project.

Is there anything like a reverse search engine, that let's you enter e.g. some js code and it tells you what language feature has been used? Imagine you see syntax you've never used before and don't know what it's called or what it does but would like to know more about it.

I wonder how many github issues have been closed by asking the author to implement the feature they've requested for. In the past, I was confident my issue will be resolved by opening a new one when there's no answer in earlier questions. I can't tell whether the nature of my questions advanced or whether it's a new trend. But I've opened maybe 4/5 issues in recent memory, and each time, the collaborators suggest the feature is one I should contribute to their project by implementing. Isn't this their job as maintainers? I'm already working on something that barely gives me breathing space. I encountered a challenge using your library, and your idea of helping is that I dissent from my own trajectory, acquaint with your project /how to implement what I want, wait for it to get merged etc, before continue what I originally intended. Do they think that's worth it?

Is it just me or is this a common occurrence, lately?

Without diving into OO or "Micro$oft", I think the one major flaw in C# is the ability to use "regions".

It's like a feature that was specifically designed to hide shitty code.

If you know how to separate your logic properly and focus on good design principles, you should never have to use a "region" to "clean up" the way your source looks!