Api's in the morning, ipa's in the evening.

The last two frontend devs I interviewed.

First:

He had 15 some years of experience, but couldn't answer our most basic of technical questions, we stopped asking after the first couple.

Based on a technical test I got the impression that he couldn't distinguish between backend and frontend.

So, I posed a simple question "Have you interfaced with REST API'S using Javascript before?"

Which lead him to talk about arrays. I shit you not he droned on about arrays for five minutes.

"I have experience using big array, small arrays, breaking big arrays into littler arrays and putting arrays inside other arrays."

Never been in an interview situation where I've had to hold back laughter before. We refer to him as the array expert.

His technical knowledge was lacking, and he was nervous, so he just waffled. I managed to ease his nerves and the interview wasn't terrible after that, but he wasn't what we were looking for.

Second:

This was a phone interview.

It started off OK he was clearly walking somewhere and was half preoccupied. Turns out he was on his way back from the shop after buying rolling papers (we'd heard him in the shop asking for Rizla), and he was preoccupied with rolling a joint.

We started asking some basic technical questions at which point he faked that he'd seen a fight in the street.

We then called him back five minutes later you could hear him smoking "ah, that's better". After that the interview was OK, not what we were looking for, but not bad.

Top tip: If you require a joint to get through a phone interview, roll and smoke it before hand.

I’ve been thinking lately, what is it that devRant devs do?
So after a couple of days of pulling data from devRants API's, filtering through the inconsistent skill set data of about 500 users (seriously guys, the comma is your friend) i’ve found an interesting set of languages being used by everyone.

I've limited this to just languages, as dwelling into frameworks, libraries and everything else just grows exponentially, also ive only included languages with at least 5 users out of the pool.
sorry you brainfuck guys.

Needed to download all my music from Google music, their download manager is crap (on ubuntu)

Decided to use their API, found a gem that works perfectly. Started downloading it.

Told my GF how I wanted to code something cool but gound someone else did, her response:

So why doesn't google make something ?
Me:They did, but it sucks in linux, and they have their API's which work fine.

And how are normal people supposed to make it work then?
Me: well it works, jut have to install this and run the CLI with.... wait.. am I not normal?

I guess we are not normal in the eyes of some people.

My 2 friends and me just started a company!!! I feel so excited, because I'm 17 and get to learn how to start a company, I always had that dream to be part of startup. My position is backend developer and db engineer working in apache and python for API's and MySQL for database. 😁😁😁😁😁

!rant !!joke

What is written on a dead API's gravestone?

REST in peace.

The company I recently started working for are young guys my age, who want me to create awesome stuff, however I feel is best, and they let me think and try stuff, like new cool design ideas and use latest API's to create the most modern site possible. "Whatever you think is the best way to do it"

And I'm paid a decent salary. This is the first job I liked. Ever. I literally wake up early to get going, and work overtime (without them knowing nor paying extra) because I think this project is so amazing and I feel like giving back.. I usually hate PMs, but these guys rock.

So this backend developer boasted.
"All the controls are in my hands.. you frontend developers are just the puppets of our API's".

Next day i did this:

If (email === '****') {
profilePicture = 'dick.jpg';
}

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?

Yes! you made a difference.[image]
P.S.
started working at a startup as an intern(android app developer), Most of my work is like debugging the code, new feature implementations.
And the codebase is full of this kind of shit(even worse) plus literally zero documentation(not even for API's), not even a single line of comment in complete project(40K-50K), not any unit test/ UI test.
The funniest thing is when I ask for documentation he(boss | *) said: I am documentation.

While I fucking hate front end and app development, I also hate that I'm so fucking dependant on them for the development of services and such.

Right now I'm developing a suite of services with a mate and while the backend and security (+linux servers) are something I'm good at, I find it hard sometimes to continue without being able to see my API's in action through apps and good looking interfaces.

My mate is currently handling that part but he has way less time than I do and thus I sometimes have to create interfaces to even just be able to see how my shit would work irl.

I can't fucking stand this and it sometimes entirely drains my motivation but there's also no fucking way in hell that I'll dive into frontend and/or app development.

Fucking hell.

When your API's endpoint's response time is near instant.

Rain monitoring/alert api's/services/websites/apps.

Why the fuck are those fuckers (in my case) nearly always right when I couldn't care less and very fucking wrong when I couldn't care more?

Today, morning before leaving:
Nah mate you're good for the next x minutes (more than enough time for me to bike to the station and get on the train).
Reality: suddenly getting two gallons of water a second on me in the form of rain, arrived completely soaked and headphones broke.

Before biking home from the station;
*its raining hard as hell*
Rain alert/monitoring app/radar thingy: nah mate no worries, no rain last half hour and you're good for another half hour!
Reality: arrived home soaked a-fucking-gain.

So motherfucking annoying and frustrating. And yes, I do have an umbrella and such but I hate carrying that stuff around when 'not needed'.

For several years now, I have been writing programs for myself. I have been publishing the source code for them, but none of them ever got much traction. Then I wrote a program that existing users on social media could just interact with without installation (because even that is too much apparently).

When I wrote the programs for myself with others secondary, I had logic problems to solve and dealt with fucked up API's. Now I still have that problem, but I also have to deal with user retardation. They are not using the program in the way I wrote it to be used, at all. They are not passing arguments where there should be, they are running commands that are still under development and therefore (rightfully IMO) available to only me. I am the one being blamed, why doesn't this thing work?

I'd like to rephrase their question to me. Why are you user not using the goddamn program properly? Why should I need to make half the goddamn code account for users' sheer level of retardation?

Yes, users are retarded. And it's not a battle we can win. Earlier I heard this saying that "every time you make your tools more foolproof, the universe invents a better fool".

Google/Microsoft: We are committed to Linux and the open source community!

Us: Awesome, so can we expect a one drive and google drive client for Linux or at least well documented API's?

Google/Microsoft: *Unveils random arse applications and services without answering our pleas*

Google is by far the worst for this, Chromebooks built on Linux, getting full Linux application support and android that's built on Linux all have Google drive support baked in... Can we just get a single fucking desktop client... Please!

Undocumented API's make me sick and very frustrated at times...

After a decade of working in the web development industry, I have given up all hope, it's the same fucking stupid ideas, the same retarded problems in every damned company . Monkeys discovering and reinventing the same fucking wheel over and over and over again. From a 5 man company to the unicorn scaleup (and everything between) I have had to implement access control systems, and various REST API's following the design made by mongrels who do it the first time . I have become to hate the work I once was so passionate about. Just fuck this shit , if anybody had told me when I was in my early 20's that this is what I end up doing I'd go and learn to be a carpenter instead.

I have to admit, making JSON API's is a great way to learn a language/framework. You have to deal with so many things that challenge your understanding.

when I m pissed off I feel like changing all my api's public methods to private

I love Rest API's that always return 200 and have an "errors" field in the response body that I need to check...

Amazing API's and SEX!

Alright people, now that I've got your attention, I'm getting to the point where I need to plan and roll out a solid API for a project. So after reading a lot of the horror stories written here, What are the finer points of what makes an amazing API experience to use and integrate with over a poor one?
And don't say documentation (If you do explain why) 😁

Facebook API...

Facebooks "graph" or API's in general fucking stink donkey dick.

Their implementation of oAuth is horrible.. 3 different tokens, which can be either short or long lived, for fetching a facebook page feed (the clients own facebook page)
To that you add a clientID and a ClientSecret.

Great... after painstakingly reading confusing documentation and itching your head... You get it to work.

Then they, without notice, makes a breaking change of deprecate an endpoint you were using.. Jesus..

And all the support you can get comes from a "community group" which may or may not reply with a generic link to their documentation...

There are API's right? 😟

I decided to quit my job. I was supposedly hired as an Android developer, but during the past few months I found myself doing everything except Android development: SQL scritps, frontend web development, backend web development, RESTful API's, DBA, release engineering... There's nothig wrong about being versatile, it's actually fun, but I wasn't doing what I really wanted to do and, most importantly, the manager didn't appreciate the fact that I was doing things that I'm not supposed to do, and not only that, I was doing it just as good as some full time web devs who do nothing but web development in the company. I'm pissed off. They probably believe the next Android dev they hire will do all the shit I was doing, accepting the same pay. Fuck them.

Anyone else ever just have those days where you just think of just giving up on programming all together?

I just seem to be having these days every second day or so, I mean I've been programming since I was 11 and I'm just about to turn 21... I've essentially stuck with game development in the same engine in the same language and to this day have nothing to show for the past 10 years other than a million half assed prototypes that seem to just rehash idea's already done by other but a million times better...

Tried learning other languages and none have stuck, I can't grasp C++, don't have a fucking clue how to use Vala and can't even think of anything to make with said languages...

Tried making a pushbullet front end in Vala and can't even learn how to use the fucking API's so once again, that project has been put on the shelf with everything else.

It all just drags me down and makes me think if all the trouble is worth the pain and annoyance.

Maybe I'm feeling sorry for myself (110% chance this is the case) or maybe I'm just not cut out to be a programmer...

TL;DR;

I was asked to give estimation on an app, that:
1. No one has a clue what it does, even though there is v1 on the store with almost 10% of functionality working
2. No one has a clue what should be in the new rewritten version
3. We are already behind schedule and I have no clue why, I've just been told that
4. They need UI flow that shows how the app will work with static data and when API's are ready (because ya know, writing code is easier than creating wireframes and modifying them accordingly) I will then need to link app with API as if it is as simple as drinking a cup of water, especially that: 1. What is water? 2. Do I have a cup or is it given, and 3. Relax bro, drinking water is like eating a burger, piece of cake!

I'm not sure what to do, not enough that it's React Native but also spaghetti requirements that no one was able to answer my simple question: What is the app responsible of?

P.S.: Some say I must rewrite the old app ONLY, no new features, others say: Turn the new web portal into mobile app, I say: WTF is going one?

Facebook is a giant piece of shit. Not only is their platform a massive contributor to mental illness, even their API's are fucking garbage. I'm trying to use their ads API and what it does is it hijacks the entire fucking request so you can't even extract data from the request after calling it. Fuck Facebook and everything they've ever "contributed" to society.

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

Oh I've had loads (and still have) of projects that got me to learn cool stuff! To keep them separate, I'll post some in different rants.

The thing that has helped me most over time (it didn't teach me cool things but it's very useful in general) is that, when api's have rare limits and you need/want to use them more often than is really allowed: you write your own alternatives.

I've especially had this with a geoip api's. Needed one for nearly every project but hit the rate limits with every goddamn service.

Wrote my own in a weekend and no rate limit hitting since then!

A few years ago I would whine, complain and rant about shitty software, which I knew could be so much better than it was. But I didn't yet write software of my own.

Now I complain about shitty libraries, API's and users. Not much has changed really. And every time I write code, I curse myself, and whoever made this trashpile I have to work with. I curse the user to the moon and beyond for using the program wrong. Funny thing is, exactly the thing I was complaining about (input validation, see earlier rant) is also exactly what no more than 5 minutes after release, a user fucked up with. The bot just does not respond at this point. But fuck these braindead retards for users.

In a few years I expect myself to be complaining about shitty compilers and buffer overflows, segmentation violations, bad coding style (don't make your program a fucking colander kthx), and so on.

Next decade I expect myself to be complaining about physics itself, and why the universe is governed by the laws it's governed by. Whoever this God is, he's a fucking retard. Funny thing is, the signs for it are already there. Electron theory! If only those electrons were positrons, then the math would check out properly. Instead of negative electrons traveling from negative to positive, we'd have positive positrons traveling from positive to negative. At least from what I understand so far, this is still a decade away after all.

The point I'm trying to make is that nothing changes, only my understanding of the world around me does, as I tumble further and further down the rabbit hole. Sometimes I wish I had taken the blue pill... Either complain about others' software or perhaps not give a shit at all. Become one of those filthy users I now despise.

The more I write Go the more I get to like the language, but today I felt like I hit a huge wall. I found out that the structure I initially planned for my Discord bot wouldn't work for what I actually wanted to achieve, which made me feel like a completely useless developer. I develop SaaS solutions in the form of REST API's for a living, so making a bot is completely new to me, which is why I probably shouldn't feel so useless. Any advice for getting back on the horse again? I really want to see this hobby project finished. But starting over after almost 20 hours of work feels so demotivating 😕

You wrote a little simple and clean mvc framework to work faster on some new projects. It can "compile" tags as {% var %} or {% array.key %} in the html code with support of {% for arrayOfHash in hash %} foreach construct and nice features, it can call api's callback in a smart way as ghost methods of a class, he can make routes with the route provider. You tested it and made a little example, after you went in the bathroom you read the index code and you started staring at the beauty and elegance of it. You go to bed happy and sleep. The day after you wake up and realize that it's unuseful because there's a lot of mvc framework that surely are better and ready to use, so you lost useful time. Have you ever feel this way? MVC: Me Versus Creativity.

Started new job at startup and finished all the development environment setup started development it was going smooth for one week.all the created API were working fine on the next day morning without any changes API's were giving cors error.asked my senior what must be the problem he said bypass cors and figure out the problem after trying for 1hrs i couldn't figure out what was the problem but API's were back to normal without any changes. then after sometime same day in zoom call i asked what was the problem he said show me the error but I couldn't reproduced the same cors error he then lectured me for 1 hrs and after that he said that learn to solve by your own dont come with silly mistake like this to me.
I don't know what was the problem he even refused me show to what the problem was.

This has been an interesting week! In my first management position, my first person to hire as a senior frontend developer has been approved!

Also made some killer API's this week! Show me the love!

The hunt is on! Heading to two meetups in Sydney next week 😉

TLDR;
How much do you earn for your skill set in your country vs your cost of living?
BONUS;
See how much I & others earn.

Recently I became aware of just how massive the gap in developers earnings are between countries. I'd love to calculate a fixed score for income vs cost of living.

I know this stuff is sensitive to some so if you prefer just post your score (avg income p/m after tax / cost of living).

I'm not shy so I'll go first:

MY RATES
Normal Rate (Long term): $23
Consulting / Short term: $30-$74
Pen Test: $1500 once off.
Pen Test Fixes: consulting rate.
Simple work/websites: min $400+
Family & Friends: Dev friends are usually free (when mutually beneficial). Family and others can fuck off, even if they can pay (I pass their info to dev friends with fair warning).

GENERAL INFO
Experience: 9 years
Country: South Africa
Developer rareness in country: Very Rare (+-90 job openings per job seeker).
Middle class wage in country: $1550 p/m (can afford a new car, decent apartment & some luxuries like beer/eating out).
Employment type: Permanent though I can and do freelance occasionally.
Client Locality: Mostly local.
Developer Type: Web Developer (True web dev - I do anything web related from custom HTTP servers to sockets, services, advanced browser api's, apps & more).

STACKS / SKILLSETS

I'M PROFICIENT IN:
python, JavaScript, ASP classic, bash, php, html, css, sql, msql, elastic search, REST, SOAP, DOM, IIS, apache

I DABBLE WITH:
ASP.net, C++, ruby, GO, nginx, tesseract

MY SPECIALTIES:
application architecture, automation, integrations, db's, real time data, advanced browser apps/extensions (webRTC, canvas etc).

SUMMARY
Avg income p/m after tax: $2250
Cost of living (car+rent+food): $1200
Score: 1.85

*Note: For integrity when calculating my cost of living I excluded debt repayments and only kept my necessities which are transport, food & shelter.

I really hope you guy's post your results, it would be great to get an idea of which is really the worst / best country to be a developer in.

Not really a project as such but started at my apprenticeship 3 months ago only with any real experience with html.

To date I have now worked building API's and web apps and contributing to much larger projects than I'd ever dreamed of before starting where I work.

Spring Frameworks and the projects surrounding it such as Spring Boot, Thymeleaf, and recently lombok. Without these API's and frameworks I wouldn't be using Java half as competently as I am.

Development is moving further and further towards containerization and it's a massive time saver.

¡rant|rant

Nice to do some refactoring of the whole data access layer of our core logistics software, let me tell an story.

The project is around 80k lines of code, with a lot of integrations with an ERP system and an sql database.

The ERP system is old, shitty api for it also, only static methods through an wrapper to an c++ library

imagine an order table.

To access an order, you would first need to open the database by calling Api.Open(...file paths) (yes, it's an fucking flat file type database)

Now the database is open, now you would open the orders table with method Api.Table(int tableId) and in return you would get an integer value, the pointer.

Now for the actual order. first you need to search for it by setting the search parameter to the column ID of the order number while checking all calls for some BS error code

Api.SetInt(int pointer, int column, int query Value)
Then call the find method.

Api.Find(int pointer)

Then to top this shitcake of an api of: if it doesn't find your shit it will use the "close enough" method of search.

And now to read a singe string 😑

First you will look in the outdated and incorrect documentation given to you from the devil himself and look for the column ID to find the length of the column.

Then you create a string variable with ALL FUCKING SPACES.

Now you call the Api.GetStr(int pointer, int column, ref string emptyString, int length)

Now you have passed your poor string to the api's demon orgy by reference.

Then some more BS error code checking.

Now you have read an string value 😀

Now keep in mind to repeat these steps for all 300+ columns in the order table.

News from the creators: SQL server? yes, sql is good so everything will be better?

Now imagine the poor developers that got tasked to convert this shitcake to use a MS SQL server, that they did.

Now I can honestly say that I found the best SQL server benchmark tool. This sucker creams out just above ~105K sql statements per second on peak and ~15K per second for 1.5 second to read an order. 1.5 second to read less than 4 fucking kilobytes!

Right at that moment I released that our software would grind to an fucking halt before even thinking about starting it. And that me & myself and I would be tasked to fix it.

4 months later and two weeks until functional beta, here I am. We created our own api with the SQL server 😀

And the outcome of all this...

Fixes bugs older than a year, Forces rewriting part of code base. Forces removal of dirty fixes. allows proper unit and integration testing and even database testing with snapshot feature.

The whole ERP system could be replaced with ~10 lines of code (provided same relational structure) on the application while adding it to our own API library.

Best part is probably the performance improvements 😀. Up to 4500 times faster and 60 times less memory usage also with only managed memory.

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?

So I love how for the last what now, 20 years companies that don't seem to have the most obvious sources of income build huge data servers, and make the general public push to digitization and lack of physical ownership *cough google cough* and then they, after encouraging dependency for storage say 'yeah well, we're going to press the reset button anyone who is being detained for 2 years or so or eating dogshit in the street by deleting all the photos attached to an account that is not logged into for that long'..... seriously.

So I developed a tool to download everything.. a few times now. Why should I have to hop from one foot to the other so much ? Thats what I'm asking.

I tell you, for such a rich company their api's are very poorly documented and there is so much goddamn documentation that is competing with other versions.

SO MANY FUCKING API'S WITH EITHER NONE OR VERY OUTDATED FUCKING JS DOCUMENTATION. I have been working on a JS Discord bot and I want it to work with some API's to for example display the weather in a certain place... I can't find ANY FUCKING TUTORIALS THAT WORK. I feel like I'm just missing something important.

Two phrases devs say to save their ass:
1. That's how this algorithm works.
2. That's the framework's / platform's / integration's / API's limitation.

Guest-user: finished my angular js 3 days course. Next have to start learning how to write API's using angular. Any heads-up?

Sudo-user: wow.Order raspberry pi from Amazon and build rocket. Let's go to moon next month 🤦🤦🏼‍♂️

TIL, shopify plus has whopping 4 requests per second rate limit on their admin rest api's... I don't know how much we pay them but shopify plus pricing starts at $2000 monthly, for a fucking FOUR requests per SECOND.

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'm way past the point of being pissed now....

So there's some software (API's, mobile app + website) that I wrote to manage supplier incentive programs in a big hurry last year - which lead to a bunch of stuff being hard-coded in to launch on time. So after last years promotion was done I took down all the services etc was very fucking clear that in order to finish & deploy it to run again I would need at least around 4 months notice.

On the surface its pretty simple but it has quite a large user base and controls the distribution of enough cash & prizes to buy a small country so the setup of the incentives/access/audit trails is not something to be taken lightly.

Then once I'm done with the setup I have to hand it over to be "independently audited" by 3 of the larger corporate behemoths who's cash it distributes (if I get a reply from one in 3-4 weeks it's pretty fast).

I only happened to find out by chance an hour ago that we are apparently launching an even larger program this year - ON FUCKING MONDAY. I literally happened to over hear this on my way for a smoke - they have been planning it since last year November and not one person thought it might be kinda important to let me know because software is "magic" and appears and works based on the fucking lunar cycle.

Can we please normalise using JSON bodies for GET requests? Makes life way more easy to just have one uniform way to communicate with API's and having different parameter formats between GET and POST request. I mean, In my opinion it is not logical to do one request with query params and others with data in the request body

What's the actual requirements to be called full stack developer? I do front-end, back-end, database, server, my own api's etc. I even have a t-shirt with "Keep calm and hug a printer". I've been doing this for 15 years and would not call me an expert in any part and certainly not privilegied for the full stack title. So what is?
If this was a humblebrag then please shoot me..

Every once in a while the flexibility of dynamic types comes back and bites you in the ars:

So I created method that returns the date significance (day, month, year) or null when no date is set.
I chose a class constant DAY with the value 0.
This is not a problem in if statements as I always use === but in this case a switch made more sense. And as you can guess no date set (NULL) was handled in the self::DAY (0) case... 😐😑😶 Silently resulting in wrong results when no date is given! #£#@$& (and other comic swearing symbols)

Even though php7 finally has decent type hinting resulting in much clearer defined API's we can still go very wrong.
More love to Go for less verbose static typing! To bad we can rarely use it at the office 😥

Working in a service based company in a project with dumb fcking manager/lead who can't plan proper workflow and design, where backend and frontend work on the same feature simultaneously and u get API's in the end of the Sprint and it has be integrated, tested and deployed in the same day...and the manager is a fcking virgin and starts drooling with backend team as they are most females and is very lenient towards them

Is it just me, or do REST API's literally rule the world right now?

Feeling like I can automate the universe.

But this is a real question. Are there reasons to avoid using web API's rather than sending data through some kind of shared database? I guess I'm not even sure what the alternatives would be right now... Are there disadvantages I should know about?

Google Maps API's are like :-
The girls that are beautiful but difficult to get started with them once
BUT after the first interaction , everything goes amazing

I got a long weekend. I decided to see what React has been up to these days.

I happen to learn more about Suspense that now it allows f**king data fetching with relay.

I decided to give it a try . First time I am actually inclined towards trying out relay just so I can see what the f**king fuss about `Suspense` is all about.

Honestly the API is much better than what it looks like .

However what the fuck is this fucking relay. They have a page in their doc called glossary and most of the sections says TODO .

I wanted to see how the fuck data driven code splitting works . Due to the lack of proper documentation about it I could not get it right for two days . I stumbled upon couple of docs / blogs / github issues about it and then finally managed to get it working .

Well the end result wasn't as cool as I thought it would. The fucking API's to achieve this needless method of code splitting is insane
There are lot of better ways to achieve this with Suspense and the API relay offers is so shitty and not fucking type safe.

Now today I wanna learn more about the directives relay offers and there is no fucking documentation about them except for a fucking bold `TODO` explanation under the sections.

If relay developers thinks that they are fucking wizards and talk all about improving fucking performance . Please don't fucking over engineer API's and make it un un maintainable for the consumers of the library

Wow this feels good . first Day in rant and I m feeling great

I have implemented RESTful API using expressJS, and another React app which will use the API's to fetch data.
I'm getting a problem of Allow-Origin Header.
what's the proper way of calling a API ?

do I use a CORS middleware and allow all origin ('*') and use Api-key as way of check authorization to prevent mis-use. ?
any other tricks ?

Fuck this documentation is shit! Param names aren't correct and some API's expecting a different parameter than it is even named for!

There are some who view software as a social construct (like Pieter Hientjes), and I think it's a valuable perspective. So if we know about the intrinsic brokenness of software, can we deduce sth about the brokenness of human interactions? Did social API's evolve to similar clusterfucks of dead entropy we have to shovel in our brains to get along?

I think the answer is an emphatic yes. And you know what's even making it worse? Software. Y'know there are all these whining about the millenials, and I too have had my experiences with stuff of that category. Like back when we searched a new roommate for our flat, we needed three rounds because people who had said yes suddenly reconsidered. Similarly now when we tried to sell our couch: people tried to push the price. Said they were interested, never showed up at the appointed time. It's like they have been spoiled by Amazon: expecting to buy with one click, for the cheapest price and send back if they don't like. And that is not a generation thing. Those old blokes ranting on the young are just as bad. They are just as lost in antisocial media as anybody else. It's a general erosion of not sticking to civility and courtesy, to the yes or no once said, coz everything is now as flexible and fluid as the digital projections of ourselves transmitted round the globe, changing in realtime.

I fucking hate it. - I'm out like this stupid Tom Cruise character in Oblivion.

I'm a Python programmer and I've been asked to build API's using Nodejs. It's been dofficult to even get the API running. Any advice on how to start? I am familiar with JavaScript

And there is a countdown
//Those new API's
#WWDC

I hate, hate, hate sockets! All the mysterious way they can fail. The subtleties, different API's if you switch between Linux to Mac, etc.

If the communication between (supposedly) deterministic machines is already such a clusterfuck, how do we even get sentences across humans and act as if we understood?

Spent days to setup a newer-Android version with reverse-proxy-HTTPS certificate in its CA store + one that'd support Google Play and signing in (old school man-in-the-middle).
FINALLY got the API calls of this 1 app whose unofficial client I wanted to make coz their main sucks ass. Just to get stuck on the phone-number-based OTP that they use for their login (:

They send a unique token for each OTP request, I assumed they're using some hard-coded string based function, which they decrypt on their backend to verify.
Downloaded their APK and decompiled. Went through dozens of weird-ass-named classes (coz decompiled). For the 2nd time I thought I had it!

But no -.- they call Google's Firebase messaging for the phone-num OTP n that function simply called firebase, looked into that service n ofc it's very tightly coupled with the calling API's backend

It was fun while it lasted I guess~~~

If you decide to move the api's in a folder fucking update the route as well..

Hello ranters,I'm a php developer ... I've been removed out of projects twice now due to the fact that database guys would say "nah we don't think php can handle this ,go learn a new language if you want to be in this team " ,then I thought to myself if I could learn another language. .Net came to my mind because the project is going to be for an Enterprise.
Which programming language do you think is the best for an Enterprise software? Thanks

EDIT: They want it in a web version so we could easily push out API's for other platforms like Android apps.

Java8: "the prevoius 2 api set of handling datetime were cumbersome, and not friendly so we introduced a whole new set of api's from jodatime"

(Looks at the new api trying to figure out how to get milis difference between a date and a timestamp, wants to kill everything and everyone in sight)

If i have to Google every simple date operations someone needs to pay

Every time I see posts about api's changing I wonder if none of those companies uses api versions, or simply deprecate functions before removing them...

I know a lot of people aren't fans of Microsoft here, but does anyone have some extended experience with using powershell?

I've been using it for creating a script that handles quite a large set of tasks for setting up and configuring some application servers and so far I have been really digging the language. Being able to invoke the script against remote hosts in parallel like ansible has been a really cool learning experience.

Admittedly it's verbose as fuck, so getting the same thing done in something like python/perl might be like half the lines of code. And I know that some of the commands illicit a "WTF?" every now and again. But I think one of the powershell tutorials I watched early on in attempting this helped make using powershell not suck ass.

Every command is basically 'verb-noun'. You don't know what the command or switches are:
> get-help "command" -showwindow

It will give you a list of options if you didn't select the exact command with get-help.

It feels* amazingly buttoned up as a scripting language and it's really cool to be able to take advantage of lower level stuff, like you can run alternative shells (we have cygwin installed on some of our servers), you can run C# code, you have access to interfacing with .NET api's. I haven't messed with anything azure yet, but being able to interface with products and services like SQL/Exchange/O365/azure/servers/desktops from the same language seems pretty cool.

Admittedly, the learning curve feels terrible though. I felt like a dunce for the first couple weeks, couldn't navigate the language at all, and was always in the docs trying to figure stuff out. I think I just needed to understand how the people developing powershell intended for it to be used. Once I was able to put two-and-two together about the verb-noun structure and how to find information/examples about the cmdlets it's been quite easy to work with it.

If anyone else has any extended experience with it, please share your thoughts/opinions. Curious to see if your experiences are/were similar to mine.

If you don't have Powershell experience, please feel free to share your opinions of Micro$haft and me for using Micro$haft products too! It's all good 😎

API's are awesome...😍

When did we decide managing Users through Cloud REST architecture was more secure than having them in an underlying DB?

Because I can't put my finger on exactly why... but I don't like it and I think it's probably less secure... and just spawned from the need to be able to make user management a subscription based service like fucking everything? When a simple MySQL or postgres and some bcrypt somewhere would be both more secure and infinitely cheaper?

I'm more used to consuming REST API's than writing them. Can any you REST peeps help me understand how a REST API could be made as secure as a SQL DB connection for user management?

What do you think the attack vectors are for a REST API User Management? Like... what's the SQL injection of REST API? Pack some extra JSON somewhere or something?

At least if I can have faith my shit's not gonna get hacked because I have to use a 3rd party REST service for User Management of Users to my own fucking app I can maybe sleep tonight.

How much ram do you generally need in a Linux server? I'm already using 70% out of 2GB on my LAMP stack, and I'm planning to deploy my website prototype to show off in interviews next year. Is 8-16GB of EEC RAM a better option for future proofing? The only thing holding me back is I don't plan to make money on this server in the immediate future so I'm trying to weigh the pros and cons. 🤔

This CentOS server runs on CLI only so the GUI isn't a factor. Eventually I'll have it host Java Spring API's which will easily take up what RAM I have left. On top of that I have 10 db on mySQL so that's another likely culprit.

I decided to start learning Rust, mainly to work with REST API's, any recommendations? Or do I look out for another language?

Fuck Swift. Such a garbage language. The last 3 days I tried multiple web server implemented in Swift for mocking API's and none of them worked. Old, not maintained, wrong documentation, wrong code examples and just low quality shit.
Finally I decided to not give a crap and move to use Wiremock and it works out of the box, start and configuration is a breeze and it just plainly works. I should have done that from the beginning.

Btw., as a warning these were the frameworks I used and you should avoid them if possible: Swifter, Embassy, Ambassador and Succulent.

I have a question. I currently use PHP when creating my API's, however, I am unsure wether to move on from it. I use either laravel or lumen to do so and use vuejs for the client apps. I am proficient in Java and JavaScript and wondering wether I should move over to spring/spark or express. I have been programming for almost 10 years now and just finished my first year in uni. I want to appeal to employers for my placement year and I know they look down on php. So, should I go with java spring/spark or express ? Other suggestions are welcome!

One of the coolest projects I've worked on was with the BBC, basically a competition attempting to find a new way to deliver news. Over 3 days we essentially brain stormed and scrum'd together a shoddy Web app using webRTC and 3 secret API's based on JSON and xml.
Fun project, performed badly but won. Moral of the story, if it looks nice, works as intended, no devs are reviewing it and you've crossed your fingers enough, you'll win ;)

What the hell am I!? I wonder if you guys can help me...

I've been programming most of my life but I've never actually been a developer by title or job role. I thought maybe if I list what I do and have done someone here could help? I'm sure there are more of you in a similar boat.

- C# and VB dev for some quick DBMS projects to help me understand and mine databases and create a nice simple view for project teams to show findings from the data to help make certain decisions.
- Automating a lot of my colleagues work with Python and if very restricted then just VBA macros in Excel and MSP. This did also include creating tools to gather data during workshops and converting the data for input into other systems.
- Brought Linux to the office with most team members now moving over to Linux with the peace of mind to know that though they do need to try solve their own problems, I can help if need be.
- Had to learn AWS and then implement an autoscaling and load balanced data center installation of a few Atlassian toolsets.
- Creating the architecture diagrams documentation needed for things like the above point.
- Having said that, also have ended up setting up all the Jira/Confluence etc. servers we use and have implemented so far whether cloud (Azure/AWS) or on prem and set up scripts to automate where possible.
- Implemented an automated workflow view in SharePoint based on SP list data and though in an ASPX page, primarily built in JS.
- Building test systems in PHP/JS with Laravel and Angular to help manage integration between systems. Having quite a time right looking into how to build middleware to connect between SOAP and REST API's, the trouble caused more by the systems and their reliance on frameworks we're trying to cut out of the picture.
- Working on BI and MI and training a team to help on the report creation so that I can do the fun creative stuff and then set them to work on the detail :)

Actually it seems safe to say that it seems that though I've finally moved into a dev office (beforehand being the only developer around) I seem to be the one they go to when a strategic solution is needed ASAP and the normal processes can't be followed (fun for someone with a CompSci degree and a number of project management courses under the belt... though I honestly do enjoy the challenges)

But I always end up Jack of all but master of, well hopefully some at least. let's not even get started on the tech related hobbies from circuit design and IoT to Andoid / iOS and game dev and enjoying a bit of pen testing to make sure we're all safe at work and at home.

As much as I don't like boxes, I'm interested to know if there is in fact a box for me? By the way, the above is just a snapshot of my last two years minus the project management work...

Me: removed appsettings.development.json from git index, because every time we pull, we have to correct the files of 8 api's, just to be able to build that ducktape solution

Other devs: we can't build anymore, our appsettings.development.json are gone!!!!!

Manager: (total silence on my 'good morning') you broke our application!!!!

Me: checks 8 appsettings.development.json in

Almost everybody HAPPY

We ended up finding ourselves with a bunch of tables that have mostly the same columns, but differ by a few. Every time we consume a REST API, we store the `access_token`s and expiration dates and the other OAuth data. However, each provider has slightly different requirements. For example, we store email addresses for email api's, other providers require us to store some additional information, etc. etc.. I'm tempted by the flexibility and lack of schema brought by document databases, but not enough to use one since they're generally slower and we already have everything in SQL. So I got the idea of using JSON columns to alleviate this issue: have a single table for all REST integrations (be it outlook or facebook), and then store the unique integration data inside of this JSON column for "additional data". This data is mostly just read, not filtered by (but ocasionally so). Has anyone had experience with this? How's the performance of JSON fields? Is this a good practice or will it get harder with more integrations?

Building a click/link insight tool. Might leverage geobytes.com. Nice API's, geolocation data and free/low cost pricing.

Laid the foundation and got a patent application for a custom Enterprise PHP framework that interacts with all of the big chat AI api's and can communicate with the outside world as IVR, SMS, Webchat, etc. Had corporate guidance but a lot of leeway and was the sole developer for a full year of the project. I've since left the company and they expanded the team and are soon to go to production with it.

Api's by heart. All the time that could save.

Freaking RESTful API's.
Never worked with one before and I'm using Django Rest Framework.
Currently working (trying to) with Angular 2.
Spent lots of time trying to make angular work because ng needs arrays instead of objects when I finally realized it was a matter of the API.
Have no idea what I'm doing

Visualize the entire complexity of the content within the project so that you know what data users will need to access, and compartmentalize those in to separate modules that you can build on over time. Think about any limitations with accessing that data (does the user have that role, what if the data is accessed simulateously, how to handle the same user accessing from different devices etc).
Think about the devices being used - is it going to be a website, an app, both? How best then to access the data? Direct access to a database, or an API system?
Then think about the front-end design and how to simplify the view right down as much as you can. Again, break it down in to modules.
Then decide on the technology you want to use, and what libraries would help simplify things.

These days I like to use JSON API's to access DB content because app and web technologies change quite often but the API will be accessible to whatever I use to build it.

For websites I love using Laravel, which simplifies the back-end tasks, and mdbootstrap which simplifies the front-end tasks and looks "appy".

Just talked to a Java dev that develops web apps with SOAP API's about testing. Talked to him about SOAP UI ...He didn't know what SOAP UI was. Is he f*cking trolling me or just a guy with the wrong job? I mean he seriously refused to have ever heard about it. Dafuq?

Guys i need your help, i'm in my 3. semester where i have a REST project and therefore i need to implement some APIs and for this i shoud write a documentary where i discuss my decisions. And here is my problem
I need to implement a payment Api but i cant find a Big difference between the Visa and MasterCard Api, maybe some of you already worked with this api's and can help me out
What's better and why.

So I want to start with rest API development in Spring Boot. Where's a great place for 'all-you-need-to-know' related to Spring? I already built other REST API's so I just need a quick getting started and know how to organise,configure etc. my java project.

Do only developers have to do such tasks like Cinderella sorting out the lentils from the ashes?

Poor co-workers
* who had to program against the undocumented closed, ever changing API from Exchange Server, supporting over a decade old versions
* who had to compile a c++11 compatible clang or gcc on some sick old OS and almost got it working with compiling a fresher gcc with one that got stuck in one of the build stages.

When the client amends the content and removes critical items to be surfaced via the API just because. Fuck it I hate working with immature API's, guess fraud data till they fix it I hate doing shite twice.