I know I am that kind of user 😂

Postman anyone? It's the shit.

The best APIs are the ones which aren't versioned and completely change key features overnight.

Woke up this morning to three broken client apps. Yay.

GitHub: a marketplace for publicly available API keys

You know what's funny?

Being called Jason.

Developers when talking about APIs and similar stuff: "So if you connect to our API you can get XML or JSON-" <pause>
<looks at me with a smirk like "haha! JSON/JASON LOL!">
<I gently smile like saying "yes. yes. I know. Thank you">

Sigh

Fuck it I’m posting it again because I got got by this…Again.

If this is how you write your APIs, take a number, get in line. I got some slapping to get out of my system.

1) get an idea for a cool app
2) evaluate feasibility and execution
3) ensure accessible data streams and APIs
4) get excited and realize the idea is doable
5) see someone has done that exact thing and it's already published on the Appstore :/

First rant here. Long, but please bear with me:

So after slogging my ass off in various early stage startups for over 4 years and keeping up with the almost non-existent development process, I joined an organisation which has some of the brightest and smartest minds I have had the pleasure to work with.

Mind you, this company is the market leader in it's field and has a 50+ people in it's tech team and the quality of work is pretty impressive.

Now for this week's sprint, I was asked to develop a feature which already exists on the Android app and they want to introduce in the iOS app too. The backend APIs are all in place and all I need to do is build it with virtually no dependency. My PM asks me to start with the UI and ask the backend dev for the API list whenever I need them.This is where the story turns.

For my first API, I go to the backend dev and ask him to share the API documentation and he looks at me as if I have asked him to dance the fucking cha cha. With a straight face he tells me that, 'The organisation doesn't maintain any kind of documentation for it's APIs.' Now this really shocks me. Even in a 5 men tech teams I have worked on, we have always maintained a spec doc for the APIs and this is a company which is known for it's tech practices.

Being the new guy I compose myself and ask if they have anything for me here: Postman collection, a workflowy doc, a goddamn txt file; anything which might help me, and he laughs at my dilusion and says no.

