Status code: 200
Content-Type: application/json
Body: {"error": true, "responseCode":400 }

I know I am that kind of user 😂

"Float like a butterfly, sting like a bee."

Rest in Peace, Muhammad Ali.

“It’s okay, you can go, the pain will be over soon, thanks for everything, I love you”

I never thought saying these words to my cat would be so hard.

I’ll miss you.

His legacy lives on
Rest In peace

Rest in peace bro ..!

Client "Can you change your API? If a POST return 201 ours system crashes reading it"
Me "Your system WHAT?????"

*Caps lock* *letter* *Caps lock* *rest of name*

Meditation for the rest of us...

Time to rest

Because,
Things in motion tends to stay in motion, while things at rest tends to stay at rest.

When you start wiring your api and front end together...

May your code rest in peace!

The CEO at the company I work at has been telling our partners that our PIA is ready. It took me a week to figure out what the hell a PIA was but he actually meant API

That moment when you finished your first REST API 🎉

And you realise all it can do is useless ☹️

But then you realise, you can extend the functions easily with you new knowledge 🎊

Man, this emotional up an down is exhausting 😆

For some reason, people like to show off their mostly-samey linux desktops.

Here's mine.

aaaaaand I did it again:

if( !txt.getText().length() != 0 ){

}

I'm done for today

Should i need rest for a moment?

I have my doubts of being a good developer when my fingers type this thing

Just checking if a string contains itself

i rest my case....ask no more..#programmer

"What technologies do you know?"
"I can write pretty URLs that return JSON"
"You mean REST?"
"No, I mean pretty URLs that return JSON"

Now where's the rest of your face octocat..

REST is important for developers 😊

So Twitter apparently used http status code "420 - Enhance your calm" to notify the client that it was sending too many requests (basically chill the **** out). Note the status code number as well 😁

Image from wikipedia.

A late rise up *check*
A good cup of tea *check*
A nice breakfast *check*
A rainy day today *check*
A bunch of time for reading
a book and playing with
python and elixir *check
Nobody seeks me for
tech support *check*

Did I die and go to heaven?

New favorite image for the rest of 2017

Client: "Hey we want you to integrate your product with our system."
Me: "Oh, OK. Where's your API?"
Client: "Here! We even have an outdated .Net SDK, we use XML."
Me: "Ok.. how do we authenticate? What's your OAuth 2.0 endpoint?"
Client: "O auth what?"
Me: " You know, the current standard for REST API authentication and authorisation"
Client: " What's REST?"
*Hungs up*

There are 3 types of people
Arch based Linux
Debian based Linux
The rest of people

.. when you're exhausted with trying to get your code to work.

Rest in peace, Avicii.

FUCK!!! FUCK IT ALL. FUCK YOU AND YOUR CRAPPY BULLSHT UNDOCUMENTED AND OUTDATED API.

YOUR DATABASE SERVER BACK-END HAS TO BE THE ONE MANAGING THE DISPLAY DATA FOR ITS WEB AND MOBILE CLIENTS. NOT THE OTHER WAY AROUND, DAMN IT.

I'M NOT GONNA SIT HERE ALL DAY HARD-CODING ALL YOUR SERVER'S INADEQUACY.

MAKES ME WONDER DO YOU EVER USE DESIGN PATTERNS OR APPLY DESIGN PRINCIPLES? DRY AT LEAST? DON'T FUCKING REPEAT YOURSELF, DAMN IT.

I CAN'T WAIT TO LEAVE THIS PLACE FOR GOOD.

HTTP 200 responses on failures… 😒

Anyone else who belongs to rest 14% ???

That moment when u created a project and quite some folks forked it and continued their own versions, but then you realised that you've made a little mistake back then so now your dumb code propagated across humanity.

¯\_( ͡° ͜ʖ ͡°)_/¯

No SOAP for the RESTed.

That moment you leave the office for the last time in 2018.

FAWK YEAH!

What a year it’s been, from learning new platforms, to developing never ending changes, to breaking production at Christmas time, and finishing the year at the peak of purchasing period on a couple of websites with no reason to care what happens for several weeks all while absorbing extra projects from resigning co-workers.

*Turns on autopilot and walks the fuck out*

