I just got my first open source pull request merged for a library I use!

Last month we fired our worst client. I just received a friend request from him on Facebook...

A guy who doesn't work on our project anymore, but still checks on us regularly just did this:
- reported a bug
- started explaining what's causing the issue
- realised the problem was in a piece of code written by him before
- fixed his own mistake, committed it and created a pull request

We all had a good laugh.

Just for fun I am making an RPG Maker game called "IT Quest" where you go on a 40 hour long quest just to get the security team to modify a user. The game will feature tons of mandatory side quests and a convoluted plot that requires descending into the depths of the server room to find a virgin followed by a sacrificial ritual over the broken fax machine. And ultimately the security team just closes your request without telling you why and you have to fight the final boss of the game, Zeromus who runs security. When you defeat him you get the golden CAT5 cable of time which you beat the person who closed your request with until he reopens it and does his damned job.

Today I turn 25!

All I want for my birthday is a stressball.

If the guy who just turned 30 can get one :) ...

~ shameless request ~

So I just got Ajax, how do i make a GET request now? Google and stackoverflow didnt help

Just got messaged by one of my customers. He buys a lot of scripts from me for his gambling website. He asked me to screw around a bit with the code so that of someone bets above $2500 they automatically lose. And they have a 50% chance of winning when they bet lower than 1000. He actually wanted to pay a lot of money but I declined the request, I don't want to screw around with scamming people.
I think i did the right thing? I don't care about the money though.

My company needs a new Website.

ME: Boss, let me do it. It's just a simple static site with a few pages. **Dreaming about a fast and beautiful site**

BOSS: Your time is too valuable. Nobody is paying us for our website. The apprentice will do it.

Few weeks later... Wordpress page! Page loads in > 20sec. Over 150 request for css and js... It's fast on Mobile, because it just breaks and loads only half of the content.

So ashamed working in this Company. No sane customer will ever do business with us, when he sees this stackpile of shit.

@dfox Feature request
Could we have fully displayed rants ? Maybe as a setting disabled by default ?
I mean sometimes i'd like to relax and just mindlessly scroll, and having to tap to read longer rant and then tap back is, well, too much.
Especially when the rant ia only like 2 words above limit.

Dear Android:

I know I'm not on wifi. I get it. Sometimes data coverage isn't amazing or the network is congested. It's cool. You can just flash "no service" and I just won't try. or even "3G" and I'll have some patience. I rember how slow 3G was. It's okay, I'll wait.

But fucking stop showing 4G LTE if you can't make a fucking GET request for a 2kb text file in less than 5 minutes! Fucking really? Don't fucking lie to me with your false hope bullshit, just tell me the truth and I'll probably sigh and say shit and put my phone away.

But fuck you and your progress bar externally stuck in the middle. As if to say you're making progress! Wasting my time!

If you can't download a kilobyte in a 5min period, why even say I have data at all? What good does that do me?

You is not gonna beliebers what just happened lol

So a couple weeks ago I earned a stress ball (300+ ++'s) I sent an email about it but never got a reply, so I decided to just forget about it. But then I just ranted (lastnight) about how its so hard to get a stressball. So I basically just said "fuck it i'll buy one". Then some dude comes along and is like "omg not until he shows us the bought one" so I'm like CHALLENGE ACCEPTED and buy one...

Then I get an email confirmation from devrant store confirming my order for the bought stressball. And I notive that my spam folder has unread messages in it. i look inside the spam folder and what do I see?...

I see dfox replying to my free stressball request weeks ago lol. So yay, now I gets the 3 balls (or two - depending) lol omg, so many balls.

Boss: We need a new functionality to record company names for now.
Me: Ok. (This will be a quick one)

(few mins later)
Me: Ok, adding/editing/deleting company names.. done. I also added "date recorded" field, just in case we need it.
Boss: Ok, thanks.

(~20 mins later)
Boss: We also need a functionality for the users which has "this" permission to be able to "request" for a company registration. We need to add fields to record the contact person, email, phone, etc.. Once a "request" has been submitted, "this" person-in-charge has to get a notification on the dashboard. And the requesters, should get a notification that they have a pending request sent. Once the registration is done, the requester has to be notified.
Me: 👀

Had a job interview recently that went well besides one little disagreement... and it has made me question my sanity. Tell me if I'm wrong.

They asked the difference between a GET and POST request.

Wow, that's an easy one, they're giving me a break, I thought to myself.

I said "GET is used to retrieve data from a server, whereas POST is used to add data to a server, via it's body, which a GET lacks" or something like that.

They were like "ya mostly, but GET can be used to enter data into the server too. We were just looking for the body thing."

And I'm like.... yeah, you could do that, but that's not what it's meant for.

They mention stuff about query parameters and I hold steady that GET and POST are different because GET has a specific purpose. Otherwise, we wouldn't need the "method" part of an HTTP request at all. We could just either include a body or not include a body.

I ended it with "Well, POST implies that you are adding data to a server, and GET implies you are querying data from the server. When I'm reading documentation, that's how I quickly determine what an endpoint does."

My confidence was a little shaken at this point. Crazy what two people with (I assume at least) 10+ years of experience telling you you're wrong will do to your confidence.

Writing more infrastructure than product.

Look, my application requests and transforms data from a single external API endpoint, it's just one GET request...

But I made an intelligent response caching middleware to prevent downtime when the parent API goes down, I made mocks and tests for everything, the documentation is directly generated from the code and automatically hosted for every git branch using hooks, responses are translated into JSONschema notation which automatically generate integration tests on commit, and the transformations are set up as a modular collection of composable higher order lenses!

Boss: Please use less amphetamine.

Just had chat with Microsoft support to solve a issue. I accepted remote session request. She did something and couldn't find proper a solution to my problem. Finally, she told a temporary solution and quit the chat.
When I was about to give feedback that she wasn't helpful, SHE CLOSED FEEDBACK WINDOW and then ended remote session. Lmao

I feel a bit bad when I reject most people after interviews - they'll do alright, just don't have the knowledge we're looking for.

Other people who fail interviews just piss me off.

If you're applying for a *senior* position, yet you tell me a race hazard is "what happens when concurrent applications are working efficiently", a GET request is "only ever used in a REST API", a POST request is "when you use TCP directly" and you can't write a single line of code in a new project because "in the real world we always just modify what's there already", then please sod right off. There comes a point when you clearly know bugger all, have extensively lied on your CV, and you're just trying to con your way into a position while hoping no-one notices.

Argh.

Ahhhhhhhhhhhhh!!!!!!

A pull request I made to an actual open source project got merged. I might actually be a real dev now!

(It was just to remove a snippet config, but still!)

Request: I don't like the way the page looks. Make it better.

Question: can you give me some more info? What is it that you dislike about the page? You approved the design, the mockup, the HTML version...and we just finished implementing the backend. Can you be more specific?

Response: make it more like this *gives link to completly new layout from a theme on themeforest*. Why does mine not look like this. Make it like this!

Reaction: *fuck this shit, never freelancing again...* Well, then do it yourself. I'm done!

// best feeling ever :)

Swagger does not send request body for GET calls.! WHAT THE FUCK..! And the argument supporting is get calls should not have any request payloads and rather should have response payloads since its a "get" call. Are you serious?? What if there are parameters to be passed which cannot be accomodated in the params or the header. Even though people are kind of literally abusing on their issues page still they adamantly refuse to add support for this.

Swagger you had high standards in my book. You just fell so deep down there is no coming back.

Holy shit balls it works (so far)

-
So I’ve been working on a project... well feature for the past year (yes 12 whole fucking months - anti agile I know)
And today I got to merge that bitch of a pull request into the current working branch and deploy it to UAT - no conflicts 😵I think I need to put the lottery on tonight!
And some how, by some stupid lucky roll of the dice it just works.

I have never felt so afraid and delighted in my life!

Just got a merge request to review. It's TERRIBLE

- 93 changes
- 23 commits
- includes multiple features
- includes new project configs
- includes refactoring

NO. Please don't do that.

Do smaller commits. One feature per MR. It will help you and the reviewer :D

I tell him to submit a pull request, he just merges his code. I revert it and tell him to submit a pull request, he submits one then merges it himself immediately after...

Really!? WTF would you even write a confirmation message reminding me to contact the admin if I didn't request my password change on this screen!?!? Of course I wanted my password changed, I just entered my new password. That type of crap is what you should e-mail me AFTER my password changes.

Request from a senior backend dev in a previous company:

Talking to the team thats responsible for the auth API's is such a pain. For this new API can we just not add any auth to it? Its only going to return details about who the email address belongs too. Like name, address, date of birth, car registration etc. No one will care about that, and it will be easier for mobile to integrate right?

I jump on an existing scala project.

git pull && sbt compile test

Tests are failing.

Me: "Hey team, the tests are failing."

Team member: "That cannot be. They were passing for the the last run."

Me: "Did you run them locally?"

Team member: "No, on Jenkins. It was fine."

I check Jenkins.

Me: "What do you mean it's fine. The last successful deployment was on the end of May."

Team member: "The Pull Request checker always went through successfully."

I check how our Jenkins tasks are configured. It's true that the Pull Request Checker runs successfully yet due to a "minor misconfiguration" (aka "major fuckup") the Pull Request Checker only tests a tiny subset of the entire test suite.

Team members were were fine if their Pull Request got the "Success" notification on bitbucket's pull request page. And reviewers trusted that icon as well.

They never checked the master run of the Jenkins task. Where the tests were also failing for over a month.

I'm also highely confused how they did TDD. You know, writing a test first, making it green. (I hope they were just one specific test at a time assuming the others were green. The cynic in me assumes they outsourced running the tests to the Jenkins.)

Gnarf!

Team member having run the tests locally finally realizes: "The tests are broken. Gonna fix them."

Wow. Please, dear fellow developers: It does not kill you to run the entire test suite locally. Just do it. Treat the external test runners as a safety net. Yet always run the test suite locally first.

Our PM is on vacation. And our CTO/CEO takes control of the PM role.

So today he decided it was time to just start a customer change request. Regardless of the customer not having approved the actual solution and estimate.

He just said that he did not want to waste any more time talking to the customer. Now they are gonna get what ever he thinks they want.

I predict this to backfire in a fabulous way. What could possible go wrong🤔

Kind of rant.

Why doesn't the cat sit on the keyboard?
At least my two cats just love that place. Perhaps a feature request?

My study's logic every fucking time: (I'm a senior by the way)

