"CRTL + C to shutdown"

Act I

Me (Lead Developer), Boss (Head of IT), CEO

> enter stage left CEO

CEO > "Alright Boss, give it to me straight. Are we going to be able to release app x by this date?"

Boss > "Yup we'll have a beta release on that date"

> exit stage right CEO

Me > types long email to Boss outlining exactly why we won't be able to release app x anywhere near that date, beta or otherwise, because:
1. We have a development team of 2
2. I've never developed an iOS app before
3. Developer 2 is still trying to understand git, because
3a. Developer 2 isn't even a developer (but he's doing iOS front-end so w/e)
4. We don't have the required database systems in place
5. Or CRM
6. Or CPQ
7. We'll need to conduct a security audit

Boss > "yeah, but CEO is gonna need to hear that date a few more times before he can fully understand"

Me > *internally screaming BUT YOU HAVEN'T TOLD HIM THAT AT ALL*
"ok cool just glad we're on the same page on that one"

My morning (RO = remote office):

Me: Your xxx implementation is very strange.
RO: Yes we are following a new example from experts in this field. See this link.

Me: Paragraph 1, use xxx class in these situations. Were not doing that.
RO: Yes we had problems with that, we decided to skip that.

Me: Paragraph 2, always use xxx when accessing data. Were not doing that.
RO: Yes that create many bugs, we skipped that.

Me: This section on debugging says to enable this flag while in development to allow the IDE to alert you to issues.
RO: Yes this causes the app to crash constantly. So we took it out.
Me: ... because its finding issues ... and telling you where the problem is, with an error message.

... your not following the experts at all.

RO: We are!, please read the link we provided.

... this will be discussed on my exit interview

Worst fight I've had with a co-worker?

Had my share of 'disagreements', but one that seemed like it could have gone to blows was a developer, 'T', that tried to man-splain me how ADO.Net worked with SQLServer.

<T walks into our work area>
T: "Your solution is going to cause a lot of problems in SQLServer"
Me: "No, its not, your solution is worse. For performance, its better to use ADO.Net connection pooling."
T: "NO! Every single transaction is atomic! SQLServer will prioritize the operation thread, making the whole transaction faster than what you're trying to do."
<T goes on and on about threads, made up nonsense about priority queues, on and on>
Me: "No it won't, unless you change something in the connection string, ADO.Net will utilize connection pooling and use the same SPID, even if you explicitly call Close() on the connection. You are just wasting code thinking that works."