From one exhausted dev to the rest of you, enjoy the holiday break!

Rest in peace old friend :(

You know what makes sense? Having a reCAPTCHA on a REST API.

!rant !!joke

What is written on a dead API's gravestone?

REST in peace.

Why in God's name would anyone use SOAP over Rest......

Because it makes you cleaner hahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahaha

Why on Earth would an API require me to provide input like this?

{"this": "{\"is\": \"not\"}", "how": "{\"json\": \"works\"}"}

😡

DevRant discussions at it's best.

Rest in hell IE8, 9 & 10

Looks like the recruiters are using their brains RESTfully !

Most irritating thing I have to deal with when working on a project with a third-party:

{
status: 200,
message: "error"
}

Currently working on the privacy site CMS REST API.

For the curious ones, building a custom thingy on top of the Slim framework.

As for the ones wondering about security, I'm thinking out a content filtering (as in, security/database compatibility) right now.

Once data enters the API, it will first go through the filtering system which will check filter based on data type, string length and so on and so on.

If that all checks out, it will be send into the data handling library which basically performs all database interactions.

If everything goes like I want it to go (very highly unlikely), I'll have some of the api actions done by tonight.

But I've got the whole weekend reserved for the privacy site!

Puns for days

Simply the best
Better than all the rest

What's the point of using a framework if you don't use any of its features!? What the heck, I have to fix this damn web frontend that is so broken in many ways.

Instead of using an authentication middleware, every single view has the same block of code to check if a user is authenticated. Instead of templates, they used static HTML/JavaScript files and they passed data to pages through cookies.

The "REST" API is so messed up, nothing is resource-oriented, HTTP methods are chosen randomly as well as status codes. They are returning "412 Precondition Failed" instead of a plain simple "401 Unauthorized" when you're not authenticated! What the hell, did they even bother to check what 412 is about when they copied and pasted it from a crappy website!? I would never come up with 412, not even in my scariest nightmare.

What kind of drugs were they using when they wrote such code? Oh dear, I need a vacation...

Hey, thanks for teaching me JavaScript and HTML. I almost feel like a web developer now.
What about the REST?

Just found this piece of code from one of my coworkers:

restMethod() {
try {
// some complicated logic
} catch (WebApplicationException e) {
throw e;
}
}

Why?!

And btw: Hi fellow devRant ppl! 👋

Yesterday I received the API documentation from an external company. Over half of the endpoints are either wrong or send invalid data and even the given test requests are fucking failing.
It's a nightmare. We have to finish a website until friday and that company did nothing for 2 months and now we have 2 days left.
The sheer incompetence is too damn high.
My boss said it would have been much better if we had implemented the API on our own. Damn right.

I am roughly 12 hours away from a deadline that seemed pretty impossible.
I finally got everything to work, it seems I'm actually going to make it.
After so many hours of frustration, despair and walking in circles, it is finally fun again :)

You know what's more irritating than working with a partner who doesn't understand how to properly build an API?

Working with one who fully understands the best practices but doesn't give a shit to implement them until something breaks.

I feel sad for some of my officemates. They are required to go to office today due to client support stuff, and it's a Sunday. They should be resting, be with their family/love ones/pet/bed, playing games, or whatever they want to do on a rest day. :(

What we think working with REST looks like but... 😁

I feel guilty when I rest during holiday instead of coding or learning a new concept.

This one py2 lib when the rest of the project py3

thought I'd check why I'm getting connection timeout on my app
I think the problem is me and not the code

That moment when I read "sass-loader" as "ass-loader" (҂⌣̀_⌣́)

Is it me or all REST api use json today ?
And xml is kinda dead ?

I always feel awful when I see an xml rest api.

Sometimes the best thing to do is to rest during a weekend and do an activity away from software.

Well that's my evenings sorted for the rest of the week

Rest in peace, Totalbiscuit 😖

Coworker:" ...so this openflow switch has a really great CLI tool that lets you configure all sorts of settings programatically such as..."

Boss: "I don't like CLI tools, they're too hard to use and can be unreliable. Before you do your task, can you spend a couple of weeks writing a REST API and a web interface to the network switch so you don't have to rely on CLI commands? I think that will be much better and safer."