Junior: Sir, could you help me out for a minute?

Teacher: I'm busy right now, please fill out the support request form and go ask one of the seniors (yeah, not even kidding)

Junior: Alright, hey dude, could you help me out maybe?

Me: yeah of course, just get your laptop and go sit here next to me!

Other Teacher: Hey you, leave the seniors alone, they've got their own work!

post != rant;
post = "Feature Request";
@dfox

Stack Overflow is full of abuntch of downvoteing dickbuts. The devrant community is so much more accepting of new devs, why not add a question section.

Down votes would only be allowed for spammers.
One the question was solved, it would go into the devrant question archive, Searchable by everyone.

Ik you have heard this one before, but it's Just my two cents.

Why write any specs anymore? The juniors don't read them, nor do the product managers. I'm just talking to myself at this point.

So, I waste time writing these nice detailed tickets, then when I go to review the pull request, the whole pile of horseshit is half done, and when I ask the product managers for resolutions, they don't have a clue either.

So just give me the whole fucking app, I'll do the whole damn thing myself. See you on Mars in 2025 while you and your pleb asses serve me fries and burgers.

Its so weird working in this company. No onboarding, no micromanaging, noone to track your progress or performance. U can basically do what u want and ask what u want and requests will be fulfilled.

Initially was assigned to a random team and started fixing stuff. I hated the scope so after 2 months in requested to switch teams, request approved.

3 months in realized I lowballed myself during the interview and actually am doing better than half of the team, so I asked for a 43% bump, request approved.

4 months in I realized that I did atleast 100hrs overtime in a month during crunchtime, burned out. Asked for a paid week off to recover, request approved.

5 months in realized that we have many MR's piling up in the team and I could help with approving some of them, but they grant MR approval rights only when u work here for a year or are a decent dev from the get go. Requested for MR approval rights, request approved.

Again it feels so weird working on a big product with 6-7 scrum teams. Its like there is no bullshit, just ask what you need you will get what you asked so you can continue working.

On the other hand its kinda weird to keep asking everything, in other companies a good teamlead/manager shows more initiative takes care of stuff like this without even asking.

Comment on a GitHub issue on one of my repos:

"Almond I posted this feature request last month, please start to work on it in your free time"

Dude, that's just made it a whole lot less likely I'll even give that feature request the time of day. Take your entitled arse attitude to the bank and pay me to do it if you care that much.

Also, free time?!?! Hahahaha.

3:30 on a Friday, random PM: our Argentina devs just sent out a merge request. We need to release before the weekend.
me: We try not to release on Friday afternoon unless it's for a high priority bug fix.
PM: This is urgent
me: why?
PM: We're two weeks behind schedule and the dev for this it's going on vacation in an hour.
me: so, you want to release when there's no one around if something goes wrong and the person who knows anything about it isn't contactable?
PM: yes
me: no.

Does anyone have a good and free translator api I could use? I’m doing small school project and I just wanted to create text translator app. I tried yandex already, and ibm sucks since it doesn’t allow ajax request

Business: we need feature x in two
Days, highly urgent!
Me: fine, here’s a shitty implementation we can live with until you decide how to Actually make this work in the future.

2 days pass...
Me: where’s the content for feature x?
Business: awaiting approval

5 more days pass...
Me: I’m guessing this super urgent request wasn’t needed after all?
Business: it’s still awaiting approval
Me: so... I’ll just go and remove this feature, and revisit when its actually needed.
Business: no, it’s needed now, we are just waiting on approval
Me: 🤷‍♂️

Duck my life sometimes.
I could have built a full fledged system of this shitty hack job instead in the time taken to approve a useless piece of content.

WHY DON'T YOU FUCKING READ THE CHANGES IN YOUR FUCKING PULL REQUEST???

If you did, you would realize that 50% of the stuff is total fucking nonsense. I don't want to see that you changed "var a = 0" to "var a= 0" just because you can't type with your shitty fingers.

Also, if you did read the changes in your PR, you would have realized that you added a bunch of totally unrelated changes in totally unrelated files.

Fuck! Am I the only one who always tries to produce a clean changeset?? Damn

[ Coworker walks up to my desk at 4:15 PM ]

Coworker: "Hey man. We had to make a few changes to the codebase because one of our unit tests were failing. Can you take a look at a pull request for me?"
Me: "Yeah sure, how many files?"
C: "About 600"
Me: [ thinking it might just be a ton of libraries or gradle shit] "...ooookaayyyy... that's a lot but doable... how many lines?"
C: “128,000 lines"
Me: "Fuck you"

Contributed to a open source project for the first time what hasn't been updated in 3 years and my pull request was just accepted!

I just submitted my first pull request though it was a minor addition in readme. So happy 😊

I created a my portfolio using ReactJS and actually open sourced the whole thing. Within just a few weeks, its got 67 stars, 38 forks, 3 watches, 1 issue, 1 pull request, and so on.
People out of nowhere messaged me in my whatsapp, skype, facebook to help them in React.
People out of nowhere wanted to hire me, even though I'm still working in a company.
People out of nowhere messaged me just to tell me, how much they liked my work and appreciated it for open sourcing it.
It felt awesome! Like, I can't explain how amazing it felt! ^_^

@trogus @dfox
Can we have support for
```
snipets
```
Doesn't even need syntax highlight, just the <pre> behavior.
In support of my request, I know this isn't code sharing but we still quote code and commands alot.
It would be a nice differentiation.

!rant

*me trying to add one more field to a SQL request*
*asks coworker* Hey, do you know how I'd get this field? You have to go through 4 tables just to find it because of the way the tables are related.
*coworker looks for a bit* Oh. That's crazy. We should ask the DBA.
*we ask our 60 year old DBA for some help.*
He walks us through a minefield of inner and outer joins and selects and we finally arrive at a solution. Kudos to our DBA, who in the eyes of us young devs is a wizard.

Two new coworkers step in. HR hasn't set up their accounts yet. We create all necessary tickets and wait. A week has now gone by. New guys are just sitting there reading documentation. Call HR

- We are currently processing the request.
- But what is taking so long?
- The request needs to be approved in 4 steps by people on higher and higher levels.
- What level is it currently on?
- Two

*Rage quit*

Just spent hours, debugging why a system is creating two objects in the database when trying to create one.

Turns out it is Chrome re-sending a POST request.

Really.

What. The. Actual. Fuck. Google.

Product manager had me spend an hour setting up his machine for rails development. Then walk him through all of our workflow. He then proceeded to make some changes to a header tag content. Made a pull request while I was holding his hand. Then he walks out of his office acting like he just won a national championship and proceeded to talk about how he was basically a developer for the next hour interrupting work.

*Creates a rest api that runs on localhost:8080*
*Creates React front end that runs on localhost:3000*
*Sends a GET request to api*
*Cross-Origin Request Blocked: The Same Origin Policy...*

Thats my fucking dev environment and its my local fucking host! Let me just send a fucking request to my own fucking machine you piece of shit! Why the fuck they didn't add an exclusion to fucking localhost?!?

I swear...in enterprise...doing things right is almost pointless. First off they punish you for it by insisting you use shitty outdated libraries and resources, making every request painful and a week long, and telling you "don't use any design patterns or good practices because the over seas third party people we hired won't understand it".

And ultimately those third party people are going to get a hold of your code and turn it to shit. So really...other than having pride and standards...just pile more shit on top of the other shit because it will all be shit soon enough.

“sEniOr tEcHniCiaN”: “I don’t know what Blazor is. I write my projects in ASP.NET. You should just use ASP.NET”

Me: …”Blazor *is* ASP. This project is running on ASP.NET 6.”

“seNioR tEchNiCiaN”: “As previously stated, I don’t use Blazor. I don’t care what version it is.”

