Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I don’t usually recommend movies to a lot of people, but if you like going to the movies, I highly, highly recommend you see “Searching”. Its wide release in the U.S. is today and it will be out internationally soon I think.
It’s probably the best thriller movie I’ve ever seen, and the best movie I’ve seen in last few years, and I see a lot of them. The tech in it is awesome, and how the movie is presented will bring back tech memories and it really is a trip down memory lane. The movie has a bit of everything. An awesome story, awesome suspense, and great use of technology and social media.
10/10, definitely see it!32
This is a view from a rooftop in NYC that I sometimes get the pleasure to work from. I really like the view and it’s pretty quiet usually. It also overlooks one of my favorite buildings, the Empire State Building.
I’m looking forward to seeing everyone else’s desks, setups, and remote/outdoor workspaces.
We’ll be featuring them on our recently launched devRant Instagram account, devDesks (https://www.instagram.com/devdesks).54
One of my favorite aspects of devRant has always been getting to learn more about the awesome people who use it. Beyond just the awesome stories posted by many here, one of my favorite ways to learn about and feel connected to the people here has always been desk/setup reveals. I personally love seeing different kinds of setups from all over the world, knowing that’s what the people here use to do their work and compute in general.
As an experiment, we want to try a few different things to highlight desk/setup/remote coding location posts. First, we’ve created the first devRant Instagram account, which is completely focused on developer desks/setups/workstations/remote coding. Please check it out here and follow: https://www.instagram.com/devdesks/
I want to use the account to bring more attention to the wide assortment of setups the awesome members of the devRant community post from all over the world. We’ll promote cool desk/setup/remote work images that are posted on devRant to the Instagram account for more exposure/additional audience.
Beyond that, I also want to try to come up with a way to better organize all of the desk/setup posts on devRant and encourage more of them. One kind we don’t see that often that I personally really enjoy is people coding with their laptops in locations that show the culture of their country or something special about the region they are from. Personally, I’m going to try to post some of those for where I live and work.
So how can you help with this effort? It’s easy! We encourage people to post their setups/working remotely pics and we will start featuring them on the Instagram account and hopefully elsewhere in the devRant app for some increased visibility/searchabilty over what we have now (since pics are kind of hard to search).
Also, we plan to make the weekly rant this week “post your setup,” so maybe wait until then to post, and you can work now on getting that awesome shot :) I know a lot of people here love photography like I do, so I think that part is fun too.
Please let me know if you have any ideas or questions about this, and I’m looking forward to seeing the desks/setups of many more devRanters in the next few days!
P.S. not a requirement, but one thing I think makes these photos better looking through a lot of them is when there is code visible in some way.52
When I worked for an online dating app, at one point we had the ridiculous idea to try to take a popular LinkedIn feature and convert it to a dating app feature in order to capitalize off of the success LinkedIn had with it.
The feature was LinkedIn endorsements. The idea was to allow the dating app users to get endorsements from people in their contacts lists on certain traits/features from a defined list (ex. Funny, smart, etc.). It wasn’t a terrible idea on the surface, but the way we planned to execute on it was insane and everyone knew it was going to fail. To avoid any controversy all of the endorsable terms were watered down to the point where no one would ever find using them/asking their friends for endorsements to be any fun. And the worst part was how we planned to get people to ask their friends for endorsements - management wanted us to build a contact list importer and just spam email contacts with “please endorse me” emails. The whole thing was ridiculous.
No one, including myself, wanted to build the feature/spam tool but management really wanted it so we had to build it. Like expected, it failed very quickly when it was clear no one cared about getting their real life friends to endorse them on some dating app, and the spam contacts took was ineffective and... spammy.14
For about the last 24 hours, there was unfortunately an issue with the algo feed where scrolling did not show more rants. This has now been fixed.
One of our background queues stopped processing for some reason which caused rants to not properly get marked as read for algo.
If you notice any other issues with this, please let me know. Thanks!13
@trogus and I have been working on some cool devRant features that we're going to be launching very soon. In addition, as some might remember from a recent discussion, we're trying to bring in some more revenue (so we can at least break even) to avoid having to think about advertisements in the app. To do that, we're brainstorming possible useful add-on features maybe that we can offer to devRant++ members, or possibly offer for a different plan or as a complimentary product (under the devRant umbrella, but separate in terms of where it's accessed.)
If you have a few minutes, we'd appreciate some feedback by taking this survey @trogus put together: https://surveymonkey.com/r/DT9MKVN/
Also feel free to discuss here too if you want, and thanks everyone!51
This was during the first day of my first real dev job, straight out of college. I didn’t have have much experience with version control since I did mostly solo projects in college, and I wasn’t exposed to SVN or Git in school at all.
One of the senior devs was going to give me and another new guy a brief overview of the codebase. He sets us up with the GitHub repo for the codebase and tells us to clone the codebase locally. I didn’t really know what this meant but I felt kind of embarrassed to ask, so I just clicked “download as zip” on The GitHub repo.
After a minute he saw what I had done and was like “yeah, that’s not what you want to do” and showed me how to clone it. I was kind of embarrassed but I learned Git pretty quickly after that.
I don’t really have a moral to this story except that “no question is a stupid one” is much easier said than done for many people, and it can be embarrassing to ask certain questions sometimes.11
Hey everyone! @trogus and I are headed to TechDay New York tomorrow (May 10) and there will be a devRant booth in the social network section. If any devRanters are attending, you should definitely stop by our booth! There will be free swag and we’d love to meet some fellow ranters!42
We’ll be doing maintenance on our web server on Sunday, April 29 at around 3pm EDT. The app will probably be unreachable for about 10-15 minutes over that time. We apologize for the inconvenience and we’ll be sure to get it back up as quickly as possible.
Feel free to let me know if you have questions.40
I have a couple of stories that I think are memorable from co-workers quitting in funny/interesting ways.
1. At one of the first companies I worked at, they gathered everyone to make an announcement that began with, “this is just a reminder, any heavy objects/packages need to be removed through the freight elevators, and cannot be taken through the main lobby.” We’re all thinking OK... why are you telling us this. Next part of the announcement was, “so and so (co-worker) is no longer with the company.” Apparently, which we found out later, the guy either quit/and/or got fired and wheeled his desk chair out the front door through the lobby (keep in mind this is an office on one of the busiest avenues in Manhattan). The whole thing was crazy. That’s the last we ever heard about him.
2. This one was strange. A really quiet dev at one of my previous companies was clearly constantly bored at work (he barely had any responsibility and was pretty much ignored) but the job was pretty cushy. One day, he was out from work, and no one thought much of it. Then he was out another day, then another, and before we knew it, it was like a week. No one knew where he was. Eventually, he sent an email saying he got stuck out of he country or something and he wouldn’t be coming back. Ok... weird, but kind of made sense.
But, one of our ops guys was able to see the ip/location of where he logged on to send the email, and it was right from NYC! So pretty much this guy was just fed up, left one day (with no notice), and just never came back. And then lied that he was out of the country when trying to explain is hasty departure.13
I worked with a good dev at one of my previous jobs, but one of his faults was that he was a bit scattered and would sometimes forget things.
The story goes that one day we had this massive bug on our web app and we had a large portion of our dev team trying to figure it out. We thought we narrowed down the issue to a very specific part of the code, but something weird happened. No matter how often we looked at the piece of code where we all knew the problem had to be, no one could see any problem with it. And there want anything close to explaining how we could be seeing the issue we were in production.
We spent hours going through this. It was driving everyone crazy. All of a sudden, my co-worker (one referenced above) gasps “oh shit.” And we’re all like, what’s up? He proceeds to tell us that he thinks he might have been testing a line of code on one of our prod servers and left it in there by accident and never committed it into the actual codebase. Just to explain this - we had a great deploy process at this company but every so often a dev would need to test something quickly on a prod machine so we’d allow it as long as they did it and removed it quickly. It was meant for being for a select few tasks that required a prod server and was just going to be a single line to test something. Bad practice, but was fine because everyone had been extremely careful with it.
Until this guy came along. After he said he thought he might have left a line change in the code on a prod server, we had to manually go in to 12 web servers and check. Eventually, we found the one that had the change and finally, the issue at hand made sense. We never thought for a second that the committed code in the git repo that we were looking at would be inaccurate.
Needless to say, he was never allowed to touch code on a prod server ever again.9
EDIT: devRant April Fools joke (2018)
Hey everyone! As some of you have already noticed, @trogus and I made a decision (based on the suggestion of some members of the community) to start transitioning all scores on the app to binary. We have started by making all user scores in our mobile apps and website (if you’re logged in) appear in binary. We think this makes the app more fun while remaining usable at the same time!
Please let us know what you think and happy binary-reading!102
I wanted to post a note on devRant community etiquette and rule-breaking behavior we’ve been seeing lately to make clear it will not be tolerated. This is pretty much a rehash of this rant, https://devrant.com/rants/609739/... and also our official rules which I highly encourage people to read: https://devrant.com/rules
I’ve noticed an influx of a select group of members, mostly older users, expressing a distain towards other users or declaring content they dislike “shouldn’t be posted”, “please stop”, etc. If you find yourself about to post that, as per our rules, please don’t. It blatantly violates our rules and we are going to start cracking down on it much more. Whether you have 30k+ points or 10, we will apply the rules fairly to everyone and not give breaks to specific people, which admittedly I’ve done in the past.
If we see this behavior in rants/comments first we will give a warning (and the rant/comment will be deleted) and the next offense is a ban.
A valid question (even though I’ve answered it before) might be why does this need to be a rule? Simply put, it’s a rule for a number of reasons: posts like described try to inflict one’s will upon the entire community (even though we have a Democrat voting process...), they create confusion (almost every time they try to sound official, ex. “Stop doing this”), and beyond those two main reasons, they literally accomplish nothing because they offer no constructive methods of achieving what’s being requested, and only a fraction of the community will actually see it.
Here’s an example of what’s not allowed and what is allowed:
- Allowed: posting an issue on our GitHub issue tracker saying “I really dislike seeing this type of rant in my algo feed, here’s some ideas I have to improve the algo and add more personalization so I can see what I want.”
- Allowed: posting on GitHub issue tracker: “I found this awesome image similarly algo that I think can improve the ‘repost check feature’ - you guys should check it out and see if it might be good”
- Not allowed: “Omg stop shitposting windows update rants and Linux rants I hate them. Go post this type of rant because that’s what everyone really wants to see.”
One is constructive an the other is merely an opinion expressed as an enforcement of a self-made rule on the community and tries to tell other people how they should use devRant.
I cringe when people tell others how to use devRant because without fail when I see those posts, I go through that person’s rant/comment history and I nearly always see them using devRant in some kind of way I disagree with or isn’t exactly what I like to see. But that’s OK. I understand I’m not going to enjoy everything posted and I’m also not going to agree with everything posted. But I think it’s fair for those same people to then lecture on what isn’t appropriate to post on devRant, and it’s even more silly when their posts are sometimes irrelevant to development and the posts they are complaining about are relevant.
In the end, based on the large majority of feedback we get, we want to make devRant a place where everyone feels comfortable expressing themselves and doesn’t have to think about possibly getting ridiculed every time they post and that don’t have people trying to dictate what kind of ideas they are allowed to post. We also realize there’s types of content people don’t enjoy, but telling others not to post it is not the solution. We will soon be launching post type filters that will make filtering rants by post type possible.
Please let me know if you have any questions and thanks for reading.69
As a long-time iPhone user, I am really sorry to say it but I think Apple has completed their transition to being a company that is incompetent when it comes to software development and software development processes.
I’ve grown tired of hearing some developers tell me about Apple’s scale and how software development is hard and how bugs should be expected. All of those are true, but like most rules of law, incompetence and gross negligence trumps all of that.
I’m writing this because of the telugu “bug”/massive, massive security issue in iOS 11.2.5. I personally think it’s one of the worst security issues in the history of modern devices/software in terms of its ease of exploitation, vast reach, and devastating impact if used strategically. But, as a software developer, I would have been able to see past all of that, but Apple has shown their true incompetence on this issue and this isn’t about a bug.
It’s about a company that has a catastrophic bug in their desktop and mobile platforms and haven’t been able to, or cared to, patch it in the 3 or so days it’s been known about. It’s about a company, who as of a view days ago, hasn’t followed the basic software development process of removing an update (11.2.5) that was found to be flawed and broken. Bugs happen, but that kind of incompetence is cultural and isn’t a mistake and it certainly isn’t something that people should try to justify.
This has also shown Apple’s gross incompetence in terms of software QA. This isn’t the first time a non-standard character has crashed iOS. Why would a competent software company implement a step in their QA, after the previous incident(s), to specifically test for issues like this? While Android has its issues too and I know some here don’t like Google, no one can deny that Google at least has a solid and far superior QA process compared to Apple.
Why am I writing this? Because I’m fed up. Apple has completely lost its way. devRant was inaccessible to iOS users a couple of times because of this bug and I know many, many other apps and websites that feature user-generated content experienced the same thing. It’s catastrophic. Many times we get sidetracked and really into security issues, like meltdown/spectre that are exponentially harder to take advantage of than this one. This issue can be exploited by a 3 year old. I bet no one can produce a case where a security issue was this exploitable yet this ignored on a whole.
Alas, here we are, days later, and the incompetent leadership at Apple has still not patched one of the worst security bugs the world has ever seen.106
This coming Sunday (Feb 4), at about 12AM EST, devRant will be going down for scheduled maintenance (database server maintenance). The maintenance shouldn’t take more than about 15 minutes.
Feel free to let me know if you have any questions and apologies for the inconvenience!37
Huge congrats to @linuxxx for being the first ever member of the devRant community to reach 100,000++
This is an awesome accomplishment and @linuxxx earned all of his ++ with awesome stories and has represented everything the devRant community is about while getting there.
So once again, congrats @linuxxx, and thanks for everything you have contributed to devRant!56
I’ve had a good amount of incompetent co-workers in the past. One that stands out was this junior developer who worked at one of my previous companies. He was incompetent, but that wasn’t even his worst attribute. He was incompetent, and worse, he had a piss-poor attitude.
Myself and a few other devs at the company tried to help him, but he would literally get mad when people tried to help him. Sometimes he would even call one of us over and start getting snarky with us as we tried to help him. He was a piece of shit and a shitty developer. I don’t think he built one complete feature or fixed one bug in the year he was at the company before he was eventually fired.
Oh, and aside from his incompetence and shitty attitude, he had no sense of humor. It was so annoying. My friend and I made a little song based on his name and a group that sounded like his name, and he got pissed. We always used to sing it anyway after that and it always riled him up. I feel a bit bad about that now but he pretty much got mad at everything so whatever.
One of my favorite memories of him is when he was leaving one day, my good friend/co-worker and I were having a Nerf gun battle. The junior was leaving the office, and my friend tried to get him involved in the battle and shot him, but accidentally hit him in the back of the head. He said nothing, didn’t turn around, and just walked out lol. He was not happy about it.10
First off, a Merry Christmas to everyone who celebrates, happy holidays to everyone, and happy almost-new-year!
Tim and I are very happy with the year devRant has had, and thinking back, there are a lot of 2017 highlights to recap. Here are just a few of the ones that come to mind (this list is not exhaustive and I'm definitley forgetting stuff!):
- We introduced the devRant supporter program (devRant++)! (https://devrant.com/rants/638594/...). Thank you so much to everyone who has embraced devRant++! This program has helped us significantly and it's made it possible for us to mantain our current infrustructure and not have to cut down on servers/sacrifice app performance and stability.
- We added avatar pets (https://devrant.com/rants/455860/...)
- We finally got the domain devrant.com thanks to @wiardvanrij (https://devrant.com/rants/938509/...)
- The first international devRant meetup (Dutch) with organized by @linuxxx and was a huge success (https://devrant.com/rants/937319/... + https://devrant.com/rants/935713/...)
- We reached 50,000 downloads on Android (https://devrant.com/rants/728421/...)
- We introduced notif tabs (https://devrant.com/rants/1037456/...), which make it easy to filter your in-app notifications by type
- @AlexDeLarge became the first devRant user to hit 50,000++ (https://devrant.com/rants/885432/...), and @linuxxx became the first to hit 75,000++
- We made an April Fools joke that got a lot of people mad at us and hopefully got some laughs too (https://devrant.com/rants/506740/...)
- We launched devDucks!! (https://devducks.com)
- We got rid of the drawer menu in our mobile apps and switched to a tab layout
- We added the ability to subscribe to any user's rants (https://devrant.com/rants/538170/...)
- Introduced the post type selector (https://devrant.com/rants/850978/...) (which will be used for filtering - more details below)
- Started a bug/feature tracker GitHub repo (https://github.com/devRant/devRant)
- We did our first ever live stream (https://youtube.com/watch/...)
- Added an awesome all-black theme (devRant++) (https://devrant.com/rants/850978/...)
- We created an "active discussions" screen within the app so you can easily find rants with booming discussions!
- Thanks to the suggestion of many community members, we added "scroll to bottom" functionality to rants with long comment threads to make those rants more usable
- We improved our app stability and set our personal record for uptime, and we also cut request times in half with some database cluster upgrades
- Awesome new community projects: https://devrant.com/projects (more will be added to the list soon, sorry for the delay!)
- A new landing page for web (https://devrant.com), that was the first phase of our web overhaul coming soon (see below)
Even after all of this stuff, Tim and I both know there is a ton of work to do going forward and we want to continue to make devRant as good as it can be. We rely on your feedback to make that happen and we encourage everyone to keep submitting and discussing ideas in the bug/feature tracker (https://github.com/devRant/devRant).
We only have a little bit of the roadmap right now, but here's some things 2018 will bring:
- A brand new devRant web app: we've heard the feedback loud and clear. This is our top priority right now, and we're happy to say the completely redesigned/overhauled devRant web experience is almost done and will be released in early 2018. We think everyone will really like it.
- Functionality to filter rants by type: this feature was always planned since we introduced notif types, and it will soon be implemented. The notif type filter will allow you to select the types of rants you want to see for any of the sorting methods.
- App stability and usability: we want to dedicate a little time to making sure we don't forget to fix some long-standing bugs with our iOS/Android apps. This includes UI issues, push notification problems on Android, any many other small but annoying problems. We know the stability and usability of devRant is very important to the community, so it's important for us to give it the attention it deserves.
- Improved profiles/avatars: we can't reveal a ton here yet, but we've got some pretty cool ideas that we think everyone will enjoy.
- Private messaging: we think a PM system can add a lot to the app and make it much more intuitive to reach out to people privately. However, Tim and I believe in only launching carefully developed features, so rest assured that a lot of thought will be going into the system to maximize privacy, provide settings that make it easy to turn off, and provide security features that make it very difficult for abuse to take place. We're also open to any ideas here, so just let us know what you might be thinking.
There will be many more additions, but those are just a few we have in mind right now.
We've had a great year, and we really can't thank every member of the devRant community enough. We've always gotten amazingly positive feedback from the community, and we really do appreciate it. One of the most awesome things is when some compliments the kindness of the devRant community itself, which we hear a lot. It really is such a welcoming community and we love seeing devs of all kind and geographic locations welcomed with open arms.
2018 will be an important year for devRant as we continue to grow and we will need to continue the momentum. We think the ideas we have right now and the ones that will come from community feedback going forward will allow us to make this a big year and continue to improve the devRant community.
Thanks everyone, and thanks for your amazing contributions to the devRant community!
Looking forward to 2018,
- David and Tim56
We used to do this more often - but to kind of bring it back - what is everyone working on this weekend?
I’m working on some new API endpoints for the awesome new devRant web version that @trogus made that we’re releasing soon.
Share your weekend project!117
I’ve been inspired by programming many times, but a few early moments really stand out for me. Some of those most memorable early moments came when I developed Flash games with my friend in high school.
Growing up, at this point in time, around 2005, Flash games were really hot. All the kids in my school played games on addictinggames.com during any classes that took place in the computer lab, and when my friend and I started making games, it was our dream to get a game featured on addictinggames.com.
When one of our early games ended up getting featured, we were absolutely ecstatic and I’ll never forget the feeling of seeing our own work on this game website that we loved for years prior and that so manly people at our school used. It was the coolest thing and I think went a long way to encouraging me to continue to want to create things, after seeing the impact we were able to make with a simple game (as two high school students).
And I think that shows the beauty of the internet today and the power people with few resources have to get stuff out there. I think it’s maybe gotten harder as of late since there’s probably more competition, but I also think the audience is ever-growing and I hope many more people get to experience that awesome feeling of having something you worked hard on become popular.14
This happened at my previous job where I worked for a dating app. It was at a time where the CEO was trying to turn the dating app into “more than a dating app” by adding tons of social features. We always had “interests” which allowed users to see what interests they had in common with another person, but he wanted to take the social component even further.
So with that, he decided we needed an “activity feed.” The activity feed would show what various Facebook connected users were liking on Facebook, posting on Facebook, etc. On a dating app. Where the majority of the audience was > 50 years old. The idea was absolutely ridiculous and everyone but the CEO knew it was destined for failure before we started building it.
But that’s not the best part. The best part was when we launched the activity feed component. We launched it late on day and went home shortly after. The next morning, we came in, and checked on the activity feed to see what was doing. It was literally all spammers liking porn/sex related stuff on Facebook. It was a complete disaster. All garbage but not just boring garbage - completely obscene garbage.
And just like that, the activity feature came and went in the course of a few days.18
Today we have an exciting devRant announcement! As many observant members of the community have problably noticed, since launch we've been using the domain name devrant.io since the .com was already taken. Today, we're happy to announce, we now own devrant.com and it is now the official devRant URL!
How did this happen you ask? The devrant.com domain was already owned by a developer named Wiard when we launched devRant. It took a while to track him down, but when we did, turned out he saw the good we were doing and wanted to help the devRant community by generously offering us the .com domain for a very reasonable exchange (considering that we are a self-funded bootstrapped startup!).
Since Wiard recently started writing a blog on devrant.com, he had to find a new home for it. His new blog is https://sysrant.com and I encourage everyone to check it out! Great topical/educational dev/sys-admin related articles? Check. Someone who cares about the devRant community and allowed us to leave the firey hell that is .io? Check. So check it out!!
Some technical info:
This change is immediate and all devrant.io non-api requests will now redirect to devrant.com. We might have missed a few things (purposely or accidentely) so we're going to be going through and converting anything that's left. If you use the devRant API, your implementation should not break since API requests are meant to be excluded for now, but I highly recommend switching any API URLs to https://devrant.com so you can avoid issues in the future if we decide to stop redirecting devrant.io API requests. Also one note, there was an issue for about a minute after we turned on the redirected where some API requests to devrant.io might have 301 redirected to devrant.com. If an app you were using broke, try clearing whatever cache the 301 redirect might be stored in and the issue should go away.
Feel free to post any questions you might have here (and please let me know about any issues you might discover!), and once again, huge thanks to Wiard!79
Announcing a few new devRant Android/iOS features, available immediately in the latest versions of the devRant app which just went live.
1. As pictured, you can now easily scroll to the bottom of any long rant by selecting “scroll to bottom” in the ... menu of any rant with >= 10 comments.
2. At the bottom of any rant that has at least 1 comment, you’ll now see a button that allows you to refresh the rant (and scrolls to the bottom) so you can see new comments if there are any.
3. Any rant can be refreshed by tapping the “Rant” title in the title bar.
How did we come up with these awesome ideas/decide to add these features? For most of them, we didn’t! At least 2 of these were recently requested by devRant users (some requested a bunch of times) and we heard everyone and saw how much these were needed. Remember, you can always suggested features in our GitHub issue tracker: https://github.com/devRant/devRant - we always appreciate feature suggestions and ideas for improvements!
Just to add one note - we still have plans to improve commenting functionality, but we’re hoping for the time being these additions make things a little more intuitive.
Let me know if you have any questions, and thanks everyone!23
A devDuck update!
First off, thank you to everyone who has purchased a devDuck (or a bunch!) and thanks to all who have given us feedback. @trogus and I are thrilled at the incredible response these ducks have gotten. If you haven’t seen them yet, you can check them out at https://devDucks.com or the devRant Swag Shop (https://swag.devrant.io).
We are trying to process all of the orders as quickly as possible and our goal is to have all current orders out by the middle of this coming week. Many orders have already shipped, but if yours hasn’t, rest assured it will very soon!
If you ordered a Java devDuck or cape, your order might be delayed a bit until the middle of this coming week because Java seems to be a heavily-demanded cape and we needed to get the material shipped in to make more of that, specifically.
So far we’ve gotten some awesome feedback from the community. A short list of possible future additions based on what’s been requested: Go devDuck, Kotlin devDuck, Perl devDuck, Android devDuck, and possibly some devDuck accessories like little hats, sunglasses, headphones, etc. If you have any other ideas just let us know:)
Lastly, please know that even with the launch of devDucks, we remain extremely committed to the devRant product and we have some very exciting big devRant features coming very soon.
Thanks again everyone!29
Our live stream announcement and Q&A will be going live in less than 30 mins (9pm EDT)!
The event is here: https://youtu.be/Vk7TIKadYHk
We will be taking questions on the YouTube chat, feel free to ask whatever you want!
Thanks to all who tune in, hope you enjoy!
EDIT: big thanks to everyone who joined us and participated! The replay is available at the YouTube link above, and you can check out devDucks in the devRant swag store (https://swag.devrant.io) or the page we set up at http://devducks.com20
Big congrats to @AlexDeLarge for being the first devRant member to hit 50,000 ++!
A pretty awesome accomplishment highlighting great contributions and content.80
Get ready for the first ever devRant live stream event! @trogus and I will be making an exciting announcement/launch live on our YouTube channel (https://www.youtube.com/devrantapp) this Wednesday (October 4th) at 9pm EDT. After the announcement we will also take some questions from devRant users who are watching. The questions can be about the announcement or anything devRant-related in general. We hope to get some fun questions so feel free to ask anything you want.
We look forward to having some fun with our first live stream! If you can't make it, don't worry, the replay will be available on YouTube and we'll likely do some more streams in the future. Please let me know if you have any questions and we hope many of you can join us!
Edit: the stream will be available here once it begins tomorrow: https://youtube.com/watch/... I will also post another announcement rant when we go live!56
One time a company I worked for tried to fuck me over and not pay me the referral fee that was promised for referring an employee. They hired the person I referred for a position that was advertised as having a referral fee paid after 6 months.
After the 6 months were up, I went in to HR to ask when I could expect to see the money, and they said “oh, you’re not eligible to receive the referral bonus because we hired so and so as a contractor (full-time) instead of an actual full-time employee.” And I was like... fuck that shit, they never mentioned that to me and I didn’t burn a referral lead so they could hire the person as a contractor and avoid paying me the advertised fee. I was absolutely livid and couldn’t believe it after I had been expecting this money for 6 months.
I felt cheated and none of my colleagues at the company could believe they’d stoop so low to not pay a highly-valued employee an advertised referral bonus. I had lots of battles with management over it, and eventually ended up with a portion of the promised fee, but not the whole thing.27
We're currently experiencing major issues with the devrant.io domain due to another outage/problem with .io domains themselves. More info here: https://news.ycombinator.com/item/...
The issue is also being reported on twitter.
If you receive a host not found, connection error, etc. connecting to devRant, this is why. We'll keep you updated and in the future we will probably be switching away from .io at least for our API.
Thanks for the patience.29