Dejected, I ask for a way to get the APIs and I am told that there are only two ways: either I keep bothering the Android dev for the APIs(No, I don't have the access to the android repo and nor am I gonna get it) which he had worked on 4 months back or I install the prod app on my phone, and use Charles to get every fucking API which is really, really annoying.

I thought writing out this rant would make me feel better, turns out it just made me angrier. Why the fuck can't they document such an important thing!?

I currently have the best problem ever:

Our client applications and APIs are so fast, users are complaining they don't notice that the UI changed in between the time they clicked a button and their eye drifts to the adjacent component. So now we're having to build visual cues to account for that.

#KillingIt

My first markerless ar in development!
Built from scratch, with unity webcam apis!

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 programmer once explained Nietzsche like this:
A long time ago, god created the world, but forgot to leave a developer documentation, thus the whole world was like legacy code...
And humans are like the end user of this world, and some among them spent time studying it, using the Moral API, hoping to get a result of "http 200 ok" from our world for the peace of mind. But the true operation of this world is still yet unknown...
As time passes, humans begin to find that in Moral API, good and evil are two base classes, and all the other moral properties (like ethic, justice and stuff) are just other classes based on those two classes through multiple inheritance.
One day, when programmer Nietzsche was observing the world's runtime behavior, he came up with a question:
"Did god really use good and evil as base classes? Could it be that they are actually derived classes?"
Most of the world is currently in the favor of mankind, and god must've wrote individual user cases for it's end users, he thought.
This made Nietzsche thinking: if end users are considered into two cases: the strong and the weak, how would the world be designed base on its user story?
Let's think about the strong, they can bully the weak as they please, and there's nothing the weak can do to stop them. In this case whether the Moral API exists or not doesn't fulfill the need of the strong.
But when it comes to the weak, Nietzsche thinks that because the weak cannot fight the strong, they need to belittle bullying and praise the strong for being nice. When the weak does this, it covers their powerless state to some extent, making them look somehow equal to the strong by being capable of commenting.
God might have coded the Moral API to fit the weak's requirement, also adding some public methods for the weak to comment on the strong. If the strong takes care of the weak, they call him nice and good, if the strong bullies people, they call him bad and evil.
That's when Nietzsche realized, that good and evil are both derived classes from the weak, and the base class should be the strong and the weak.
Then he started a series of studies about the Moral API, and got some thesis that persuaded lots of other end users...

Tip: Don't reinvent the wheel.

Use APIs

Susan, where are the fucking API docs?
Harold?
Jimmy?
There ar no FUCKING documentations for all our APIs????

Long story short, I'm unofficially the hacker at our office... Story time!

So I was hired three months ago to work for my current company, and after the three weeks of training I got assigned a project with an architect (who only works on the project very occasionally). I was tasked with revamping and implementing new features for an existing API, some of the code dated back to 2013. (important, keep this in mind)

So at one point I was testing the existing endpoints, because part of the project was automating tests using postman, and I saw something sketchy. So very sketchy. The method I was looking at took a POJO as an argument, extracted the ID of the user from it, looked the user up, and then updated the info of the looked up user with the POJO. So I tried sending a JSON with the info of my user, but the ID of another user. And voila, I overwrote his data.

Once I reported this (which took a while to be taken seriously because I was so new) I found out that this might be useful for sysadmins to have, so it wasn't completely horrible. However, the endpoint required no Auth to use. An anonymous curl request could overwrite any users data.

As this mess unfolded and we notified the higher ups, another architect jumped in to fix the mess and we found that you could also fetch the data of any user by knowing his ID, and overwrite his credit/debit cards. And well, the ID of the users were alphanumerical strings, which I thought would make it harder to abuse, but then realized all the IDs were sequentially generated... Again, these endpoints required no authentication.

So anyways. Panic ensued, systems people at HQ had to work that weekend, two hot fixes had to be delivered, and now they think I'm a hacker... I did go on to discover some other vulnerabilities, but nothing major.

It still amsues me they think I'm a hacker 😂😂 when I know about as much about hacking as the next guy at the office, but anyways, makes for a good story and I laugh every time I hear them call me a hacker. The whole thing was pretty amusing, they supposedly have security audits and QA, but for five years, these massive security holes went undetected... And our client is a massive company in my country... So, let's hope no one found it before I did.

On the job 😊. Told them I could code in the interview... and they believed me.

Now I'm our Director of Technology, and spend at least 8 hours a day building everything from GraphQL APIs to Electron apps. It's been an awesome journey!

There is this service that I want to use (wont name it for privacy/legal reasons) and I have created a trial account which gives me a limited access to their apis. However the usage is where things are interesting.
The api access is restricted to some 1000 calls per trial account. But also they have a explorer option which lets to have the functionality as a web app like a dashboard and the explorer usage has unlimited access.

Now since I didnt want to exhaust my api limit, I let my service call the explorer apis instead. Is this ethically wrong or it is the fault of the service providers that they have such a big gaping hole in their licensing?

I'm the only programmer in the company. Sometimes it's exhausting doing everything. I'm currently working on 3 iOS apps, a web app, building out the APIs and managing the databases at the same time.

Full fucking stack. Every day.

FUCKING TELEGRAM FUCK YOU STAY IN YOUR FUCKING API DOCUMENTATION AND STOP FUCKING TESTING YOUR SHIT ON A PRODUCTION SYSTEM WHY WOULD YOU DO THAT FUCK OFF WHY AM I EVEN DEVELOPING SHIT FOR YOUR PLATFORM ANYMORE WHEN FOLLOWING YOUR DOCUMENTATION LEADS TO FUCKING ERRORS AND WE HAVE TO DECOMPILE AND REVERSE ENGINEER YOUR FUCKING "OPEN SOURCE" APPS BECAUSE YOU DONT EVEN BOTHER TO FUCKING UPDATE THE SOURCE CODE ONCE A YEAR WHAT THE FUCK

Thank you for your attention

Trash, trash, trash.
Who the fuck writes this shit?

Who the fuck lets these trash should-be-junior devs roll their own crypto? and then approves it?

The garbage heap of a feature (signing for all apis) doesn't follow Ruby standards, doesn't follow codebase conventions, has `// this is bridge` style comments (and no documentation), and it requires consumer devs to do unnecessary work to integrate it, and on top of all this: it leaks end-user data. on all apis. in plaintext.

Fucking hell.

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

I recently interviewed for a job at company where I had 20 minutes to code a solution in python (whose standard library I know nothing about) to a question, which also included googling certain finance-related APIs, with not one but two technical interviewers looking over my shoulder THE ENTIRE TIME.

Best: My first app for Windows 10, "devRant unofficial".

Worst: A website for a client using Facebook APIs which don't want to work properly.

Just when i thought i had met my fair share of stupid apis I find this.

Worst of 2020?

Well, I've learnt never to do free / voluntary work.

Been spending many weekends helping out a former friend, mostlyby creating APIs, sites, managing servers & scripting.

Now that I have a girlfriend, my weekends are spent mostly with her.

He got really mad, said he doesn't want to waste time.

Then went to *pay* someone else to continue what I've been doing...

Just a Developer thing!. You can apply for jobs through APIs.

Just saw an advert with the tag line similar to "An API built by developers, for developers"
Which makes me wonder. Do non-devs build APIs? How does that work?
The same to using APIs. Surely some dev knowledge/experience is required?

I find the way to communicate with APIs very inteRESTing.

Friend: Hey, so what do you do?

Me: I build backend systems and apis. I work with java/mongodb. I dable into some elixir and kotlin on my free time.

Friend: Cool, can you build me an Android app?

Creating RESTful APIs with dotnet core on Linux, without any pressure from PMs.

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

1. Pre-sales to Client: We can develop 200 APIs with 10 developers in 9 months.

2. Client: Ok! Cool, its a deal.

-- Sprint starts --
3. Actual: We are 6 developers, commited (or sold out) to make 200 APIs in 9 months.

Fucking pre-sales.

"You've been working on this for 6 weeks, and I don't see any changes. What have you done?"
"I completely overhauled the backend, now everything makes more sense and we're using more modern APIs"
"But nothing's changed at all! The front-end looks exactly the same!!"
"*sigh* The new backend is also more secure.. "
"Oh, so it's a security upgrade, that's good, but why did it take six weeks?"
-_-

TPM decide to upgrade all our servers at once Friday night and didn’t bother with any smoke checks. This is what our APIs looked like Monday morning.

"It is risky to release an app that depends on APIs that you don't control."

Yeah, dude, we also live in the real world.

Better to say: "Your app should handle cases where the third party API is partially or even totally down."

God, some people, they build a wall of rules around themselves and wonder why their skills don't improve.

Css was developed by monkeys. I fucking hate how there is no organisation, laying out stuff requires too much work, there are billions of ways to do something. Aligning things in css actually has a web page dedicated to that, seriously, what the fuck????? I love doing backend and creating rest apis but for the love of god i cant stand css and front end in general🤦🤦🤦

Dear Google, please notify devs before you overhaul apis in Android, I hate updating my api level and then my code won't build, this ia extremely shitty, where I have to now update random Android code because of deprecated apis, Shit Google.

So my CTO comes to me and asks me to checkout the APIs provided by a particular service and see if we can use them.

After two days of research I go to him and tell him that it cannot be done and it doesn’t fit our use case. He tells me research more although I have researched everything required.

So I take two days doing absolutely nothing, send a mail to the developer of the apis and they tell me that it can’t be done.

Now imagine this kind of scenario occurring every three months. RESEARCH MORE.

Why do super senior members of our company don’t trust me. It’s just so random and anger evoking

We're digital plumbers.

90% of this job is figuring out what thing to connect to what thing and then figuring out how to connect them.

Writing the code that goes in-between both ends of the pipe is easy if not trivial 90% of the time.

Meaningful change in this industry is centered around endpoints: contracts, deployments, etc. Nobody needs yet another way to organize and import their leftpad().

Bless the service APIs that don't charge you for failed requests, that fucking on-site team almost cost my client 7k$, just because of a typo and an endless loop, that they pushed to production, while bypassing the rate and resource limit I set in place, because it "wasn't working" - it was working, you fucking cunts, it was preventing your system running wild for a reason.

Client: "Let's code a prototype to show our intents to the customer. We have 96 screens to implement as a native app in 6 weeks"
~Prototype delivered in 6 weeks, despite some changes in the design on-the-go. Few months later~
Client: "The customer likes the prototype a lot. They would like to see some changes (another set of > 40 screens). It's still a prototype and the changes should be implemented in a month, but this time it has to use real data from external apis. We don't know which APIs yet, but it should also go live on the app store"

Like, seriously?

Android docs suck so hard 😇

Google sucks so hard at making APIs 😄

Wraps everything in libraries, whose only purpose is to hide their incompetence 😛

A free, open source, modular (plugin based) home automation control center.
Ultimate goal is to support the core / apis and other devs code the drivers for the 'IoT' devices.
Also integratable with all the speech assistants like Amazon Echo, Google Assistant, Cortana etc.
Not that money dependent but very time consuming project.

Im starting in a week tho!

I think I'm not as socially awkward as I once believed. I realize I just have nothing in common with the majority of people.

I don't watch sports, I don't care about cars, or fantasy football, or have any hobbies non-developers would find interesting.

If you want to talk about software patterns, finite automaton, Lua/C APIs, etc, then fuck yeah I'll talk to you all day long.

I wrote my app so nicely, I just finished adding a 2 new features without any major rewriting... even after not touching it for many months...

when in doubt,
write everything manually,
because even if a package exists,
it's so old and outdated,
it's not even worth fixing all the errors,
so you may as well,
grow your own APIs

it'll be faster!

I don't know why, but each time I have the chance to create a caching system with redis to e.g. cache requests to APIs I get all excited about it.

1. Understand APIs without reading documentation.

2. Write correct code from first try.

3. Know to program in every language.

4. Create the perfect fully functional AI system.

5. Center objects vertically with one line CSS at target object.

When the 3rd party library you're using is raising compile time warnings about using APIs that have been deprecated since iOS 6.

It was last updated in Sept 2015. President says they're working on iOS 10 compatibility.

If it still has that warning next release...

While working on generic enterprise code: querying databases, calling third-party APIs and just passing data around, I'm thinking: "PLEASE LET ME DO SOME THINKING, LET ME WORK ON SOME HARD ALGORITHM OR SOMETHING!"

When finally working on 'some hard algorithm or something', I'm thinking: "ARGH! MY HEAD ACHES! GIVE ME RELEASE! LET ME WORK ON SOME MINDLESS ENTERPRISE CODE!"

I only have least favorite APIs

Coding is like cooking.

But only if
the heat source is lava. //Language
And the pot is lava. //IDE
And the food is lava. //Program
And the dishes are lava. //Classes
And the floor is lava. //APIs
And the tools are lava. //Compilers

People are so obsessed with apis nowadays that I was thinking about writing a rest api to get the amount of fucks that i want to give to the client whenever they ask for some change requests or improvements..

Unintuitive APIs, with poor documentation and terrible parameter names. It's like they don't want me to use it

And today in Laravel-land, how to take fluent APIs to the utmost consequences.

Better...? Seriously? All your lines got longer and you know have closures to run.

I like obj c more than I like Swift. I don't know why and even tho it is the same API I find obj c more intuitive and useful since it is a strict superset of C and C is very useful.

Not to say I don't like Swift. I like it. I just have something against mobile OS APIs really

Favourite API.
That's a hard one.
I guess it's a toss up between Salesforce APis and Cloudflare.

Both are straight forward and work within minutes of getting started, and both are well documented to the point, you only need a basic understanding of what you are doing or trying to manipulate to get it up and running.

If only AWS could do the same 😅

TL:DR
Why do so shitty "API"s exist that are even harder to write than proper ones? D:

Trying to hack my venilation at home.
This API is so horrible D:
The API is only based on POST requests no matter if you want to write values or get values and the response only contains XML with cryptic values like:

<?xml version="1.0" encoding="UTF-8"?>
<PARAMETER>
<LANG>de</LANG>
<ID>v01306</ID>
<VA>00011100000000000000000010000001</VA>
<ID>v00024</ID>
<VA>0</VA>
<ID>v00033</ID>
<VA>2</VA>
<ID>v00037</ID>
<VA>0</VA>

Also there are multiple API routes like
POST /data/werte1.xml
POST /data/werte2.xml
POST /data/werte3.xml
POST /data/werte4.xml
And actually the real API route is only given in the request body and not in the path.

Why is this so shitty? D:<

Btw in terms of security this is also top notch. It just globally saves if one computer sends the login password.
I mean why even ask for a password then? D:
That made me end up with a cronjob to send a login request so I don't have to login on any device.

PS:
You see, great piece of German engineering.

Last year I changed jobs from a large multi-national to a small local agency (which happens to be run by friends of mine).

One of the reasons for doing this was that my work involved more office politics than *actual* software development, and had just plain stopped being fun.

Now, I am having fun again! An example?

For one of our clients we have to connect to (a lot) of third-party APIs. Often even SOAP APIs!

Now I hear you protest "But that is no fun at all! SOAP APIS SUCK!" Which is true, more often than not. 😔

BUT! My friend started an internal API-SNAFU Trello board. Every time you get bitten in the ass by some ill conceived fuck-up of an API, you get to add your complaint to the board.

Beside giving as something to reciprocally rant about, the board also serves a serious function: depending on the amount of fuck-ups an API has been known to make, the price for working with that API will go up.

Who said it doesn't pay to complain? 😀

The whole office thinks I'm working on a serious dev. I'm just running dev rant APIs on cmd and scroling.Happy Friday!

Fuck you Twitter for making your widgets createTweet-method only work with the tweet-id as string. Fuck you especially for don't returning nor throwing any error for giving an integer value to it.

This took some time...

Started a new gig doing APIs and deployment pipelines. After a few weeks a new boss came on the scene and decided I'm now a web dev, and the API and pipelines are going to be scrapped, and replaced by something with less availability and scalability.

Anyone looking for a good back-end dev?

😵‍💫

One of our internal apis returns an array in which the first element is metadata about the request.

Why would anyone want to punish their users like that

From today on I'll have two roommates. Two girls, who always listen. And the best part, if I don't like their response I'll just use their APIs to make them say what I want. Too bad both of them are unemotional boxes.

So google maps APIs will now basically be a pay to play, like many other services of google, is there any actually good alternative for getting long+lat and distance matrix for free?

You know it is gonna be "fun" integrating client APIs, when all of them respond with
"Thanks for submitting the request"
And no error or status code whatsoever, no matter what you send.

Also, the client likes to test/call this API in Internet explorer address bar, and doesn't trust Postman. Amazing shit dude.

The worst thing I have seen a dev do?

- Have all the APIs work without an access token for our main product which handles ~10k requests a day.
- Calling our architecture secure in the crucial investor meeting and being 'confident' that our database can not be compromised. No wonder we did not get funded.

Yup, sure our team of three devs will build you a fully functioning e-commerce site from scratch that grabs data from several APIs and uploads it to several more.

You need it in two weeks? No problem.

Me: Wait...what the...?!

One week in and I only have access to test one of the four necessary APIs as the client hasn't signed the necessary paperwork with other providers.

If we had a devRant vote on the most annoying word of 2018, I'd vote for "token".
Token here, token there, token yourself in the rear!

Some project I'm currently working on has to fetch 4 different tokens for these syphillis-ridden external CUNTful APIs.
Your mother inhales dicks at the trainstation toilet for one token!

Companies that create APIs and then update them but fail to update the documentation, to a point where the syntax doesn't even remotely resemble how it originally was, or even give the location of where the new endpoint is.
WHY MUST YOU MAKE MY LIFE HELL

Front-end web development in 2018 is a fucking dumpster fire. 4 month old blog post guides are out of date, hipster toolchain APIs change monthly, npm can't find a module that is literally right there in its entirety in the fucking node_modules directory. JavaScript is love. JavaScript is life.

NASA APIs. I frigging love space

That moment when you browse github repos to contribute but then you realize the APIs are way more advanced than you're coding skills. #fml

Google: we want to crack down on adblockers in Chrome and remove APIs. If we threw out Chrome store extensions that use the old ad blocking APIs, Chromium forks would be hit as well, haha!

Vivaldi: we've integrated DuckDuckGo based ad and tracker blocking right into our Chromium based browser. Also for Android now, haha!

My story with frontend devs who use my APIs.

So.. Someone proposed replacing all huge functions with apis and then using them internally in our own code.
Accessible over http..

We converted all TCP APIs to UDP to ensure there are no handshakes...

Yesterday, when I was discussing my project with my Java professor, he told me to build an online quiz system in which the user can't view anything other than the quiz (to prevent cheating).
I tried telling him it's not easy and it definitely can't be just made into a website.
He told me to make it using APIs.
Now I'm wondering if he even knows that an API is...

Wow, very technical and clear documentation:

"While we do not publish the symbol limits for the streaming API, we do monitor for abuse to make sure people aren’t doing anything egregious. Essentially, ask for what you need. Don’t abuse the APIs and you should be fine."

...and, we all know what 'fine' stands for, right?

🤡

THIS IS HOW TO INSULT A DEVELOPER 👾🤓

Microsoft APIs documentation, best API documentation ever!

I never knew APIs could be this awesome!

Clients assume that because they can't see it, means no real work was done. Or even worse, you show them code that was written for the server, even demo the apis but without a pretty front-end it's pretty much meaningless. Even if ITS NOT YOUR JOB TO DO THE FRONT-END!!!

!rant
Postman - app for developing and testing APIs, it is so damn gooood!!!

I am genuinely curious, to those still building SOAP based APIs in 2022, why??

Need to have APIs ready, worked weekends of my own time still not done, why won't my boss get bums on seats to help -.-

I often have ideas, and can (and have) the APIs for my ideas often built in one single evening - but - i absolutely hate building the frontend of sites and apps.

Where do you look for people on the opposite side of the coin?

Company A: Oh yes we work with this huge tech company all the time and our APIs are just amazingly well made! DONT WORRY!

Company B: Yeah we've worked together once or twice and nothing seemed to go wrong the last time. DONT WORRY!

Reality: 11 API warnings, no data transfer and a SQL error meaning nothing I've been working on actually worked. #Rantover

ideal sprint fallacy.
total days 10 , total hours(excluding breaks ) 8 hrs per day= 80 hrs per dev

code freeze day = day 8, testing+ fixing days : 8,9,10. release day : day 10
so ideal dev time = 7days/56 hr
meetings= - 1hr per day => 49 hrs per dev

- 1 day for planning i.e d1 . so dev time left . 6 days 42 hrs.
-----------
all good planning. now here comes the messups

1. last release took some time. so planning could not happen on d1. all devs are waiting. . devtime = 5 days 35 hrs.

2. during planning:
mgr: hey devx what's the status on task 1?
d: i integrated mock apis. if server has made the apis, i will test them .
mgr : server says the apis are done. whats your guestimate for the task completion?
d : max 1-2 hrs?
m : cool. i assign you 4 hrs for this. now what about task 2?
d : task told to me is done and working . however sub mgr mentioned that a new screen will be added. so that will take time
m : no we probably won't be taking the screen. what's your giestimate?
d : a few more testing on existing features. maybe 1-2 hrs ?
m: cool
another 4 hrs for u. what about task 3?
d : <same story>
m : cool. another 4 hrs for u. so a total of 12 hrs out of 35 hrs? you must be relaxed this sprint.
d : yeah i guess.
m cool.
-------
timelines.
d1: wasted i previous sprint
d2 : sprint planning
d3 : 3+ hrs of meetings, apis for task 1 weren't available sub manager randomly decided that yes we can add another screen but didn't discussed. updates on all 3 tasks : no change in status
d4 : same story. dev apis starts failing so testing comes to halt.
d5 : apis for task1 available . task 3 got additional improvement points from mgr out of random. some prod issue happens which takes 4+ hrs. update on tasks : some more work done on task 3, task 1 and 2 remains same.
d6 : task1 apis are different from mocks. additionally 2 apis start breaking and its come to know thatgrs did not explain the task properly. finally after another 3+ hrs of discussion , we come to some conclusions and resolutions
d7 : prod issue again comes. 4+ hrs goes into it . task 2 and 3 are discussed for new screen additiona that can easily take 2+ days to be created . we agree tot ake 1 and drop 2nd task's changes i finish task 2 new screens in 6 hrs , hoping that finally everything will be fine.

d8 : prod issue again comes, and changes are requested in task 2 and 3

day 9 build finally goes to tester
day 10 first few bugs come with approval for some tasks
day 11(day 1 of new sprint) final build with fixes is shared. new bugs (unrelated to tasks. basically new features disguised as bugs) are raised . we reject and release the build.

day 2 sprint planning
mgr : hey dev x, u had only 12 hrs of work in your plate. why did the build got delayed?

🥲🫡

After over two days of debugging, lesson learnt don't assume your table's prefix nor depend on other APIs for SQL injections

There's this Senior Developer here at the company I work for, and every single project he works on (usually APIs), the return status codes are always 400 when there is an error.
How do I tell him there are over 60 status codes?

Worst thing I’ve seen other Dev do?

Asking someone else to do the documentation for APIs he/she wrote...

Gotta love it when everything works flawlessly with the test API endpoint and credentials, but when I try to go live, there's suddenly a ton of additional configuration to get the third-party APIs working.

Why the fuck do you even provide a testing environment, if it's completely different from the live one?

Feature to spam people everywhere. A frigging set of apis where you can spam sms to people based on their habits. I am sorry for this shit. Even I'm not safe from this.

Today it is the day of:

"Ok just a few more changes and this thing is good to go. Let me just look at this for a bit to make sure the changes work and...."

And now I'm looking at some APIs spitting out garbage and somehow everything is working and I'm questioning if I know anything at all now :O

Seeing the phrases and language and different APIs and platforms and various versions of everything everybody talks about makes me feel even less prepared to enter the industry properly when I leave University.

I'm going being a WordPress specialist.

My current project: PHP microframework that makes building REST API kinda 'easy'

But I've read some articles online that building APIs using PHP is a really bad idea. I guess I just wasted my time. Lol. I hate myself.

Why do people design web apis where the way you submit your authorization is via a custom header?

Especially when the authorization is literally a token?

Am I ingesting something special?

Can we all start using error codes for apis? I'm so sick of doing a reg exp check to see if the word "failed" is in your return message and having to change it every time you feel like updating the language.

On the one hand I really wish there was a good open-source self-hosted file sharing and collaboration service which made use of modern web technologies to provide most of its features inline as well and not just through APIs consumed by client applications.

On the other hand, I tried writing a WebDAV server once, and I fully empathize with the people who have to deal with this madness.

Remember, the more "cutting edge" and "thousands of clients" a company has is inversely related to the quality of documentation they have on their APIs and software solutions.

I don't give a fuck about your pretty examples, show me which FIELDS can take which VALUES. It's that simple. Instead, I'm wasting your company's and my own time by spamming support for what should be basic questions clearly outlined in the documentation.

The way I feel when working with Google APIs:

Personal mini-project from a million years ago which I practically don't maintain anymore, broke. External APIs are being bitches.
Made a fix, but I'm too lazy to push. (I don't think anyone else is using it tbh)
Huehuehue.