Yes, this is a real exchange from my ongoing problems with this idiot.
His attitude is what ticks me off the most.
He doesn’t know what CORS is.
He doesn’t understand that “ASP.NET” covers Blazor, Razor Pages, the old MVC stuff, web APIs, and more.
He doesn’t understand the difference between a web request being initiated from the browser via Fetch and a web request being initiated from the server. (“My ASP site is shown in the browser, so requests to the third party API aren’t originating from the server.”)

And yet has the arrogance to repeatedly talk down to me while I try to explain basic concepts to him in the least condescending way possible.

After going around and around in circles with him, he finally admitted to me that “he doesn’t actually know what the CORS configuration looks like or how to modify it, to be honest.”

I just wanna go home.

Data Engineering cycle of hell:

1) Receive an "beyond urgent" request for a "quick and easy" "one time only" data need.

2) Do it fast using spaghetti code and manual platforms and methods.

3) Go do something else for a time period, until receiving the same request again accompanied by some excuse about "why we need it again just this once"

4) Repeat step 3 until this "only once" process is required to prevent the sun from collapsing into a black hole

5) Repeat steps 1 to 4 until it is impossible to maintain the clusterfuck of hundreds of "quick and simple" processes

6) Require time for refactoring just as a formality, managers will NEVER try to be more efficient if it means that they cannot respond to the latest request (it is called "Panic-Driven Development" or "Crappy Diem" principle)

7) GTFO and let the company collapse onto the next Data Engineering Atlas who happens to wander under the clusterfuck. May his pain end quickly.

So I'm a backend engineer and my boss keeps telling me I over engineer stuff. I'm never given a technical spec or architectural spec, just told what to do so I build. But apparently I over engineer? Admittedly I do tend to but recently I cba and done the most basic thing. Apparently its over engineered.
Would you agree that to say something is over engineered a technical requirements document is required in order to specify over engineered said request needs to be?

Ps: my boss is an inappropriate cunt. Finally got that out.
Feel like hes just making arguments with me to get rid of me because I didnt want to cuddle in bed with him after he gave me an uncalled for back rub..

Just recalled the time we sent the new apprentice developer to HR for a "verbal agreement form" to request his birthday off. HR Came back down with him unsure as to where to find the verbal agreement forms.

"Well, that's not very funny." - HR

Just received a support request that the lift is broken and requesting I fix it... Their reasoning? It has buttons and lights up (I'm dev/IT at small company)

Today the IT deparment update the firewall's configuration, they blocked almost every website except email and Google.
The problems:
- Blocked some systems outside the organization, there are in another building and also network
- I can search on Google but I can't see the results outside Google
- Forget about download depencies, libraries, deploy code to outside services, search at StackOverflow

I JUST WANNA SAY GOOD JOB, GUYS

PS: The firewall also block the SSH port, I had explained to my boss and he sent a request for allowing the port, so far no answer

Well, for starters there was a cron to restart the webserver every morning.

The product was 10+ years old and written in PHP 5.3 at the time.

Another cron was running every 15 minutes, to "correct" data in the DB. Just regular data, not from an import or something.
Gotta have one of those self-healing systems I guess.

Yet another cron (there where lots) did run everyday from 02:00 to 4ish to generate the newest xlsx report. Almost took out the entire thing every time. MySQL 100%. CPU? Yes. RAM? You bet.

Lucky I wasn't too much involved at the time. But man, that thing was the definition of legacy.

Fun fact: every request was performed twice! First request gave the already logged-in client an unique access-token. Second request then processed the request with the (just issued) access-token; which was then discarded. Security I guess.

I don't know why it was build this way. It just was. I didn't ask. I didn't wanted to know. Some things are better left undisturbed. Just don't anger the machine. I became superstitious for a while. I think, in the end, it help a bit: It feels like communicating with an alien monster but all you have is a trumpet and chewing gum. Gentle does it.

Oh and "Sencha Extjs 3" almost gave me PTSD lol (it's an ancient JS framework). Followed by SOAPs WSDL cache. And a million other things.

Dev: I think I just deleted data I shouldn't have. Can you do a rollback?
Me: No, I'm a DBA, I don't touch data. Did you commit?
Dev: Yes, I committed.
Me: Your data is gone.
Dev: But don't you guys do backups?
Me: We backup the Prod servers. We only back up Dev on request. Did you request a backup in Dev?
Dev: No.
Me: ...
Dev: The Testers are going to be pissed.

Yay! I just got a FB friend request from a really beautiful woman! We have no friends in common, and when I looked at her profile, she didn't have any friends, and she likes robotics. I can be her first friend!

Or not.

My manager wonders why I don't respond to people in a timely fashion.

I'm watching 83 Slack channels and private messages, I get 45 emails an hour, I'm on-call, and I have 125 servers to monitor.

Number of Jira tickets I received in the last 3 days? One single fucking ticket.

Open a damn ticket and I'll shove you to the bottom of the backlog, just like everybody else... I mean, I'll be able to track your request and not loose it.

To the coworkers who won't read this -- If you have a question to message me, type the QUESTION ITSELF. Don't coyly request permission to ask me a question because you're worried you'll bother me, that just turns it into TWO questions. Let us put an end to saying 'hey, can I ask you a question' and then virtually walking away.

The new mobile app codebase i'm working with, was clearly written by someone who just read a book on generics and encapsulation.

I need to pull out 2 screens into a separate library to have it shared around. The 1 networking request used is wrapped up in a 'WebServiceFactory' and `WebServiceObjectMapper`, used by a `NetworkingManager` which exposes a generic `request` method taking in a `TopLevelResponse` type (Which has imported every model) which uses a factory method to get the real response type.

This is needed by the `Router` which takes a generic `Action` which they've subclassed for each and every use case needing server communication.

Then the networking request function is part of a chain of 4 near identical functions spread across 4 different files, each one doing a tiny bit more than the last and casting everything to a new god damn protocol, because fuck concrete types.

Its not even used in that many places, theres like 6 networking calls. Why are people so god damn fucking stupid and insist on over engineering the shit out of their apps. I'm fed the fuck up with these useless skidmarks.

So according to google domains I just put in a transfer request 5 days in the future... Fuck me I need to learn to contain these powers...

Someone just sent a connect request via Skype. The request had a full name so Googled and then LinkedIn'd

Found a few matches but her headline was: Intelligence Officer at National Geospatial-Intelligence Agency

sorta worrying?

Ah the wonders of working with non-technical people. 😤
I had a logistical problem. The SSD on my laptop crashed.
Me: No biggie just request new one.
Them: Sorry we don't have any on stock.
Me:Okey then give me a new laptop.
Them:Ok fine here you go.
Me:I specifically required 16 GB of RAM.
Them: ok here is an extra 8gb
Me: I need DDR 4 not DDR3
Them: don't have any. We will restock shortly.

A couple a days later a colleague requested 8gb DDR3 and got DDR 4.
The fuck is wrong with people. Can you not read?🤔🙄

So I'm job hunting and trying to beat ATS systems like the cool programmer I try to be.

Same company, two postings - first position I sent my resume to, rejected me after a day. Second position that I optimized my resume about 2% more, immediate interview request.

Here's the kicker, interview is done using an AI.

So basically I spent time trying to beat one robot just to be video interviewed by another robot.

Welcome to the future ladies and gents.

So, I just realised that a contribution I made to an open source project 12 days ago had gotten accepted 3 days ago. I'm so ecstatic over this!
I was basically just in need of type definitions for a javascript library, and seeing as it didn't have any, decided to make them myself. Done that, I made a pull request, but seeing as there was no changes after a few days, I forgot about it.
Now I just remembered about that, and wondered if it got any comments or anything, and it turned out that they had accepted my PR and it had already been put into a release 3 days ago
I can't contain myself right now, it was my first open-source contribution, and it just feels good to know that I somehow helped some people by giving them type definitions :D

Cheers

This stupid crap is pissing me off.

I write a quick blob of code that performs an http request with custom headers and writes the response to a file. easy squeezy. Everything works.

I abstract it into a class and add request building and stages (enjoayble!), and have one method make the response, read its body, and write to a file. I literally copy/pasted most of my existing code into the method and indented it. The only changes were updating var names to instance vars.

But now? It's complaining something is trying to read the request body twice, and it's throwing a fit. What? How? You were just working!

asfklasjdf;l

< !-- features request -->
1) I think we should have a left swipe menu open action.Every time I want to open menu I have to go left top of screen.
2) preview of attached image if possible
3) Open images in posts directly without going into post and then image
4) auto play gif !??
5) Make rant favourite without going in ? Like a star symbol I suppose !

Just few thoughts ! Happy ranting ...😊

Just did my first JobIntentService on Android. Hoo, boy.

The problem: I need to send a network request.

The issue: Android.

Of course, you can't do network on the main thread. That's silly in any application. Android really does try to punish you, though. The Android lifecycle can really fuck you over here. Imagine a long-running network operation, like 15 seconds. Plenty of time for the user to do something silly, like rotate the screen.

If you opened up a good old new Thread from Java, you'd get a crash because of a screen rotation. Same thing with Android's AsyncTask, which is the top answer on StackOverflow. AsyncTask is made for things that will take no longer than a few seconds (less than 5!). Network, especially cell network, can take longer.