T walks over, stands over me (he's about 6.5", 300+ pounds), maybe 6 inches away

T: "I've been doing .net development for over 10 years. I know what I'm doing!"

I turn my chair to face him, look up, cross my arms.

Me: "I know I'm kinda new to this, but let me show you something ..."

<I threw together a C# console app, simple connect, get some data, close the connection>

Me: "I'll fire up SQLProfiler and we can see the actual connection SPID and when sql server closes the SPID....see....the connection to SQLServer is still has an active SPID after I called Close. When I exit the application, SQLServer will drop the SPD....tada...see?"
T: "Wha...what is that...SQLProfiler? Is that some kind of hacking tool? DBAs should know about that!"
Me: "It's part of the SQLServer client tools, its on everyone's machine, including yours."
T: "Doesn't prove a damn thing! I'm going to do my own experiment and prove my solution works."
Me: "Look forward to seeing what you come up with ... and you haven't been doing .net for 10 years. I was part of the team that reviewed your resume when you were hired. You're going to have to try that on someone else."

About 10 seconds later I hear him from across the room slam his keyboard on his desk.

100% sure he would have kicked my ass, but that day I let him know his bully tactics worked on some, but wouldn't work on me.

Do you ever open devRant, read a little, and then exit the app to find something else to do. Then open the app immediately again, because that's what you do when you want something to do?

Type 'exit 'on any messaging app to close it.

Been really depressed at work for the last two years. To the point where myself and colleagues would constantly petition our boss to work with us to change our internal process.

After being constantly ignored / seeing no really impact ( he literally renamed a step in our process and said he fixed it forgoing all the recommendations that we suggested and refusing to discuss anything with us );

I decided to resign before I say or do anything to completely burn the bridge.

Two days later one of my colleagues also resigned ( the only other device at the company ) now my boss is frantically looking for our replacements while also trying to maintain that he holds all the cards.. he offered my colleague less than he is on now to freelance for him. And will likely attempt the same with me in my exit interview today.

But I'm working on a web app which I find interesting. Problem is that I'm not as hopeful as the others working on it with me that it will ever make any money. (It seems like a money pit if anything)

I think I may be in for a couple of rough months. But at least I'm not working for a company that made me so depressed that all I would ever think about is how to convince the boss to improve things.

I'm worried but for the first time in 2 years I feel happy.

The Windows taskbar programmer, the steam app programmer and anyone who supports either of them can go fuck themselves.

Look at the exit button, the most used button at the bottom.

Things might be looking up for me.

Saw an opening in a huge company for a dev position. They might consider me, just biding to see what is said.

That being said, today I deal with a user complaining that their app wasn't working. They moaned that exit should rather be close. The text. I raced 60km because you told me it was crucial. Fuck you.

XCode you fucking piece of shit...

So I just wanted to process my ios app to the app store and start the archive process. All of the sudden:
Command CodeSign failed with a nonzero exit code

What? So there is an error and you cannot tell me the error code? All information you give me that it isn't zero!? Wow... Amazing... What a great user experience. Maybe it cannot resolve the error? Maybe it is some external tool Apple has no access to and that is the only valid error they can throw at us?

Oh hell no! It has something to do with the keychain access! But why tell the user? That wouldn't be as much fun as just tell it is a nonzero error, isn't it apple?!

In the end locking and unlocking my key chain solved the problem... Thanks for nothing XCode!

@dfox
There's one thing I hate about devrant...
While I'm browsing posts I can't check back for my posts or exit the app or I'll have to scroll down again (gets messy after like 50)
That means I just stop watching for the rest of the day.
Suggestions:
3rd button to mark as seen and don't show on post lists
Add a mark on last seen post so it will continue there when we return to browsing.
Thank you for this community once again

It’s been a loooong hiatus from devRant but I’m back and still no swipe to exit a rant. Cmon, that shit would make this app easier to navigate.

Me: there seems to be a problem in the Web Sphere app server...I would recommend u change it to weblogic

Client( IT division head of his company): is it compatible with websphere soap..??

Me: soap is generic, websphere is just an app server

Client: no but we have been told to use only websphere soap, is weblogic having that..??

Me: soap is protocol, app server is changeable..

Client: no we want only websphere soap.

Me:....(trying to find the nearest exit)

ok I give up trying to make a screensaver for Linux

I don't even have anything to rant about

just everything I tried didn't work and nothing makes sense

I'm gonna find somewhere to bury my woes

this is so stupid, too. because I can just query the system if it's idle, run my app, and then ask my app to exit if there's any user input. but instead I'm trying to integrate it with the existing screensaver software. which evidently never runs my application for God knows what reason. and I'm tired of reading 100 pages hunting for the answer. where's my arch wiki page for how to make a screensaver =[

Has anyone ever tried to send a message to a rep at PNC on their online banking?

-you can't write any 'special characters' in the message. This includes dashes, slashes, and even apostrophes ("don't" is not allowed!) among others. I guess they just pipe the message right into the SQL queries!

-I had to type a long message there, and I was tired and forgot to do my usual CTRL+A/CTRL+C ritual - BIG MISTAKE!! After clicking submit, I get a JS alert() come up saying that my session timed out after 15 minutes of inactivity (writing a large rant to PNC ofc). Back button does not bring up the filled out form to copy from, as like the whole site seems to be on the same URL. There was no way to exit the alert without losing the message. Thankfully I did not close the tab, and I was able to recover and piece together some of the text snippets using $ gcore / $ strings | less.

Overall this has to have been the worst web app I have dealt with for quite a while.

Does anybody else have the project where every time you try to change something, no matter how small, you always end up screwing it up and needing a bunch more time to fix it just to get back to the starting position?

I have this project I've done, a custom Ambilight system for my TV, and everytime I try to add a feature the lights stop working altogether... Tried adding detection of when I start my media player to automatically start the Ambilight mode (I made several modes, one of which is just shine a certain color all the time which is great if you don't want to use normal lights and want to be able to control the lights from your phone).
I had the code for detecting app start and stop from before when I implemented it for a slightly different system. I just changed the few things that are different and poof, no more lights... I managed to forget the other system checked a flag after every process exit and overrode the mode and I removed the setting of the flag, but not reading of it...
Every single time I do changes on this it's something... Other projects sometimes go smoothly, sometimes not, but this one just doesn't want to be kind to me....
Results are awesome, though :)

My bank's website is the shittiest fucking site in the world. It literally kills my phone, to the point where my browser takes a full 5 minutes to exit.
The latest bug I mean feature they have rolled out interrupts your login with a fullscreen modal which asks if you want the app or to continue on the site.
Well, the fact that I'm in a browser means I've already made up my mind so why don't you go and fuck yourself? And based on the quality of your website, do you really think I want to voluntarily install software that you've sellotaped together onto my device?
Thought not.
Go and fuck yourself you pieces of shit.

What I would like, do I want to start a conversation?
Sorry...