Reading about micro services and they sort of sound like mini APIs wrapped by individual HTTP servers.

But if all the APIs need to send requests to each other wouldn't the overhead from just making the connections for each request add up and be huge?

REST apis. More than you think it is.

Just because you can access a resource by a uri, doesn't mean you have a good api.

Hypermedia that shit and let websites reuse your links from api responses, then we are getting somewhere.

Also, Fucking api versioning.. Learned the hard way that /v1/ doesn't mean Shit in most cases

To me, writing authorization code for securing APIs is like having to fold an enormous pile of laundry and actually putting it all away afterward. It needs to be done but I'm not going to enjoy it.

I totaly hate SOAP APIs!
Pls stop using SOAP.

Part of my job requires me to use SQL in SQL Server and databases and Python and utilising Javascript APIs - so I was thrown in at the deep end. But my fiancé is also an amazing help as a software engineer he helps to spot my errors and encourages me to take on new challenges.

Puts three months of work into this project; cronjob to ping 3 APIs at regular intervals, cleans, massive features extraction, dumps into PostgreSQL db. Got Django on top of that with a small neural net and interesting viz - absolutely gorgeous!

Can’t fuckin wait to showcase that.

Feedback: “is that the right blue? I think you have the old company logo! etc”

Mah.LahF

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.