So the solution? Create a JobIntentService class. It's a service, it will run in the background. You need to register it in your Android Manifest and ask for a new permission (wake lock). You need to implement another class for the receiver, and then you need to go to your activity and implement the receiver interface you just wrote.

Just. For. A. Network. Request!

And as far as I'm aware, this isn't even that bad considering the rest of Android's bullshit.

What a headache!

“Hey, thanks for accepting my request we have a role you might be interested in.”

Sure, happy to move forward

“Great you just need to a complete a Technical test”

How long is the recommend time?

And I quote:

“It’s entirely up to you how much time you spend on this task. I’ve seen tasks done in 45 mins with minimal effort previously. I’ve also seen others take a week on it. Totally your call”

——

...so you contact me to offer me a role and want me to invest up-to 1 week on a technical when I’ve not even visited your offices. How about no.

"I want visibility in the sprint", "Information for everyone! When you do even a small refactoring, you should add a card to the sprint, clear?"
Those were the words of the product manager.

That sounds reasonable but when there is a bug to investigate, he just pops to the chat channel throw a request with a bit of information and asks to check/fix that.

So to keep my sanity, I asked him to create a ticket with relevant information and additional observations so we can have visibility as he was advocating for it ;)

It felt just good to see him going silent :D

Feature request:

A lot of people have been commenting on rants just to later get notifications about it, but also from my experience often times I comment on a rant but don't want to be subscribed to it.
Why not make it not subscribe you to the rant by default, and instead change the rant mute button to do the opposite and subscribe you to that rant? It would avoid the pointless comments, and this

This is a request from all devs out there:
Please, If you plan to use a word play in naming your next product, please make it a little specific.

*googling "Brackets + [issue with some programming language]"

Just imagine how would I find what I want in a pile of crap about matching brackets.

Friend of mine created a blog from scratch... You could create a post, by just sending a POST request (no authentication required!)....
As an additional bonus: you could dump full unfiltered HTML in a post, which was then executed...

Please kill me

User: "Why isn't this process updated? There's something wrong with your system."

Me: "Did you submit the request?"

User: "Uh yeah I'm sure I did..."

Me: "Go submit the request again." (they never did the first time)

User: "I don't know how. Will you show me?" *shows user how to do it* "Ok I did it now."

Me: "You did it wrong, you need to resubmit it."

User: "Ok I resubmitted it."

* a week later *

User: "The process still hasn't shown any progress."

Me: "You didn't resubmit it like you said you did."

User: "Will you show me how to do it again?"

* fuck me *

Me: "Sure..."

Process works as expected and everyone lives happily ever after, except the developer that knows it is just a matter of time till the next user blatantly lies, has no respect for anyone's time, and demonstrates a complete lack of desire to care about their job at all and just wants to bitch and complain like a typical lazy ass-hat.

Someone just told me that I have a 'strong LinkedIn network'

Little do they know that I just accept every friend request I get

Me: why are we paying for OCR when the API offers both json and pdf format for the data?
Manager: because we need to have the data in a PDF format for reporting to this 3rd party
Me: sure, but can we not just request both json and PDF from the vendor (it’s the same data). send the json for the automated workflow (save time, money and get better accuracy) and send the PDF to the 3rd party?
Manager: we made a commercial decision to use PDF, so we will use PDF as the format.
Me: but ...

Just got an email with a new really nice douche-bag move from Postman to raise their prices again (this time for almost double) on their paid plans with excuse "it will help us deliver more of what our customers need from us."

Even though I've decided to look other way around for years on their electron-based garbage of bloated app, have not been a fan of their pricing 8$/month/user just for a simple feature such as sharing request schema and environment data.

This simply needs to stop and I'm seriously thinking about doing something about it. 🙄

Actually just got a bit of a project request with a 7 day deadline.

OK, great, but I'm on vacation for 5 of those days.

My first rant...

Every time a coworker asks for an enhancement, the request is followed by "it should be easy to implement".

1) If you think it's easy, then you obviously know the code better than me, right?
2) The idea of the enhancement may be easy, but you don't think about how a small change can have a cascading effect throughout the entire process... and potentially in a catastrophic way.

Happens every time. Maybe I'm just bitch eating crackers at this point, but it annoys me when people analyze something they have no idea how to write themselves.

I previously worked as a Linux/unix sysadmin. There was one app team owning like 4 servers accessible in a very speciffic way.
* logon to main jumpbox
* ssh to elevated-privileges jumpbox
* logon to regional jumpbox using custom-made ssh alternative [call it fkup]
* try to fkup to the app server to confirm that fkup daemon is dead
* logon to server's mgmt node [aix frame]
* ssh to server directly to find confirm sshd is dead too
* access server's console
* place root pswd request in passwords vault, chase 2 mangers via phone for approvals [to login to the vault, find my request and aprove it]
* use root pw to login to server's console, bounce sshd and fkupd
* logout from the console
* fkup into the server to get shell.

That's not the worst part... Aix'es are stable enough to run for years w/o needing any maintenance, do all this complexity could be bearable.

However, the app team used to log a change request asking to copy a new pdf file into that server every week and drop it to app directory, chown it to app user. Why can't they do that themselves you ask? Bcuz they 'only need this pdf to get there, that's all, and we're not wasting our time to raise access requests and chase for approvals just for a pdf...'

oh, and all these steps must be repeated each time a sysadmin tties to implement the change request as all the movements and decisions must be logged and justified.

Each server access takes roughly half an hour. 4 servers -> 2hrs.

So yeah.. Surely getting your accesses sorted out once is so much more time consuming and less efficient than logging a change request for sysadmins every week and wasting 2 frickin hours of my time to just copy a simple pdf for you.. Not to mention that threr's only a small team of sysadmins maintaining tens of thousands of servers and every minute we have we spend working. Lunch time takes 10-15 minutes or so.. Almost no time for coffee or restroom. And these guys are saying sparing a few hours to get their own accesses is 'a waste of their time'...

That was the time I discovered skrillex.

long time ago....
Feature request: We want an android backup solution in Our app!
UI guy has already developed it, you just need to see if his solution is solid!
Ok then - lets look at the UI: Nice progress bars, that turn into green checkmarks. Looks good.
Now lets look at the code: ... Ok. loading some files into memory.... and... dafuq? does not write to a file?

Backup to RAM. With no restore. 🤦‍♂️.

Just a personal request to @dfox
Can you screenshot only the part of the behind the scenes code of devrant? Just the part of it.
I want to see the syntax and how the language is used.
Thanks.

When you just wanna code but are waiting on the infinitely slow sales person to respond to a really simple request...

My very first rant here was about the mess of ticket submission and ticket tracking applications we use, and about how we were moving to a single unified system some day.

Well, that day is today. And, predictably, it went horribly wrong.

So the way it's supposed to work is people login to the portal, search for what they want to request, then fill in details and submit. It creates a request ticket assigned to the appropriate team. (The old way involved a bunch of nonsense that you can see in my first rant).

The thing is, I found out about this today, when I got a company-wide email saying the new system was live as of this morning. None of us knew it would happen today. Not that I could've foreseen any issues just by getting the announcement early, but still, usually people find out about these things beforehand.

So, ecstatic to finally be rid of the old ticket tracking system, I log into the new system and look for our request form, which is, of course, not there. I check the old system and see that they combined every single "general request" into a single request where you pick which team the request goes to.

So I finally find the right request, pick the right department from the drop-down, and see that the request looks much better than it did on the old system. Out of curiosity, I look at the list of people who are part of that department.

I am not on the list.

My ENTIRE TEAM is not on the list.

Because they migrated the team data to the new system a year ago, when the issue tracking/reporting portion of it went live. My current team was hired approximately six months after that and apparently updating the team data in the new system isn't part of our Onboarding process yet.

So... Bright side is I guess I will have a lot of free time soon since nobody can submit new project work to my team?

tl;dr: they took a great software product and implemented it so poorly that our team can't use it.

API Request validation is stupid.

Until you remember
* Your target audience is highschool students
* Your front end dev loves to fuck your stuff up
* His mom works in QA and she equally likes to fuck shit up
* It's just a good idea
* People just fucking suck

Got an interview request for a new job. They mostly do WordPress. I don't want to touch WordPress.

Talked to the Project Manager woman on the phone about the job, seems decent.

Sounds like a nice place to work at, but I just can't do the WordPress thing, man.

I forgot Visual Studio 2019 was a paid software until IT emailed me that my software request was forwarded to accounting 😅😅 I'm so used to just having the community edition on my home desktop.

I just received my first pull request today.

It wasn't what I wanted, expected, or hoped for.

It was a full-on codebase rewrite.

I made my very first pull request to a project of public interest.
It's just a paragraph in the React docs, but still.
I feel like a useful person.

So here I am testing some python code and writing to a file. No big deal. But damn is it taking a long time to get data back from this API. Ah it's fine I'll let it work in the background.

40 minutes later.

Oh! The requests timed out. No big deal. I'll just cut out the parts that are already done.