Coworker: "Well, will you ever have to use it? I think I'll be okay with just the CLI, I actually prefer it..."

Boss: "No, the CLI is unsafe, please just write a REST API and get back to me in a couple of weeks."

Me: *dies inside*

The program they're using is closed-source. Any REST API will have to just make calls in a subprocess shell to the CLI binary.

There were just so many things wrong with the scenario I facepalmed my way out of the conference room.

This feature I'm building requires crossing over to a second application for some actions (fair, this reduces repetition), but the method used for it is kind of ridiculous.

To keep with the existing patterns, I followed suit, and added two PATCH and a DELETE routes, wrappers, and calls. (Typical CRUD + de/reactivate).

But. This freaking halfassed HTTP model doesn't support anything but POST and PUT! wtf. (Also, the various IDs, naming schemes, and required json data/formats differ across view, controller, and endpoints. but whatever?)

Two and a half hours later, and the feature is done and works wonderfully. Four times the functionality of the previous incarnation, and the code is only about 25% longer! haha.

Ahh, I'm complimenting myself again. (but somebody has to, right? 😅)

but really, when i want to get something done i'm actually surprised at how quickly it all comes together. Even when I need to patch API Guy's madness.

(and this time I actually found someone else's code in the mess! It was actually worse!)

I suppose taking a day off yesterday did me some good.

REST is history?? I don't think so.

Fucking IT and their self signed corporate proxy SSL bullshit getting in the way of anything that needs to verify SSL requests,
Fuck you for making my day a slow and miserable day and having to resort to forcing rest apis and SDKs to work over HTTP instead, all in the name of “Security”.

Rest in peace Chester Bennington 😢

I propose to consider the question, "Can machines think?"
-Alan M Turing

[Begin Rant] When you show your senior manager your REST Web Service and he says "Oh no nooo... I don't wanna see no code"... Me: Code?? That ain't code you fat silly fucker it's the command line output data which I spent a week parsing, batch processing, and storing into the database! [End Rant] :[

-Code all day at college
-Get home to rest
-Bored
-Back to coding all night

Sleep rant time!

As per usual, I got home late and tired, but wanted to keep on with learning to use Electron for a personal project. I setup everything, created the project and began to tinker with it.

One issue, the script I made was not loading, I spent like 30 minutes wondering why, reading docs (it was 12:40AM). When I was about to give in, I opened the index.html file and guess what? I IMPORTED THE SCRIPT AS A FUCKING STYLESHEET.

I laughed like 2 minutes, then shut the lid of my laptop and went to sleep and thought "Oh, so silly"

Would you rather only be able to use Internet Explorer for the rest of your life or only use Light themes also for the rest of your life?

Java dev here. I rewrote an app and replaced a system call to ssh with a modern jaxrs post for uploading a file and (new) some additional data.
I even used a stream.

1 hour in production, first client doesn't get his file. Log says OutOfMemoryError: heap.

Me: wtf? I already use streams.
Looking at the Jersey library. Docs say nothing. An issue from 2013 says: oh if you silly don't use the Apache httpclient addon, we disable chunking and buffer the whole body, because our tests fail with the jdk included http client otherwise.

Me: meh.

No warning in the logs. Thank you soooooo much! Who could have known?

!rant

I've been doing wrong these last year, so I decided to step up my game, implementing on my work cycle:

+ Testing
+ CI

It feels fucking great. If you're not doing it, it's time.

Dear brain,

I just wanna have some rest, please.

Nobody told you you had to make a REST API, but if you want to call it REST, please learn the basics of what it means...

Me: please return http code 202 in your http service.

My collegue: ok.

After one hour...

Me: you are returning 200, I told you 202. Let me see the code:

OMFG she was writing the string "202" in the response body!!!

I do not know how to escape from all of this shit.

So we have an API that my team is supposed send messages to in a fire and forget kind of style.

We are dependent on it. If it fails there is some annoying manual labor involved to clean that mess up. (If it even can be cleaned up, as sometimes it is also time-sensitive.)

Yet once in a while, that endpoint just crashes by letting the request vanish. No response, no error, nothing, it is just gone.

Digging through the log files of that API nothing pops up. Yet then I realize the size of the log files. About ~30GB on good old plain text log files.

It turns out that that API has taken the LOG EVERYTHING approach so much too heart that it logs to the point of its own death.

Is circular logging such a bleeding edge technology? It's not like there are external solutions for it like loggly or kibana. But oh, one might have to pay for them. Just dump it to the disk :/

This is again a combination of developers thinking "I don't need to care about space! It's cheap!" and managers thinking "100 GB should be enough for that server cluster. Let's restrict its HDD to 100GB, save some money!"

And then, here I stand trying to keep my sanity :/

Why the fuck does your API have to send 401 when the server is down.

Just spent an hour thinking something was wrong with my auth wrapper.

That moment when you've tried everything and nothing works and the only logical thing left to do is post a question on stackoverflow;
&wait;
&obviously rant on devRant while you wait;

So, I was getting started with express middlewares and installed Postman. I saw this. I literally cracked up laughing so hard at this.

Anybody else feeling it after Chester Bennington's death recently? I'm nearly 30 years old, so I listened to him a lot through my teenage years. Linkin Park was practically my favorite band back then. I'm pretty bummed out man. 😔

Damn.

I need some REST

I have discovered a fresh hell

Some guy I’ve never met or heard of in the office lobbed a comment at one of my *approved and merged* pull requests. He doesn’t say anything specific, only that my REST urls are not in line with naming convention. That’s all he says, and I’ve already walked the URL consumers through the code and given them the URLS.

I’m really annoyed that this guy won’t just say what he has in mind, but fine whatever this is a professional environment and developers are not known for being a diplomatic people. Let it go and get your work done!

I do some googling and find an obvious change that needs to happen- I implement it, open a new pull request and inform my URL consumers of the change.

This rando still isn’t satisfied and still won’t say what needs to change. I am on round 3 of this wonderful cycle and this guy is acting all fuckin HAUGHTY about it. “Here is a list of conventions I found googling, you should read them even if it takes 4 hours because it will benefit your career”

Sure dog you’re probably right on that one but we are in a professional environment and at this point you are holding up production so you can wave your dick around! Just SAY WHAT YOU MEAN SO WE CAN MAKE THE CHANGES AND GET OUR WORK DONE

A transaction level to match the rest of my code.

Unemployment week 2

I finalized buying ~1000 square feet ( ~95 square meters ) apartment. Still renting 100 square feet room ( ~10 m2 ) so change will be tremendous. It’s first property I will own. With that amount of free space I think I can start constructing small spaceship or time travel machine.

Typed on linkedin that I’m offline.
Phone is still ringing. Time to turn it off for a while and rethink my life and world around from scratch.

Rest is good for my soul.
Peace ✌🏽

Me trying to learn React & Angular

Finally got my dog's urn in. Rest in peace, boy.

I dread the day that Slack has a “... has read this message 2 seconds ago” feature. Please Slack, continue letting me pretend I haven’t seen that message that I don’t want to reply to.

I'm implementing some Italian web servicies.

The server response is "INDISPONIBILITÀ TEMPORANEA" (temporarily not available).

I'm Italian, but I'm not used with localized error messages. When I read this message I tought to a server in a toilet.

Neo: "Why do my eyes hurt?"
Morpheus: "You've never used them before... REST Neo, the answers are coming"

See; it was never SOAP!

Why soap when you can do rest? fucking why? 😠

"Our company encourages cryptocurrency big data agile machine learning, empowerment diversity, celebrate wellness and synergy, unpack creative cloud real-time front-end bleeding edge cross-platform modular success-driven development of digital signage, powered by an unparalleled REST API backend, driven by a neural network tail recursion AI on our cloud based big data linux servers which output real time data to our Wordpress template interactive dynamic website TypeScript applet, with deep learning tensor flow capabilities.

Don't get what the fuck I just said? Udemy offers countless courses on python based buzzwords. Be the first out of 13 people to sell your soul and private information, and you'll get the first three minutes of the course free!"

Made my first Node.js Todo list today! Got myself a new front end design tool, Bootstrap Studio (50% off). Learned about REST, using Node as an API and MongoDB and Angular! Had a lot of fun learning and I would recommend it to anyone that's a Node.js beginner. I want to do a video tutorial series on Node.js, is that a good idea?

Currently working on my first real REST api and I've arrived at the authentication part.

I'm not sure how to do this one, the client will have to login using username/password but then, what's the most conventional way of authentication logged in users through a REST api? (no oauth (yet))

This should be usable for anything like ajax requests to calls from the backend to curl requests.

Looking forward to ideas!

You know you're talking to a sales guy:

"What's the URL for your API?"
"Um, I don't think we have one."

Your body needs REST and SOAP both

~ Random

Sometimes you need to take a break.

How mac users perceive the rest of us...

That joy feeling when you are finally rewriting the backend and frontend with GraphQL instead using the fuckin old undocumented REST API who was written by fuckin amateur ex-coworker.

Better think for 30 minutes than to fix for the rest of development

A client's company will be sold, including the code we've had written for them. But it was the usual we-got-no-time project, so we cut the documentation.
Well, guess who has seven days left to add comments on a ~15k custom-PHP-lines project (RESTful Backend)
After that, some other Dev _might_ be able to understand at least something.
Also, I'm doing huge refactoring, improvements of code-smell and restructuring the whole project.
Maybe, our company stays as a development company for the new client but maybe not. So I'm paying now for being "lazy" two years ago.

up, up, down, down, left, right, left, right, B, A, start!

Me: I should make REST API docs
Also me:

My man said "What should I return if the True/False field is left blank?"

WHY WOULD A BOOLEAN BE ANYTHING OTHER THAN TRUE OR FALSE???!!!

I'm gonna have an aneurysm. I shouldn't be educating people on best practices for something that's already been written about time and time again. RESTful philosophy has been documented so much, and all it takes is a quick google search, but noooo! I have to take time out of my day as if I'm a regular old stakeholder to explain that I want the exact thing that I sent in an email two weeks ago. Amazing.

Okay, I knew one of my colleagues was actually a work freak, but to this point...

He's been working for most of the day yesterday on a school project, and so was I. Satisfied with my progress, I push the code with TODOs on things we had to agree on tomorrow as well as mentioning it in the issue associated with it on Git, with my last commit a bit before 11PM.

I wake up, with a ping on Discord asking me what was that "bug" I just pushed, wondering what editor I use and asking me if I even use the console debugger. Said "bug" was the point of discussion I said we wanted to talk about tomorrow, I replied in the morning. But he decided of the fix on his own and committed it, as well as other things until... 3AM...

Honestly, I don't blame him for choosing at our stead, he's the leader of our branch and the Gitmaster on top of that. I just reproach him to call it a bug, not see the issue, and all that while he could, you know, sleep. And get some rest overall.
This dude has been working himself madly these last weeks, where he did about 80% of what each of the team member was supposed to do in a whole semester (which amounts to 150 hours of work) for this project (we're nine folks on it).
Now I'm pretty sure it's how he works and that he still gets a decent amount of sleep (like I dunno, until 9AM or so), so I don't expect a response beforehand.

And indeed, as he woke up, he replied to me.

At 7:50AM.

!Rant

TLDR: What's your favorite REST API Documentation tool?

I'm about to start developing a really large REST API. I have never really had need to document my previous API's since they were small, self explanatory and had only me using them. Aside from this one being too large for me to keep track of there is also a remote team that will need to integrate with it.

Basically I need write exceptional documentation while using as little time as possible. I love postman and am planning to use it for documentation since I currently use it to test during development anyway but I have seen some really neat looking tools like swagger and apiary so I figured I would check for some other suggestions.

What is your current / preferred REST API documentation method?

Please stop calling calling rest to any json over http api. That's not rest, rest has its specifics details to be called rest.

The world: we found a cure for AIDS.
Hacker news: I don't see a RESTful api endpoint for that, so it's useless.

Since a few days I have my first dev job in a small it company. At my first day I directly stared to implement a rest api for managing dns servers.

Today I completed the prototype and all works well. What a feeling :)

Just spent over 5 hours trying to figure out Microsoft’s OneDrive REST api. Basically my first time trying to do POSTs n’ stuff. I got very very close, but the server kept throwing 400 error codes. Eventually I had to give up and ask Stack Overflow. Going to bed now at 2:20am. No worse feeling then not being able to solve a problem you’re dedicated on solving. :/

Api with no documentation and obscure endpoints

Does anyone know how to post a rant via their api. Trying to make a custom devRant app.

Dear API vendor,

Please get off your arse and learn about REST, OpenAPI, JSON Schema, XSD and basic documentation so that I don't have to guess how to use your shitty, inconsistent, RPC over HTTP service.

With Love,

Platypus

After fiddling with configuration I decided our application needs this header

Microsoft APIs documentation, best API documentation ever!

Why doesn't Twitter have a public API without authentication for simple stuff, such as reading tweets. One can do that without logging in on the website, why shouldn't code be able to do it.

“Don’t forget to go home”
A solution architect when he looked into my team room at 6:30 and saw me still sitting there working.

While some say REST is best !

Unit test works, unit test works... commit it, push it, take screenshot of it, and go to sleep... peacefully...

I don't use soap, I use ajax while at rest.

I found a great app on iOS that allowed me to clone my Git repo, make commits, change branches, it had everything! I made a small commit and went to push to the remote server, but then it told me that I had to purchase premium to be able to push to remote. I was kind of upset, but I went to check the price of premium, in case it was a few cents. Nope, $25 just to be able to push commits. Seriously? If I was at my computer I’d be able to do this for free.

Some designer told me: "I'm sending it in Adobe XD format. Do you use Adobe XD?"

I answered with a 😆

Maybe I need a pause?

I spent the entire weekend studying C#.

..Forgot I had a test today. Whoops.

So, first: I'm a bit of a perfectionist when it comes to code and love to think I know everything.

We had a group project at university and me being laid back but unknown to the other people, the "rest" of them was together with me in a group. We got to know each other and actually we were a pretty cool group. I guess "the rest" in a computer science course means you get the cool guys.^^

1/6 of us did ever code in C# and 2/6 even knows what an engine is and how unity works. I was in both sixths, got group leader somehow (if you'd know me from school. Omg. I was that one guy not knowing what went on, saying my two sentences at the presentation and took the B-.:D), so what to do to have a nice 2 weeks with them?
We did a crash course, I taught them some basics and everything.

The point is, i was hella nervous and i really get anxious if something is expected from me.

Long story short, I talked a whole week for 5-7 hours straight without real pauses and eating wayyy less a man should. Dude I was literally dead on my way home on friday evening. I felt like I would fall over any fucken second, i was all shakey, dizzy as hell, weird vision, everything. It felt like I was about to die on the spot.

I got home though, ate like 1/2 kilograms of pasta and felt myself coming back to life.:D

What to learn from this:
Keep the fuck calm, do pauses, drink and eat enough and don't rush all in for a fucken week without real rest..^^
It fucks you up and doesn't do anything good for your productivity.

We got an A btw, so in the end, all went good.(:

Anyone here has an idea of a project to do in Java and Spring (REST stuff) ?
I'm out of ideas :/ and I really want something to build in Java and keep me busy for a while.

You do too much web-engineering when you read / sing the wrong thing...

Rest in pieces, youtube

I didn't rest this weekend and it's Monday already.

Right now, whether you're making money or not, try and make sure you take some time for yourself. Whatever you like to do: take a walk, exercise, meditate, or even sit by the shore if you live close to the coast. 🏖️

Interviewer asked:

SOAP or REST Which one you used..?

Does devRant have some REST API like twitter?

Fellow devs. I think there is something wrong with me.

My eyes hurt everytime our backend guy gives me a new REST API to implement in our app and always the formatting of the json is something like this. Like why can't you just fucking format it properly so I won't have to look at my code and feel disappointed for writing such ugly code. All because your lazy ass didn't care to understand the fundamentals of how json objects and arrays work !!! It's been a month since I've joined this company and I'm tired of explaining why we should use the status code for failure checking and not this stupid pass/fail status flag. I don't even remember how many times I've brought it up but everytime I get reasons like "Dude, you know what our server is never going to go down or fail so it doesn't even matter". And at that point I feel like I shouldn't even argue with him anymore.

What idiot uses 0 for a success response!!! Integrating with a 3rd party I found a bug in our code that uses the default value for an int when the external server can't be reached.

As it happens 0 is the default integer in most languages so no surprise when our system accepted the 3rd party as a success when it blew up 😒

I just learned the concept of this thing called REST API and now here's GraphQL showing up on me face. Mother fucking web development hell. BRB. KMS

Started Learning django rest framework. Yay.

When the whole api is using just GET requests, even when updating

Took company's laptop to vacations, because it's lighter then may gaming laptop rig.

VPN works seemlessly, all my intranet work is accessible even away from the country >.<

I guess I'm a bit of a work junkie / bitch ?

We are switching to an infinite scroll mode for our app. I told the backend dev in my project (we're just 2 people) I need an API to get more than one post at once.
He told me to use a loop to call the old URL 15 times.
...Not sure if stupid or just too lazy

friendly fish... makes a good neck rest :-)

JFrog Artifactory uses HTTP POST for updating and HTTP PUT for creating.

... I'm correct to be offended by this yes?

Robots that build the server's and devops for the rest. Truly full systems automation

I hate discussions about how to name resources in a REST api. It’s not like there will ever exist a client that magically knows your conventions. At some point, you need to hardcode an URL in a client/browser. That’s fine, just keep it simple.

This has been a great source of bike-shedding in my job recently.

And don’t even get me started on HATEAOS...

After a huge hit of a long term burnout explosion that affected my life and self confidence in many ways, I've decided to focus on video and photography and leave my restless programmer side to rest a little bit. It's been around 25 days without touching on a single line of code. Never stopped this much in my life. It's weird.

RESTful API Question

Let's say when a user do an action, I need to insert a record into a table and then update a record in different table.

Should I write two API routes (PUT, POST) or one route (POST) ?

fuck sockets, all my niggas query rest endpoints with setintervals

I have been sitting in front of my laptop for 4 hrs without getting up with full concentration and now all I can see is black boxes wherever I look.

Learn Vim and rest of your dev life is magic!

Spent the day refactoring a REST app into graphQL, that feeling when all tests are green and everything is committed and merged 😧🤓

Public REST (-inspired) API. Should I skip numeric IDs because it's easy for consumers to snoop around?

Example:

POST api/foo
201 Created api/foo/69

Uh, I'll get 68 just because I can. Hopefully it returns Unauthorized, unless we some kind of bug.

Is it just security by obscurity if I use, like, guids or something instead of sequental IDs?

I need to encrypt some large files at rest and then decrypt them immediately prior to processing.

App and files are on a Linux system (CentOS). App is in C. Machine is controlled by a third party.

What encryption libraries would you recommend? And, is there any clever way of managing the decryption key beyond compiling it in the code and doing some basic obfuscation?

Are they fancy obfuscation libraries out there, for example?

And, the reason I'm not going to SO (well, one reason) is that I don't want to have 50 answers that tell me that's it's impossible to 100% protect data on a machine you don't control. This I understand---just looking for "best effort" solution.

Tonight I rest well...

When there is a blizzard and all local buisnesses shutdown, kids are stuck at home, and the doors to the office are locked but the CEO sends out an email reminding all software developers to remotely work from home as long as they still have power and everyone else gets paid time off due to the weather.

Left what I like doing the most, i.e. Coding, R&D stuff and started studying German trying to travel and continue my studies there. Really frustrating to do a task you don't love continously without breaks lol. Anyway yesterday opened up my gaming rig. started steam. opened Path of exile to play after a really long time. 17 GIG UPDATE. quietly closes pc. starts crying in a corner.

Abstract ReST endpoints with nested resources

stackoverflow is down developers rest in peace.

Have you worked with GraphQL? Saw it for the first time and it looks like a pretty good tool for working with APIs, to me. I am excited to read your opinions about GraphQL.

Rest API not working since yesterday

:( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :( :(

In Django code, looking at a class for caching REST calls. The cache is using Redis via Django's cache layer. In order to store different sets of parameters, each endpoint gets a "master" cache, that lists the other Redis keys, so they can be deleted when evicting the cache. Something isn't right, though. The cache has steadily increased in size and slowed down since 2014 even though many events clear the whole thing!

... And then it hit me. Nothing empties the list of cache keys. Nothing. So it has been growing endlessly since 2014. And everytime it grows, cache eviction gets a little more expensive, network traffic increases a little more, and cache evictions get a little slower.

Fixing this bug took things that were taking routinely an entire minute to complete and made them take a couple seconds.

Developed a very simple REST api with pure php. Eventually "api/users/" worked but "api/users" was 301 moved!!.. it was a big problem

I'm implementing a RESTful API to display search results based on a huge number of parameters. There are so many of them at this point that using a HTTP GET method feels quite cumbersome.

I was wondering whether it is okay to use a HTTP POST method to POST these parameters all at once at every request in exchange of a result set instead of bothering with so many GET parameters.

Some of these GET requests are even blocked by certain firewalls for being too long.

So this is my first experience of shitty code written by colleague

God, for REST API she used ?id=<int>
Not only that,
if the route was /cms

she used GET method for /cms/get/?id= to get single record and
/cms/getAll again in GET method to get all records

Damn

Trying to integrate with sales force API via oath2 has made me lose all confidence in myself as a programmer.

At my office rest room 😎

I fix one issue there 😍🤟🏻

16 files (!) to create a rest endpoint that does nothing (returns an empty wrapper message).

WTF spryker? are you fucking kidding me?

This morning me and my colleague had huge debate about using GraphQL or REST. While I was in total favour of GraphQL, that guy was more on REST side because he read some random articles on dev.to and medium and was highly motivated to use REST instead of GraphQL.

The problem is, some people write anything on blogging websites without even doing a proper research.

Since, I have worked on GraphQL, I knew it's pros and cons very clearly and what are the things that can be done to solve them.

The guys said that we can't do native caching in GraphQL at which the lava from my head just got burst out.
I showed him the official GraphQL docs where it was clearly mentioned that we can do caching in GraphQL.
Poor guy couldn't say anything after that.

P.s: We are still going to use old school REST APIs but I am happy that I could prove my point. I'll use GraphQL in my side projects anyway, loss for him if he's not exploring something new.

WHY THE FUCK DO YOU FUCKING RETARDS USE TWO DIFFERENT AUTHENTICATION METHODS FOR THE PAYMENT AND THE CHECKOUT API AND DON'T EVEN DOCUMENT THIS SHIT PROPERLY!! 🖕

rant == false && help == true
I usually don't like posting non rant stuff here but I need help.
How do you usually design your service communication class?

I am working on a mobile app which contains talking to a REST service, I usually put all network calls in one class. Down side if it becomes a big class it becomes a pain to maintain. Any thoughts?

For a backend service I usually go with Repository design and it is working out well for me. But for mobile Apps I'd like to see if there is a better approach

Spilled tea on keyboard, 3 buttons doesnt click, rest feels different, fml.

I been using digital ocean to host my server for a project, but they seem to get shutdown because of DoS behaviour. I have no idea why. The server is doing some soap and rest communication and controlling a database.
To be fair the password was poor, but it was meant to be a fast way for four people to work on it at the same time.
But after the first shutdown, we rebuild the server and work on functions. Finish the work and went home. But in the server 9 hours of uptime with 2 of them unsupervised it was detected as DoS behaving server.
💻🔪

Programmers and all the rest...

Can't decide if I should join this nice internship or let myself enjoy this summer and rest a bit, as I burned out a bit this semester with studying and freelancing.

Why is it so difficult to decide..

The internship is at cool place with nice tech and I feel like its a nice opportunity to grab, but I feel like I need the rest too.

And I have to decide tomorrow. I guess I'm terrible at decision-making sometimes Ffs..

Currently we have to make a new REST API at work. I want to have a clear and functional API (with HAL JSON, that is given). But my colleagues don’t like this, because they don’t like the design (the look and feel) of the HAL JSON responses. They just want an easy API with a nice design, so they want to ignore half of the HAL JSON specification. But a REST API don’t has to be easy and don’t need a fancy design, REST APIs are not for humans but for computers! How can I explain this to them?

"The API will be ready soon", but it comes in late and nothing like the agreed upon spec.