Hi all! I am an iOS developer and I've been using Firebase as my 'online storage'. I want to be a more full stack dev and creating my own APIs. I want to start to learn Java or .NET APIs (uuh an iOS dev speaking about .NET :P). Anyone that can recommend good courses or tutorials and best practices? I have been learning Java and .NET in college, but that is about 4 years sgo.. Thanks in advance!

The project is about keeping track of APIs of libraries, frameworks, language, and notify subscriber when some API is changed, added or deprecated

The principal developer who wrote one of our APIs is on annual leave, there's no documentation.

It's in another language.

Add some points into scrumwise for 'Deciphering hieroglyphics'!

Why would anyone ever choose Oracle proprietary APIs for building web applications? I'm pulling my hair out trying to fix, yet, another Oracle ADF project... Why? Why?

Apiology: the study of APIs and how they work

APIs, APIs, APIs... I feel like building an API for everything which goes over the wire is a must-have today! Yes it makes sense for decoupling purpose, access control etc (all the things we learned from OOP design principle books when we were in school) but come on, REST API for internal database access when there is something like SQL over JDBC/ODBC/WhateverBC ?? So I have to study the REST API documentation for applying simple where-statements but in API manner...

That moment you underestimated a local company site from using APIs. So you manually collect the data by scraping the HTML. But months later learn that they DO in fact use APIs.