1st request in.
I wonder what the file is looking like.
Only showing 1 request.

waitaminute.jpeg

I should have more than that.
*Suddenly realizes that I was writing to the file and not appending.

Fuuuuuuuuuuuuuuuuuuck

Had this PM who would call me while intoxicated mid afternoon. He would come up with these random ideas, and request them be implemented into the web app we were building for him. One time he called me saying "I have an idea for a page, but so far just the page's title. I'll call you back and tell you what to put on it."

This was actually written by a Junior of mine (and if it wasn't for me having to review it, it would have made it to production):
- Admi password was just an MD5 in the javascript.
- Javascript would validate the password input.
- Javascript would then send a POST request to a PHP script.
- On display, the HTML of the news article wasn't HTML escaped.

My brain: "Let's just send this XSS vector to this PHP script"

DONT do production stuff on friday afternoon. This friday evening we had an issue on production and just wanted to do a quick fix. The fix resulted in a ddos attack that we accidentally started on our servers in an IoT project. We contacted all customers' devices and asked them for response at the same time. Funny thing is that the devices are programmed to retry if a request fails until it is successful. We ended up with 4 hours downtime on production, servers were running again at 11pm.

Submitting a pull request seems a good way to end the week. That's what I love about (some) projects on GitHub; instead of just ranting about bugs or out-of-sync documentation, you can fix the problem and send a pull request upstream. :-)

http requests

literally the bread and butter of any software engineer building applications, you would ASSUME they know what they are doing...

and you're gonna write a seperate http get and post function for every type you have?

apparently stuff like this that is written by "senior" developers? you don't even have a basic understanding of software...

i'm won't do it that way, becuase i'm an adult, not a child

what i'm going to do is write a HTTP request util function that can be used for any type and HTTP verb. DRY, single responsibility, etc.

imagine making the http request itself a responsibility coupled to the type 😂😂😂😂

get a clue and come back later

i can't tell anymore if my thoughts are so outlandish compared to everyone else that no one understands them, or if i've been doing this so long that i just immediately understand what needs to be done and don't know how to explain it to anyone else anymore (or take the mental effort to)

peace out

oh P.S.: imagine thinking the SOLID principles are only applicable to OOP

stay safe out there folks, its getting more painful every day

Based on @darksideofyay "poll feature" request I made a simple bot to make them.

Just post this as a comment:
@PollBot Q: <Your question>?
A:
- <Answer 1>
- <Answer 2>

// Up to 10 answers
It will post a comment for each answer, just upvote the one you like (look at the upvotes to see the result of the poll).

P.S. It's not ideal and it's running on a mini PC in my house, so it could fail sometimes. :P

Ok so we just signed a new client with some "artificial intelligence" back-end...

To authenticate with their back end, they developed a FU**ING GET REQUEST so the username and password are passed in the URL.

Then we get a token that we pass in FU**ING GET REQUESTS to communicate with their "artificial intelligence enhanced" back end.

I can't even. I just can't.

Our ticket tracking system and our IT service request system are from two different companies that are direct competitors. The source code is full of temporary hacks to just make them play nice until a better solution is worked out. Fast forward a few years and we're abandoning both systems in favor of a single, unified system that handles everything. We currently have maybe 20% of the new, unified system done, which is now hacked together with both of the legacy systems until we finally transition fully to the new system. The current plan is for next year, but the plan six months ago was for this year, and almost no progress has been made since then, so we're probably going to have two ticket trackers and two request systems for a while.

Actually, three ticket trackers and three request systems. The third ticket tracker is used to track work done on tickets that exist in the legacy tracker because the legacy tracker can't do that on its own, while the third request system is the oldest and most cumbersome legacy system of them all.

today I spent an hour and a half (30 mins past my paid hours) explaining go my boss that I'm not just being rebellious; that the time I'm taking to do the job right is appropriate and the only way to end up with a piece of software that they'll be able to request features for without adding on to the absolute shit pile frankenkrakken that is their mutated 13 year old OSCOMMERCE dumpsterfire.

I convinced him.

Chat apps. What's the idea? Those are basically tools of violence. They give you a possibility to in real-time stop someones work and start demanding service. Now. Immediately.

Usually people send you first email and then they after 10 seconds chat "did you see my email?? read it! serve it! please me!" Usually it's just a small request to document something, review someone else's document. Do it ASAP. If you were coding something, then drop it and do someones job for them instead.

You got a request for me to create some verification case list? Put it into my backlog. I might start doing that in week or two. Or month. In case there's nothing else more important. Since I know that you are working with something that you think is the whole universe, but trust me, I got my own problems already.

But hey, if I don't reply to your chat in a minute, please feel free to walk behind me and start explaining your life. No need to wait even for me to get my headphones off. "Oh you are in conf call? Well, this is just a quick thing blaa blaa..."

Amazon's AWS support sent me an email about a request to support that I sent to billing, saying they sent it to billing. They then said they couldn't help.

I just need them to stop billing me for things I no longer use!

I just found out google web dev tools let you copy a request as curl command!

Time to scrape some websites baby!

Image relevant.

Tried getting puter to talk, puter no want to talk.
Me sad.
Me tell puter to stay put and listen at 4444.

External device doesn't do shit.
Me sad.

Read the docs. Nothing. Written like a 5 year old would.

Be angry, how do I put external device into tcp/ip mode? No one knows, the docs don't know.

I get frustrated and pull the USB cable out of it.
Mfw it starts spitting out requests to my server with no end in sight.

Mfw the requests all just repeat.
Mfw the docs tell me to acknowledge a request I have to respond with a content type of
"application/x-www-form-urlencoded"
How.

Not possible.
Mfw I decide to dissect a request to check it's accept header.

Mfw it says text/plain.
Great, no idea in what format the thing expects it.

Try writing out query string plainly.

It fucking works.

Why can't people just learn to write proper documentation.

Freaking love it when devs from other teams work on you code base and implement components you already have ... Don't talk to each other, just submit your awsome code and leave a mess behind. But OK ... Just a simple click on Pull Request -> Denied!

A dev joins the project. I help him set up, and he has everything up and running. I give him a task to fix a CSS issue, I even tell him what needs to be done. Almost 4 hours later I begin to wonder what's taking him so long and what is he up to. He finally sends me a pull request with just one line of code changed, and leaves for the day, over 45 mins earlier than supposed to.

Today i spent one hour and half trying to understand why my ajax request was returning "undefined" instead of a json object. It turns out i had just to restart ionic because of some bug in the ts transpiler.

Fuck you typescript.

>Be me
>Decide to contribute to an open source project for the first time
> Nothing big, just a simple compile error fix
>Make first ever pull request
>Over weekend pull request accepted
>feelsgoodman.jpg
>Take a look at recent commits
>Module I tweaked was finished in a commit 6 hours ago
>Fix no longer relevant

So close.. :(

Well shit.

Recently refactored some backend code that makes some https requests.

I realized I was repeating myself a lot with the request options so I decided to make a function to generate the options with defaults.

Works great, shortened my requests to almost nothing.

The problem is it wasn't working great.

It took me about an hour to finally figure out that the requests were failing because I forgot to return the options object after I created it.

Sending the request with null options just makes it act as if the options are there, but incorrect, so I was totally lost.

FML

I just wasted 2 hours trying to figure out why the properties of a destructured object returned undefined, even though everything was fine in JSON format. Tried to request data on the frontend from my server with a database attached. Tried accessing each object of my array separately, it worked. In a loop: dataArray[index].propertyX ... undefined??
Turns out I used the wrong property names to access the info inside each object.
🤦

Today I solved the problem assigned to me by changing one character. Simplest fix ever. Except that this problem is not on my project, and I don't have control over this project, so I can't merge my pull request or deploy the code, and the dev that does hasn't answered email today, and he's not scheduled out, and he's not in his office. Whatever, I'm just gonna say it's fuck it Friday and call it a week.

It is not on production anymore, but it was for long enough. Someone thought it would be a great idea to be able to debug a web app while signed in as a user reporting a problem. How to do it? It's easy. Just check on every request if magic HTTP parameter SIGN_IN_AS=id is present and if it is, sign in as this user. Of course, it worked also with admin account with hard-to-guess id=1.

me: "I need to buy some licenses for the `software package`. I'm just going to use my corp card..."

manager: "...Sorry, you'll have to go through procurement for those licenses...I'll put in a request"

me: **grumble** -- waits a week -- buys them on corp card anyway

6 MONTHS LATER

procurement: "now how many licenses did you need?"

Fuck NodeJS. I don't want you to be asynchronous sometimes. My gahwd I need like 3 deep nested loops just to get you to make a request and compile a damn JSON of requests.

I'm learning Golang goodbye forever node.

Just received a Jira request to remove training videos from the business ethics page or our employee intranet because we longer hold the license's.

HaHa

I have a crush on my single, young manager. He sent me request on facebook recently, although he has befriended almost everyone in the office, I just can't stop thinking about him.
Please help me, give me good reasons that it's a stupid crush, I literally can't stop thinking about him.

Whyyyyyyy do people go back on their word and stab you in the back just to make themselves look better?

Mate, I’ve got a paper trail of your request, detailing EXACTLY what you asked for. Don’t make me use it against you to prove you’re wrong and I’m right... guess I better start collecting emails to use as self defence 😩😔

So I just used Google analytics data from my sites to reverse stalk someone who google stalked me today. I got a whole bunch of information including their mobile model, their city and bunch of other data to confirm they did actually stalk me and understand their psychology.

Backstory: I had deactivated my instagram a couple of weeks ago account without any notice. It was the best decision I made this year. I feel more focused and found myself with plenty of time which otherwise I would have spend on lusting over those sexy ig girls.

Thought nobody would even notice or care. But apparently this one girl, my 2020 covid long distance lover whom I haven't talked to in over 8 months noticed it and decided to Google me.

She spent over 25 mins on my main site and also somehow managed to discover my dead travel blog from Google. I was thinking that I did a good job with the pseudonym I used for the travel blog. Apparently that's not the case!

She must've then proceeded to my linkedin account listed on the site and then sent me a connection request. That was then the notification popped up in my phone earlier today and made me feel butterflies in my stomach. I hadn't felt those butterfly feeling ever since I figured out that we can't be together or possibly even meet for once in real life.

I was curious how she found my linkedin and why sent me the request. We are not even in a related work field, same country. I never thought I'd be thinking more than 5 secs over a linkedin connection request.

That's what lead me to check out the Google analytics data to find the chronology of the events that lead to this connection request.

Anyways, it warmed my heart to learn that she still remembers me after all these months and that she bothered to Google me. Maybe she worried if I blocked her in ig? Or maybe she wondered if I lost my life in the recent covid wave?..

I wanted her to think that I was dead by not responding to the linkedin connection request. But it is possible that she checked out my GitHub profile and found my recent activities.

It fucking sucks knowing that I might never meet her in real life. If we meet, I worry it will lead us to doing things that might hurt others.

I guess at least I can die knowing that there was some truth in our love and someone cared about me and that it was not some illusion I felt..

Maybe the least I can do for her is to just accept that connection request.

Request I saw today...

* A new, empty AWS Account
* The ability to run 120 high memory EC2 instances, including up to 80 instances of dl1.24xlarge, but don't worry, 40 of them will be spot instances. I'll probably just start with two m5.xlarge for simplicity.
* VPC Peering into our primary AWS network
* VPC Peering into a 3rd party's network (because we're paying them for this service)
* A couple cross-acount IAM roles
* Granting "AWS: AdministratorAccess" to said IAM roles

I'm a bit behind schedule, and this is urgent. When will you have this completed?

I'm still wet behind the ears as developers go, and about a month ago I cobbled together a webservice. After many bug fixes I somehow got it working as intended, held together by tape and shoestring and creaking all the while.

This week, one of the consumers of the service wanted me to open it back up to change the name of the request .xsd. no functionality changes, just a name change.

I protested, worried my service would fall apart if I breathed on it. But he insisted so I made the change.

I just tested it and... it's working as intended.

But I still want to be mad about this!!

TIL you can crash a Tomcat request processing if the app reads request bodies using a reader() and you feed it a json body with an innocent nbsp :) the whole request processing just goes *pooooft*

