Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "twist of events"
-
In a twist of events, I got myself into a tight paper deadline to help a friend, about a project that I haven't even been a part of.
But, now that the paper is done, hopefully my friend has to go to the conference just to pay for his sins (mostly writing/literature sins), and hopefully I get back into my machine learning adventures!
... I'm super fuckin exhausted tho.
Yesterday I had a panic attack while walking to the grocery shop. Was fun! Always wanted to feel like dying without actually dying! Yay! 🤪 (Wasn't that serious. Don't overreact)3 -
working from client's office from last 3 months.
The project manager whom I'm working with asking me to Join full-time there.
The company is way bigger than my current employer, package definitely will be 2x or more than my current package and I'm not sure.2 -
So me and a couple of my teammates were developing a website for artists where all the things related to artists such as artworks, events, geolocation info etc. happen to live.
2 months down the line, the client comes up with another team who is supposed to develop iOS and Android apps to give the users the ability to leverage this data.
Now this team is so annoying that they want the API according to the specifications they provide. That's really weird. API should be generic, right?
But no, this doesn't end here, the PM of mobile app team comes up with a specification document for the API and what does it contain, a few endpoints which go as below:-
/home - To bring all the home screen data
/events - To bring all the event screen data. But here is a twist, on Event screen, they have defined different sections for Upcoming Events, Workshops, Talks etc. And for each event type they don't want a filtered API but just this single endpoint which will contain all event types data in their own JSON keys.
FML
:/4