🙃

A hackathon sponsored by two brands, the topic was to create smth cool with their APIs (either of them, they were to pick a winner each). We got a little too ambitious and tried to use both, ended up messing everything up and nothing to show. They loved our idea though :|

PS: Somehow the winner was a crappy flappy bird clone ¯\_(ツ)_/¯

Mixing PHP and HTML code with a bunch of if-elses, creating a docker-compose script thats uses the remote database password (and its committed) and set API calls to IP fucking addresses with no explanation. Just make POST requests to undocumented APIs.

How the fuck are these people allowed to code?????

Hi friends and others. There is a task I want to automate. I want to convert .docx files to .pdf and then minify those. Are there JavaScript libraries or npm- packages which can do that? Because I would like to use Gulp or Webpack for this task. I would not mind if external APIs are involved, but I would rather not use those if not required.

Pls share your wisdom. Bye.

An hybrid app for Onesignal APIs

Being blamed for and written up by your manager for a late deliverable on a ui component that the same manager failed to provide the APIs for in a timely manor.

I was just getting frustrated how hard it can be to search on google for very specific subjects when it comes to development. So I thought, why hasn't anyone made a search engine just for developers so you don't get any bullshit in between.
I found apis.io but they only have 1076 documented apis in their db... lets collectively make this better!