reminds me of an ios bug which could brick the phone if it received an sms with weird chars.

These lynch-pin-bugs where a single byte/char in the right place at the right time can tear things down, are so subtle and fascinate me for some reason :)

Last week,my friend asked me to fork and pull request on his github repository so that he could review my changes and merge them,I had included some more exciting features in his app but till now he has not merged my request,instead he just copied the changes I made in his repo into his repo manually and updated his project,still he has not merged my pull request!!
That guy is a genius!

Send the dev a request for a design before they do a delicate process. They send back some mess done in MSPaint and a ton of select statements, with no context or explanation.

Send back an example of what they need to work through. Get back a response saying that the previous spec was just a draft, and once they complete development they’ll complete the design.

Why would I want a design once it was too late? What would be the point?

I have been trying my best to fix a broken process and a product that never saw the day of the light.

Aligning all the teams, trying to bridge all the feature gaps, and at the same time learning this new product and company culture.

Now this lady comes to me with a requirement. I have zero clue what it is and instead of empathising with me that I am new and should dumb down her ask, she kept throwing heavy product specific terms as if I have been working in this team for previous 9 lives.

Anyway, I take her ask into my product roadmap and try to prioritise it.

Now I connect with them again for some discovery and she is passive aggressive towards me that it's been more than a year no one is considering their request and started whinning.

I have just joined the org 6 months ago and you start attacking me for someone else's mistake?

What the actual fuck! Go fucking die bitch. Never again I am taking her request.

If she has a problem then just speak it up and take it with leadership. Don't fucking be passive aggressive with me especially when I am not at fault and infact I am trying to help her.

And in interviews they ask people whether they are a team player or not.

!(isRant(thisPost));

Submitted my third pull request today in just a couple months as an intern, got told I'm doing a great job and already being considered to move to a more in depth dev team. Honestly a dream come true. Great company, great people, and I have a solid shot at a REAL full time dev position after college. I'm so happy man all that work finally paying off.

On today's episode of Corporate BS

I must please go update logstash on this server. Okay, so I literally just need to ssh in and run "yum update logstash"

No, I need to apply for temp root access and depending who picks up that ticket, I may have to log a change request

Every time there is a problem with API, the other team ALWAYS send sample request as image. I don't know if they are just mean or stupid.

I was thinking about how I implement login functionality, and realised I have no clue how I came up with it so decided to ask if it was a good way to do things.

Basically, client logs in, username/email and pass are sent to server.

Server salts and hashes password and checks it against the one in the database for that user.

If its correct, send the client the user ID and the user token. (User id could be username, or a number, it depends)

When that client makes a request, the request must contain the ID and token.

The server checks that the ID and token combo are correct, and because the ID is linked to the user we know who it is and can complete the request.

Usually I make the token a random string of 16 or 32 chars, each account has their own token, and it may be stored in the browser so they stay logged in. I also normally add a "log out everywhere" button, which essentially just generates a new token to overrides the current one, making any previously saved tokens invalid.

Callum, not everything is a "useless fad" just because you don't like it. I understand that you think AWS lambda functions are "just an expensive con for morons", but for our batch processing use case they really do make a lot of sense.

Running some numbers to show they cost 10x more for a completely unrelated always-on service with a completely different request pattern is either naive, stupid, or malicious, and considering you're meant to be a principle architect, I'm really not sure what's worse 🤦‍♂️

Just got a Google Home. I'm very impressed with it, there's just so many possibilities with it. I just found out I can trigger a HTTP request using my voice (!). So now I need to find out good use cases and build a server.

Ideas?

[vent]
I am java dev with 5 yoe at a place which has really good engineering talent.
Was assigned a feature request.
Feature request requires me and one more older dev(in age, not in exp at company) to write the code. My piece is really super complex because of the nature of the problem and involves caching, lazy loading and tonne of other optimization. Naturally it makes up 90% of the tasks in the feature request. On the other hand, the older dev simply has to write a select query (infact he only needs to call it since a function is already written).
Older dev takes up all the credit, gives the demo, knows nothing but wrongly answers in meetings with higher ups and was recently awarded employee of qtr.
It looks as if I do the easy work whereas he is the one pulling in all the hard work.
Need advice to justify my work and make others realise it's significance, nuances of area and complexity of it.
Do not expect monetary benefits, just expect credit and recognition for the worth of work I am doing.

PR used to mean public relations to me few months back. Now it just means pull requests to me.
The fuck happened. Anyone says we need to improve our PR, I'm like how do you improve a pull request and I end up face palming

Been engaged in a silly-client-request VS stubborn-developer war since last week. They wanted a textbox where they enter decimals - generally in the form 1.234 - to automatically put the decimal point after the first number.
"What if it's 10.xxx or 100.xxx?"
"That won't happen"
"How much time will it really save them having to press another key?"
"Why, how long will it take you to do the fix?"
Etc, ridiculousness and rage increasing exponentially...
Common sense finally prevailed today. Just think of all those wasted milliseconds having to press the "." key.

The last communication we had was me asking you if you would like a service for that, with no response? And now, ten days later, you’d like an update on when it will be available?

Well I raised a pull request on your side a week ago, your developers have just been ignoring it.

What? No, I don’t know when it will be merged and ready.

So I go into Google Search Console to try to determine why its saying pages are not compliant with mobile and whatnot.

3 hours later I come out realizing that what Google REALLY wants is for everyone to build every web page as static HTML with no script tags and never a call to an external website. Just dump all that javascript and css and HTML into one BIG FRIGGIN FILE so our crawler feels satisfied that it's loading everything all in one request.

No CMSes allowed unless GOOGLE built it.

Let's just all revert to HTML 1.0 and be done with it.

Client wants some CMS text to be automatically translated. So I checked and Google seems to have a solution for that. I thought to to be as simpel as doing a request and parsing the response. That's how API's work, right?

No. First I must create an account, that account must have a credit card, then I need to setup credentials, the default ones working with path variables, an API key... etc etc etc.