if let url = URL(string: "devrant://") {
let app = UIApplication.shared
if app.canOpenURL(url) {
//safe, Talk to user
} else {
//don’t start a conversation, or stop it now!
exit(0)
}
}

@dfox There's something wrong with bluetooth keyboards in the devrant android app.
1) If you switch from the onscreen keyboard (I'm using Hacker's Keyboard) to a bluetooth one while on the rant/comment editing/posting screen the exit and post buttons become unresponsive. (Pressing the back button on your phone is okay though. If you then reopen the rant it works again)
2) switching back to the onscreen keyboard replaces everyting you've written with the tags ...?

(Android 9)

Every time I want to quit or leave a chat app or some kind of app that uses a text box for input, I try to type 'exit'.

Does anyone else have problems with devRant? Whenever I exit a rant and go back to the 'main window', where the rants are supposed to be listed, I get an empty page (with the typical devRant background but without the loading animation). Rants won't load for me then.

Rants won't load for me except for the first time when I open the app. After I clicked on a rant and go back, it won't load.

Using a OnePlus 3 with Android 7.1.1, in case that matters. :)

Heroku logs be like
2018-07-16T00:05:06.883023+00:00 app[bot.1]: Ready!
2018-07-16T00:05:11.940150+00:00 app[bot.1]: (node:4) UnhandledPromiseRejectionWarning: Error: 410 Gone
2018-07-16T00:05:11.940171+00:00 app[bot.1]: at _response.transport.request.then (/app/node_modules/snekfetch/src/index.js:193:21)
2018-07-16T00:05:11.940173+00:00 app[bot.1]: at <anonymous>
2018-07-16T00:05:11.940175+00:00 app[bot.1]: at process._tickCallback (internal/process/next_tick.js:188:7)
2018-07-16T00:05:11.940248+00:00 app[bot.1]: (node:4) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated
either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
2018-07-16T00:05:11.940340+00:00 app[bot.1]: (node:4) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It's these individually tiny annoyances in products and software that together form a huge annoyance.

For example, it's 2022 and Chromium-based web browsers still interrupt an upload when hitting CTRL+S. This is why competition is important. If there was no Firefox, the only major web browsers would, without exception, have this annoyance, since they're all based on Chrmoium.

I remember Chromium for mobile formerly locking scrolling and zooming of the currently viewed page while the next page was loading. Thankfully, this annoyance was removed.

In 2016, the Samsung camera software was updated to show a "camera has been opened via quick launch" pop-up window when both front and rear sensors of the smartphone were covered while the camera was launched by pressing the home button twice, on the camera software Samsung bundled with their custom version of Android 6. What's more, if that pointless pop-up was closed by tapping the background instead of the tiny "OK" button or not responded to within five seconds, the camera software would exit itself. Needless to say, this defeats the purpose of a quick launch. It denies quick-launching while the phone is in the pocket, and the time necessary to get the phone out could cause moments to be missed.

Another bad camera behaviour Samsung introduced with the camera software bundled with their customized Android 6 was that if it was launched again shortly after exiting or switching to stand-by mode, it would also exit itself again within a few seconds. It could be that the camera app was initially designed around Android 5.0 in 2015 and then not properly adapted to Android 6.0, and some process management behaviour of Android 6.0 causes this behaviour. But whatever causes it, it is annoying and results in moments to not be captured.

Another such annoyance is that some home screen software for smartphones only allows access to its settings by holding a blank spot not occupied by a shortcut. However, if all home screen pages are full, one either needs to create a new page if allowed by the app, or temporarily remove a shortcut to be able to access the settings.

More examples are: Forced smartphone restart when replacing the SIM card, the minimum window size being far too large in some smartphones with multi-windowing functionality, accidental triggering of burst shot mode that can't be deactivated in the camera software, only showing the estimated number of remaining photos if less than 300 and thus a late warning, transition animations that are too slow, screenshots only being captured when holding a button combination for a second rather than immediately, the terminal emulator being inaccessible for the first three minutes after the smartphone has booted, and the sound from an online advertisement video causing pain from being much louder than the playing video.

Any of these annoyances might appear minor individually, but together, they form a major burden on everyday use. Therefore, developers should eliminate annoyances, no matter how minor they might seem.

The same also applies for missing features. The individual removal of a feature might not seem like a big of a deal, but removing dozens of small features accumulates to a significant lack of functionality, undermining the sense of being able to get work done with that product or software when that feature is unexpectedly needed. Examples for a products that pruned lots of functionality from its predecessor is the Samsung Galaxy S6, and newer laptops featuring very few USB ports. Web browsers have removed lots of features as well. Some features can be retrofitted with extensions, but they rely on a third-party developer maintaining compatibility. If many minor-seeming features are removed, users will repeatedly hit "sorry, this product/software can not do that anymore" moments.