Boss knows that building a release version of the app we are working on takes like 20 minutes, and they need 3 different apks for separate apis.

customer to boss: so, when will you send the apks?
boss while smiling: yeah, like 10 minutes

So I have been using REST APIs since last 4 years and used this term in lot of technical discussions with backend teams.
Learnt that it's full form is 'REpresentational State Transfer' just a few minutes ago 🙈

when will we have those APIs published, @dfox....
we need them

Working on an app to sync data between our ticketing system and an API a vendor made for us to interact with their ticketing system. I put off working on it for months, mostly because I had mountains of other "urgent" things that jumped in my face, but also because I needed to design the whole thing, and I really have to get into the right frame of mind for that kind of creative organization.

Today I dove into it. I built the JSON to submit, given whatever variables are necessary, and figured out after a while that the smartest way to handle this is not to search for an existing internal ticket, but to have the creation of the internal ticket set a flag for an automated sync process to check when it runs.

It's going to be much easier when I get that built, but now, knowing that, I'm daunted enough that I'm procrastinating. Think of something, chart it out with notes in a text editor, procrastinate.That is probably like 95% of the time I spend in "development."

Dear Python,

Seriously fuck your horrible compression APIs. What if I want to make a normal stream a tarball stream?

- Me

Got all the GET apis in 6:30 pm . Asked me to integrate it within 8:30pm so that they can present the demo at 9. WTF