I feel so stupid for just not understanding their docs. I'm just a dude that installs a CMS and makes pretty CSS for it. I've worked with REST APIs before (Mollie, Carerix) but none of them ever demanded the level of knowledge and setup the Google Translate API demands.

Am I just a bad developer or is this shit just too complex for your average web developer?

Just wanted to code some better public transportation route calculator (better ux) and found out that the pt company offers an API.

EVERY FUCKING REQUEST HAS TO BE SENT AGAINST THE SAME FUCKING ENDPOINT IN A POST REQUEST WITH THE ORIGINAL REQUEST AS FUCKING XML IN THE FUCKING BODY. At least they offer xsd files... BUT THATS NO FUCKING HELP. At least not that much of a help. AND THE DOCUMENTATION DOES NOT STATE A SINGLE FUCKING EXAMPLE OF HOW TO USE THAT FUCKING ENDPOINT. I FOUND THIS OUT BY SENDING RANDOM REQUESTS TO THE ENDPOINT TRYING TO REVERSE ENGINEER THE EXISTING FUCKING FRONTEND AND NOW I NOTICED THAT 80% OF THE FUCKING DOCUMENTED FEATURES ARE DISABLED BECAUSE: NOT FUCKING SUPPORTED!!!

MAAAN WHY DO YOU DO THIS.

Alternatively I'd use the GTFS files they provide but THEY ARE FUCKING INCOMPLETE AND DONT STICK TO THE EXISTING STANDARD GOOGLE DEFINED... They also offer a different propietary format... BUT THATS FUCKING UNDOCUMENTED AND FUCKING INCOMPLETE...

Just read a feature request which asked for full-app localization. The dickhead closed the request with the comment: 'since this is a small request it should probably be added to the top of the wishlist, besides you are a dutch company anyway'.

The nerve on some people

I once asked our graphics designer to send me a 1x1 transendent pixel as an image. She was just filling that role at the time, not being an actual graphics designer, and the request was rather unusual. It took us a couple of attempts to get what I wanted. I like to optimize memory for the apps, maybe a bit too much.

We've recently employed a new lead dev that seems to have a problem in that his solution is always the correct solution.

On a typical day, whenever I push code up for review via pull request, every single ticket I work on, he has something that has to change which doubles the amount of time of each ticket.

I'd be fine with this if the other 2 developers also think he's a bit of a headache in terms of his opinion but a lot of the time, there is always.. ALWAYS something that has to change because his method is better than mine.

For example, just now I pushed up some code that literally just adds in the user's email to the view which is already in the store for that action/effect anyway. I added one line of HTML.

He comments saying that I need to change the way it gets the email by doing a different request in the effect, to get the current user id, and from that match it against the email address, and THEN display it in the view.

This ticket took me 5 minutes. He's making me make it 30-60 minutes (to understand his requirement and implement it).

Is this normal? Am I over reacting?

Opinions please!

Hi guys, I’m that good guy MIS who knows a little bit python and got “promoted” to write a warehouse management system in C#, which I have never use it before.

Just now I submit my first pull request to DevOps and got accepted.

Just a small EF core and barcode generators stuff but I’m so glad I made some progress 😬

I'll try to pay back some smaller credit by one large credit...

Hence I need to contact the banks and get one (!) fucking frigging stupid piece of paper which lists the account number and the amount of money I need to pay back.

Sounds simple ...

Well.

One bank just answered my email request by sending me that piece of paper. Except they didn't have any validation of my identity.

Yes. They answered the request of 'I want to pay back the credit in full, can u send me the necessary documents?' (more formal of course) with confidential data without any more credibility than my email address.

YAY.

Another bank requests a telephone call for identity validation and sending back a signed form via postal service...

Another bank just needs a PDF sent via mail with an electric signature (yeah. They were aware of what that means - I was shocked and confused) or a "qualified signature matching previous documents" (translated from German).

The last one offers a WhatsApp number - send a GIF / JPG or video and we answer directly.

I need to reach a higher state than drunk.

It's not funny to know how confidential data gets mistreated by companies who should have the highest security.

love it when client supports comes to me and tells me the entire conversation they had with a client when i just need wathever request they had. i could have been done with this feature in the time you took giving me 90% useless information.

Worst fight was at a former job. I complained about a senior-level employee who made unprofessional comments about me.

I asked followup questions about a request. I was told the request was correct. Turns out the other employee half read/didn’t read my question because she decided I was trying to cause trouble. When my boss reviewed my work and asked why it looked weird, other employee actually wrote in the JIRA comments “Oh, my apologies. I thought [name] was question the request. [name] changed the wrong thing.” She said the silent part out loud. And the wrong thing she accused me of changing…the website always looked like that and my boss told her so. (Also, not the first time she forgot what the website looked like.) But my boss didn’t make any JIRA comment about the “questioning the request” part.

My boss was really downplaying what had happened. Like other employee just made a mistake. That wasn’t a mistake. He wasn’t going to bring it up with other employee’s boss. It was weird because the incident was a written conversation so it was really hard to deny the facts. I also had the original email notification in case she tried to go back and change her comment. I think my boss either wasn’t used to defending his direct reports or didn’t have the power to do so since most of his department (including me) was slated for layoffs in a few months.

Well, I got the last laugh. A week later, I received an offer. I put in my notice during the company’s busiest time of year. And my boss actually asked me to extend my notice by three weeks. Really?! Expecting me to forgive and forget that whole “questioning the request” incident. I stuck with my original date.

Just reviewing a critical pull request in one of our production apps.... wait, what?

receive multi year old confused bug/feature request from a former CEO

why

are there not other people who can immediately answer the questions instead of playing broken telephone when it arrives to me, to go find them

do you not have better things to do with your time and other directional priorities for the company or should i really muck around this low priority thing?

i guess i just lack the CEO M I N D S E T, also the compensation package

What is it with non-technical managers, especially those in sales, thinking that the solution to all problems is to "just pick up the phone and ring them?" This was *always* his opinion, whether the web service we were using wasn't accepting a valid request (apparently this was best "explained over the phone", I kid you not - have you ever tried speaking JSON?!) or whether we just needed a simple request going in to increase the API limit. I mean I could send an email or log a ticket in a few minutes tops, but you want me to spend 2 hours on hold to a support department only to be told "ah we don't take those requests over the phone, here's the URL, log a ticket."

Then it's always a case of "I don't understand why they're like that, all the guys I speak to are happy to help on the phone". Yeah, beacuse you're in sales & marketing you muppet. Blathering on to each other so you can stroke the egos of yourselves and your companies is kinda in the job description.

Grr. This was all a while ago, but I thought of it just now and the pure concept just annoyed me, so here it is. I really hope he's not doing the same thing to guys under him now (but let's be honest, he probably is.)

Run test
everything ok
Run again
everything ok
Run again
error
Run again
everything ok

*wtaf is happening?*
I googled for the cause of a "double callback" error and found out that supertest was throwing it when I was attaching a file to the API request. found no conclusive way to solve it, just that "supertest does it from time to time".

Trying to investigate further, I made a function to repeat the API request 5 times in a row. Everything passed. The run it again. Two failed. Again and everything passed.

this is bullshit

fml

I forgot the fricking ON clause for a important database query. While it didn't crash MY program or greatly effect the performance, I feel sorry for the API that had to deal with the idiotic results of this.

Especially that one request I just spotted, where I just got the answer "the query took too long". That one was like querying the table "females" for males.

Soo fricking sorry 😭😭😭

!dev

So my boss sent me a facebook request when he used to work with me. He is young, good looking. I kind of had a crush on him.
I didn't like that he sent me the request (he's friends with everyone in the office) but I accepted as it didn't seem a big deal.

Now when he's gone, I sent him a request on another social media( thought it will be safer now), that guy just ignored the request.

Seriously what's wrong with these people. (or with me)

I would like to call out the moron who decided to control docker through HTTP when the maximum time the server can take to finish the task is longer than the HTTP timeout.
If you expect things might time out, you don't use a HTTP request. You use a resource and poll it, or Websockets, or possibly SSE.
Shoehorning your API into a frame that obviously doesn't fit doesn't help anyone. Just admit that you don't know what HTTP is and use a regular TCP socket with regular pings.

I tried to get this trainwreck of a middleware running again. Generations of imbecile devs turned this once ambitious project into a dumpster fire. I had some feeble hopes. Wrote a little framework to get this braindead architecture back on its track. BUT EVERY PULL REQUEST I GET TO REVIEW SHOWS THEY DON'T CARE. FML! Why am I even trying. I should have known these morons just want to pour gasoline onto an already blazingly burning software. GODDAMMIT SHOW SOME ENGINEERING SPIRIT. Why are you even in this industry in the first place?

Just got a request to print the new Tesla truck.

I think it wasn't that hard for the Designer to implement the low pol. Design for the 3d print :')

The moment you realize that you have successfully beaten reality with your unit-tests...

There are unit-tests for ...
... the api returning a 408 Http StatusCode when an internal request times out.
... the react app take this status-code and fires an action to display a specific error message for the user.

Every bit of code runs just fine.

Deploy this hell of an app on the server. Dandy Doodle.

