Details
-
AboutDesigner | Developer
-
LocationMumbai
Joined devRant on 5/3/2017
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
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Frontend & backend dev conversation
Backend Dev: what will you be working on?
Frontend dev: i will be creating a nice animated loader. You?
Backend Dev: i will be working on optimizing the backend so that no one can see your loader.
🤣🤣🤣🤣7 -
Some ideas for variable names. Thank me later :))
1. bool sheet;
2. int entionally;
3. char mander;
4. double penetration;
5. string cheese;
6. long schlong;23 -
I'm the biggest dumbass, the laziest procrastinator I know of..
Joined devRant in June 2017, got eligible for the stickers in a week's time, sent a mail requesting them, but never received it. Given the size of our community, I thought I'm way behind in the list and probably receive them in few months. After a year, I totally forgot about it.
But, the colossal stupid that I am, had also lost the key to my mailbox (the physical one). I never cared about the lost key, because who sends post these days !!!
When I finally got a duplicate key for my mailbox after 2 years, guess what I found.. a first class international mail from devRant which arrived on July 2017 🤦♂️🤦♂️🤦♂️, couple of weeks after I originally requested
But, yay... I finally got them..16 -
EDIT: devRant April Fools joke (2019)
-------------------------
Hey everyone!
Today, @trogus and I are very happy to announce a devRant feature that we’ve been working on for many months. After extensive time and money investment, it’s finally here! Introducing, pixelated avatars!
@trogus came up with this awesome idea about a year ago, but we couldn’t get it just right so we had to tons of work/research to make those pixelated avatars give the full sense of retro and ULTIMATE pixelation. We think everyone will appreciate how this effort turned out.
Anyway, let us know what you think, and we hope you enjoy!
p.s. here is @trogus’s avatar - the model we used to make sure the feature is perfect!51 -
Sales employee Bob wants a clickable blue button.
Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.
Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)
Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).
These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.
Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".
The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.
What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?
Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.
Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.
But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.
So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.
On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.
In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.
This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.23 -
Yet another commercial seminar upset I won't give up a day of my time to fly to the UK to speak at the event for no payment or reimbursement for my travel.
But of course I should think about the exposure and networking opportunities! 😕8 -
Have you ever wondered we programmers have so many strong communities.... Stackoverflow, devRant, Reditt, etc...
No other profession has such communities... Why? Why?
Because, we haven't built one for them.... 😂😁61 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.52 -
Last year I built the platform 'Tindex'. It was an index of Tinder profiles so people could search by name, gender and age.
We scraped the Tinder profiles through a Tinder API which was discontinued not long ago, but weird enough it was still intact and one of my friends who was also working on it found out how to get api keys (somewhere in network tab at Tinder Online).
Except name, gender and age we also got 3 distances so we could calculate each users' location, then save the location each 15 minutes and put the coordinates on a map so users of Tindex could easily see the current location of a specific Tinder user.
Fun note: we also got the Spotify data of each Tinder user, so we could actually know on which time and which location a user listened to a specific Spotify track.
Later on we started building it out: A chatbot which connected to Tinder so Tindex users could automatically send a pick up line to their new matches (Was kinda buggy, sometimes it sent 3 pick up lines at ones).
Right when we started building a revenue model we stopped the entire project because a friend of ours had found out that we basically violated almost all terms.
Was a great project, learned a lot from it and actually had me thinking twice or more about online dating platforms.
Below an image of the user overview design I prototyped. The data is mock-data.51 -
Instead of learning how CCS works I've been adding a bunch of floats in different directions until the layout looks alright. This has been going on for years.5
-
$ npm audit
> found 19 vulnerabilities (10 low, 5 moderate, 3 high, 1 critical)
$ npm audit fix
> fixed 0 of 19 vulnerabilities in 11987 scanned packages
> (use `npm audit fix --force` to install breaking changes; or do it by hand)
$ npm audit fix --force
> npm WARN using --force I sure hope you know what you are doing.
Me too, buddy. Me too.1 -
Another attempt at trying to get support for weakening encryption recently.
An FBI spokesperson said something like 'we can put people on the moon, why can't we just create law enforcement-accessible encryption? i just don't buy it."
Fuck off and die.28