Service I was needed to integrate to our system had such poor documentation and a separate pricing tier to access their APIs...

... Not having it. Used Guzzle to perform both the authentication and their search page, then made wrote a function to web scrape the result.

Job done. 😎 And yes, I have no shame to say I love PHP.

its hard to keep yourself updated with apis, specially when you are nodejs/javascript developer.

Creating a simple application to keep track of changes in api and inform the subscribers about changes.

Stack - Vue.js (quasar), nodejs, mongoDb

You know what sucks?

APIs with the latest data, but without the latest endpoints.

What the fuck? You did the data, why not the endpoint??

Hey everyone,

When I was in college, I used to wish to do some freelancing work to earn some amount.
But I never did it due to lack of experience and knowledge.

Now, I've been working in a Small IT company for one year and I'm confident enough that I can do it.

I'm interested in making APIs as a freelancer.
I've few doubts here,
Once the API is developed is it a freelancer's job to deploy it in some cloud instance or they just need to share the code?
If the client wants the freelancer to deploy it on their behalf then do the freelancer have to create his account for example in AWS for deployment?

Also, Do freelancers have to set up and maintain all the DB for the APIs?

So Im taking over an project from an colleague. And it involves a lot of things from an external API. I cool with that, I enjoy working with APIs in general.

Let me explain it a bit more. I enjoy consuming APIs with frontend frameworks like reactjs and angularjs.

But my colleague had allready started some with consuming one of the endpoints.

He did it with ajax....for god sake. Are you serious?!?!?!!

Ajax calls??? Why ????

So I pointed out that we could use vuejs, we don't have to compile anything like with react or angular.

Things that we need to do are not that interesting nor big. Mostly getting items and maybe filter these items.

But he insisted on using Ajax because there wasn't that must time to use fancy frontend frameworks.

Feel utterly deflated today. Working with an API that gives no feedback what so ever. Going around in circles and making little progress. What’s worse is we quoted 1 days work.

With all my experience I should be better!

A new development rule I've started to implement:

All backend APIs will be written with the assumption that it's gonna get distributed as an API for 3rd parties to be integrated in their systems - meaning that every API I write will have proper response status codes for appropriate scenarios (like 400, 429, 500 status codes).

No more `res.json({status: false, message: 'message'})` with 200 status code across the board.

Wanted to test out random number generation in different distributions. So did it using HTML/JS using google charts APIs, just to find out after sometime that R does what i did by default..

Reading the docs for salesforce APIs is exhausting from the sheer density of bullshit buzzwords.

Imagine a "development" environment with no vcs, no APIs, no general hierarchy for db admin or software development, no test environment. Well this was my first job.

Quite literally a dumpster fire.

I know I'm not a world class developer but I still think this was beyond unacceptable for a software startup.

When you code sth. From ground up and it works everything without any errors as you wanted, even though you’re using 2 APIs in about 20 lines. This feels so good :)

To all developers working on publicly visible APIs or writing public documentation.
DON’T BE A DICK !
Do not just put a screen capture of your curl request which takes 10 minutes to write by hand.
Do not show me list of arguments as an image.
Have AT LEAST one executable demo project (Any language)
And, it’s 2020, add a fucking proxy generator.
How hard can it be?

Good friend, Jay. Helped level up my understanding over the years, JS patterns, using APIs, best practices, etc.

Also helped kill off anxiety about the community by proving we work together and share knowledge.

Many thanks and I hope everyone has a Jay in their life.

What tools/pluggins do you recommend for:

VSCode
Data management.
Test code
Organization and collaboration
APIs
Debugging

And other tools you like to use the most? ✌🏻☺️

Was going to work on learning more about creating APIs in ASP. Net core today. Instead playing video games with my son. Much more fun!

I am currently playing around with hosting an API on Heruko but I also hear a lot of buzz around serverless APIs...
What do you guys recommend? Or do you recommend another host for playing around and maybe getting more serious in the future?

ah, APIs... writing APIs is fine, even typing an API can be great! 😃👍🏻

that's it

---

No, actually, all of the above is invalid if you've gotta do it in typescript

Getting pretty sick of closed APIs that cost more money than I would make using them for an app.

Anyone using Huawei Cloud? How good is it? Does it have APIs to automate the infra creation and all?

The Amazon MWS API is so utterly shite! Offers error messages sometimes then others tells you to upload your file to their file checker. Their file checker doesn’t accept XML so why say that?

Who on earth develops and documents their shit APIs?

Fuck you Amazon

You know you've dealt with enough APIs when you search for Json Mraz and Google say it's Jason!

APIs this have unnecessary global state (static config properties) as if you're writing a monolithic single threaded app.

Keep your APIs clean. Forget the Rest, stay on the SOAP!

Yo, i have a course where i have to build an android app, and we can make what the fuckever we want. Can you give me some interesting APIs, that are publicly available? It doesnt have to make sense, everything is better than using the anidb api, and thats the only thing that comes to mind.

Learning how to use AWS api getway to secure APIs. I'm enjoying it