Do a smoketest of the new feature.
FAIL!
Chrome starts to crumble during runtime. The api Request freezes.
Firefox takes the 408 api response but fails to interpret it in react app.

So I began to wonder, what the hell is going on.

Actually I recognized that I had the glorious idea to return a clientside error code in a serverside api response.
Glorious stupidity :/

Finally I fixed the whole thingy by returning an 504 (Gateway timeout) instead of 408 (Clientside timeout)

Cheers!

I was hired as a wpf dev for a large scale project and I was told that the backend is perfectly complete and that I am able to work right away, then after I started working, I noticed that every request I sent was returning a 500 internal error, I thought it was a problem on my end, but later I found out that they didn't even implement the api yet, it was just a "reference" for devs, which basically means that I should work and give them a perfectly functional app without testing anything at all.

So I'm working on a project that relies on Google apis specifically Maps. What I just found out blew my mind. The company that writes documents about how you should return correct status codes doesn't return correct status codes. If I send a request with a proper API key, I get a 200 okay back. If I send a request with an invalid API key, I also get it 200 okay back

Why can't PMs do a basic user research before wasting the engg effort on building a product they don't even know what to build?????
Everytime my team completes a feature, request comes in to change it because end user does not want this. And when I take a stand to not proceed further without proper UXR, upper management forces me to go ahead without it.
I am fed up of these folks sitting at the top and being childish just to satisfy their own ego.

How do you clean up branches while working with PR ?!

It’s a nightmare. For each “bug” or feture there is a pull request created. As far as I know you MUST create a branch.

It’s easy to clean up GitHub (I’m just deleting branch after accepting PR. Which actually doesn’t even delete it for X days or something).

But local branches. OMG. It takes me at least 10 min/week to clean up and some of our devs don’t bother. They literally have 50+ local branches.

How do you manage that ?

I’m just about to write a script which deletes every local branch except selected (Yep UI with list of branches). But seems like overkill.

Have a friend who wants to enrich his coding portfolio but is scared of people copying his more serious code if he puts it up on github.
Told him it's all about open source and he could just keep the more casual code up there while giving access to serious projects on request from a company, but it's not very ideal, is it?

What would you tell him?

To the guys that develop any form of hybrid applications, is there literally no js templating engine that accepts template files as its base? I could write probably a single file that just returns the template and then all the others request it before templating, but seriously, is there no ready to go solution?

@dfox @trogus: feature request: is there anyway to store on my profile a list of recently viewed rants? It can be for private use only.

There have been a bunch of times that I will be viewing a rant, go into safari to grab a link or find a photo, just to go back to devRant and iOS has reset the app and I can't find what that rant I was looking at. It's really frustrating.

I know getting iOS to keep the app state may be difficult but storing a list of recently viewed rants, while not the simplest, I would think is straight forward.

I started working as back end dev and I was given a pc sadly with no admin rights (which I neede oc) so I happily requested them to IT services. After 3 weeks of waiting got a msg telling me that the script for giving me admin rights was not working so they had to send the request to the next lvl and bla bla bla.
So... I called them. A really nice guy just connected to my pc, used an admin resque account and added my user as admin (2 mins) et voilà. 1 month of waiting for a 2 mins shet. Hate big companies...

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

Spent months building a full regression testing framework app at the request of my boss...

Now he just says need a simple app to test a few static URLs...

I could've written that in 1 day... FML...

And now I've been pulled away from the main thing he wanted me to work on...

and keeps asking if it's done yet...

An asynchronous service in android which sends an Http request to a webpage to store its content every 3 seconds regardless of its response, and runs forever?

What the fuck where you thinking. You just killed my phone!!

Requests to a soap server were failing randomly. In order to contact the API provider, I tried to provide an curl example with the same payload and the error response. Yet when sending the payload over curl, the request worked just fine. When my application was building the request, it failed.

What. The. Fuck.

I checked and double-checked the request body and headers. They were identical.

Of course, no error response was returned by the API provider and, of course, they could not tell me how what error I caused in my request.

So I created a basic dummy server, installed wireshark and compared the payload when sending a request from my application and from curl to my dummy server.

It turns out: curl, if called in a certain way, automagically strips out newlines. The soap client kept them.

So that that shitty soap server crashed due to newlines in the message body!

Stripping out the newlines was rather easy.

Shame on you, your house, and entire family for letting it crash due to them!

Starting to feel burnt out. Past 2 days have been a struggle to be productive. And it's been a week since I've bothered turning on my 3d printers to try and make anything fun or even just tinker

Once my manager is back I'm gonna request a week off for the soonest he'll approve. Hopefully that'll help. Probably will just video game and read that week lol

Why do Apple have to hide the ”request desktop version” button behind the refresh button on the Ipad?

I get Idea. They problably thought it like you refresh as desktop site. But it took me ages to find out how to request desktop site!

Why cant it just be like chrome and have the settings and tools behind a menu where everything is.

And this is just one of many of Apple products flaws! Shame on you Apple!

If you wonder why i even use a ipad it’s because it’s a school ipad that is locked so we cant install apps.

Question: Does using cookies for user session handling hinder the scalability of your backend because all the API's have to live on the same domain. Basically if one API starts to get a lot of request and you want to add another server to off balance the load you would have to add an entire webserver rather than just a small micro webserver with the API running on it mainly because cookies are used to authenticate user request and cookies don't survive CORS request. Am I right or don't know what the hell i'm talking about lol need some opinions I suggested we make all API's micro services and use JWT for user sessions

I was reviewing a Pull Request recently and there was this line
`return josn(202, 'Record does not exists')`

I told the developer that, status code and description does not match.
He just did not want to accept that he was wrong and told me that, since this function is not exposed to public, it does not matter.

Whats wrong in accepting that you are wrong. We do make mistakes, consciously or unconsciously. Huur. I regretted reviewing his codes there after.

Stack Overflow people have profound buffallo bullcrap on their skulls, they are some software engineers who have fucked COBOL and BASIC, probably somewhere like NASA, just pondering out where someone post a question. They're probably some etilist cult banging a prostitute while delivering that awful downvote imitating the slap they give the chick during sex. They desire questions such as

"RANDOM_fuck_module_Abdul.method() not working in python" or "how to dock the dock by undocking" (tagged: AWS). Not things like "why does the audio tag not work in a PC but works in w3school tester?" or a genuine programming question. Fuck.

We don't tail recurse or loop abc for k in godfuck loops, huh? We make simple things as: a form, a http request to dell.

I hope there penises get rotten in the hell. Period.
this is just a part of SO.

So today I was having this discussion with my colleague regarding a messed up pull request.

Me: are you done merging the remaining branches into master?
Colleague: no, I'm still merging the changes manually.
Me: but why?
Colleague: because the changes will overwrite the changes in master.
Me: but how? It will just conflict and you can keep whichever changes YOU WANT. You can even edit before committing the merge.
Colleague: I'm just redoing the changes manually anyway.
Me: -_-

When you bust your ass developing a site for a client, bend over backwards with changes - pushing the rest of your extremely large queue further and further behind, just to come in to a cancellation request from someone else at said company. 😡 We had really good rapport and the site looked amazing, and all they give me is "we're going in another direction". 😡 Why do people so this when the site is already finished?!? So rude! Before you comment telling me to charge upfront next time or whatever I work for a huge company so none of that is in my control.

Contrary to popular opinion, I still firmly stand by my belief that you should thoroughly study something in-depth before you attempt to do anything serious with it. Failure to do so will have an enormous cost of waste of time attached to it.

Here's an example:
I was using AJAX to post a multi-part request containing a file.
Now here was the problem: no matter what code I forced in the backend, the browser would in all cases refuse to prompt a SaveFileDialog (and I had turned on the option in the browser to ask the user if download). This took me two entire days and at least 100 Google queries and several RFCs to figure out.

From StackOverflow:
The cause was simply that you can't (typically) make a browser prompt a SaveFileDialog via an AJAX request, even if you set the necessary headers. Why? The browser will just dump everything back into the XmlHttpRequest object..

If you make a regular request with Content-Disposition: attachment; and so on, then it works, but yeah, not with an XmlHttpRequest.

Conclusion:
Had I better studied the HTTP spec, networking and AJAX in-depth, I would have instantly known what the cause was.

I just reviewed a pull request with a test case like (pseudo code):

# Test MyService

const mock = createMock(myService.myMethod)
.whenCalledWith("foo")
.returns("bar");
assert(mock.myMethod("foo") === "bar"));

Why though? Why are we testing the mock? What is happening here? This test has no reason of being there instead of a fuzzy feeling that we now have unit test to lure us into a false sense of security.

I asked why we don't do an integration test. Response was: "They are slow."

Well, duh, but at least they would actually test something.

What do you gain by asserting that the mock is working the way you set it up?

I just built a website with Hugo. And I love it. Got a request for a certain set of pages but because of the workflow the one thing I could dynamically load wasn't worth a whole wordpress site.

So I built it with Hugo instead. I played with it a little last week so I could get around but I got good this week and damn it's powerful.

I think I'm in love. I wish more projects at work could be built in Hugo.