The world must truly hate me.

I refactored my code a lot in order to easily integrate different APIs endpoints but then I can't use the one I specifically did this for, because of TLS errors.
My browsers all agree that it's fine, but curl and the 2 http libraries I tested can't fetxh any data.

END ME!

How much of ur job is spent actually innovating and designing new architecture and how much of it is just copy pasting libraries and preexisting APIs?

I have a disagreement with my product owner (PO). Our team develops APIs in Mulesoft. We've got a release coming up and PO wants to release one of the APIs that has *some* working endpoints, but other endpoints in that same API have some open bugs.

Given that it's *unlikely* that those broken endpoints will be used, does it seem like good practice to release the API with known bugs in it to hit the deadline?

Understand that we're not just releasing the working endpoints. We're releasing all of it, bugs and all. PO's logic is that those broken endpoints won't be used therefore it's fine to send known bugs into production.

I just need some advice in dealing with this

Which PHP framework is best for REST APIs and Why ?

Missing data in 3rd party APIs is the reason why we can't have pretty NULL constraints

There are few things I hate more in software development than writing mappings from shitty SOAP apis to JSON.

I recently came to the realization that my knowledge of APIs is very basic. The idea I have right now is based on the "waiter" analogy. I want to dive deeper into the topic. Does anyone know any sites with decent information on them, other than Wikipedia?

Coming from NodeJS, writing APIs with Express, I now do my first steps writing APIs in golang with gin.

Now I know, Express is not the fastest solution out there, but I mean - a good 30ms is alright for non-high-performance backends. And I always thought that's on the faster end of HTTP handling..

..but then I used gin. A GET request doing a MongoDB-write and returning some json. 3ms response time. THREE MILISECONDS. holy fuck. By it's debug logs the actual handling took 540 MICROSECONDS. holy fuck I'm in love.

Complaints about how FE rendering is so slow when BE apis take forever to return. Working on performance projects and feel like you've done nothing at all at the end of each day.

I really dislike conflicting support. Tell me what I need to do to fix your service, don't offer maybes...

When your team can't change from the oracle database because the dba team will be out jobs and database links will be lost (people havent heard of apis)... :feelsoracleman:

Got a few
Crystal reports - words cannot describe how much I loathe this

Sybase ASE or IQ - both are just a hot mess to setup properly

Not a service now fan either

Esri map processing - basically entirely undocumented, slow, old fucking hate it

Arc GIS online - ridiculous licensing issues, undocumented APIs are given as official answers from the dev team, massive pain in the arse

Just wondering, so many people are building extensions for devRant but I didn't find any APIs anywhere. Can someone help me with a link where I can find these? Thanks :)

When recruiters put json and rest APIs on higher priority than frameworks and stacks.
Do they even know how simple are those APIs comparing to frameworks!?

You've developed APIs. And they're working locally.
What's the issue in giving that to the front-end team to consume them ?? ( Said in angry raised pitch )

Somebody please let that dumbfu manager know that the codebase needs to be DEPLOYED on a server somewhere. Without that, you just can't magically build code from codebase and give it to people like code fairy !

Project/Middleware/APIs website about section- Writes a lot of things which is hard to get for many, than explaining exactly what it does

token auth woes

I am fed up of doing shitty token authentications that don't refresh and are database dependent. what's the good way to do token auth for rest APIs? json-web-token?

How do you manage switching between different languages and the tools and frameworks that are used for each?

Or frontend server and APIs are in JS and use mocha for testing.

But backend is in Java which uses Mockito.

Every time I need writes tests and well anything that is language specifics, I basically have to relearn rather than just getting it done.

I am currently lost in translation.
Damn, standardization are important.

I am working on integration of biggest payment company in Japan. Their technical guys doesnt know much Emglish.
Their documention of APIs were literally translated into english without any standardization by their dev guys.

And now I am trying to map what they mean in standard terms.

Psst I no english speaker.

I just wanted to read news

Currently working on a API project. First time dealing with this kind of projects. Any good recomendations on migration frameworks for .NET APIs?

so i need a utility written in C because MS-DOS but i can't figure out how MS-DOS APIs work and there's no docs available so if anyone has used Borland C i'd be grateful if you could help me out on how the hell anything works

Me: “I think I’ll check linkedin today”

Clicks on video: “... good perspective on growth and blockchain micro service apis that leverage ML models for understanding interfaces that welcome scalability within a agile environment...”

Me: *jumps out window*

I got tired of the tedium of navigating dropdowns and required fields to open and close user stories, so I wrote a script with the following syntax:

./ticket open TICKET TITLE GOES HERE
./ticket close <TICKET #>

Any Kotlin fans out here? What's your favourite feature?

To me: coroutines and the flow API. I can't wait for the state flow and shared flow APIs to be released. Goodbye Rx! It'll come probably in the next release, which might come in a week already, because then JetBrains (Kotlin developer) hosts their online alternative to KotlinConf.

Funny ... When they add a feature for web and expect it to also be in the app with the snap of a finger, and the app uses different apis compared to the web ...

Ah and also translations, the translation fairy will add them overnight I guess...

Good thing weekend just started ... Run you FOOLS!!!

Microsoft azure news and other APIs, horrible but works fine.

We're a grew guys developing an application that requires a server to orchestrate everything. We'd like to make everything within this project open source. Does anyone have any experience with open sourcing server side code which will interface with OAuth APIs and what not? How do you go about managing deploys? I'm mostly concerned with security here.