Even if you uninstall MS Teams, it will find a way to start again.

Hey everyone,

We have a few pieces of news we're very excited to share with everyone today. Apologies for the long post, but there's a lot to cover!

First, as some of you might have already seen, we just launched the "subscribed" tab in the devRant app on iOS and Android. This feature shows you a feed of the most recent rant posts, likes, and comments from all of the people you subscribe to. This activity feed is updated in real-time (although you have to manually refresh it right now), so you can quickly see the latest activity. Additionally, the feed also shows recommended users (based on your tastes) that you might want to subscribe to. We think both of these aspects of the feed will greatly improve the devRant content discovery experience.

This new feature leads directly into this next announcement. Tim (@trogus) and I just launched a public SaaS API service that powers the features above (and can power many more use-cases across recommendations and activity feeds, with more to come). The service is called Pipeless (https://pipeless.io) and it is currently live (beta), and we encourage everyone to check it out. All feedback is greatly appreciated. It is called Pipeless because it removes the need to create complicated pipelines to power features/algorithms, by instead utilizing the flexibility of graph databases.

Pipeless was born out of the years of experience Tim and I have had working on devRant and from the desire we've seen from the community to have more insight into our technology. One of my favorite (and earliest) devRant memories is from around when we launched, and we instantly had many questions from the community about what tech stack we were using. That interest is what encouraged us to create the "about" page in the app that gives an overview of what technologies we use for devRant.

Since launch, the biggest technology powering devRant has always been our graph database. It's been fun discussing that technology with many of you. Now, we're excited to bring this technology to everyone in the form of a very simple REST API that you can use to quickly build projects that include real-time recommendations and activity feeds. Tim and I are really looking forward to hopefully seeing members of the community make really cool and unique things with the API.

Pipeless has a free plan where you get 75,000 API calls/month and 75,000 items stored. We think this is a solid amount of calls/storage to test out and even build cool projects/features with the API. Additionally, as a thanks for continued support, for devRant++ subscribers who were subscribed before this announcement was posted, we will give some bonus calls/data storage. If you'd like that special bonus, you can just let me know in the comments (as long as your devRant email is the same as Pipeless account email) or feel free to email me (david@hexicallabs.com).

Lastly, and also related, we think Pipeless is going to help us fulfill one of the biggest pieces of feedback we’ve heard from the community. Now, it is going to be our goal to open source the various components of devRant. Although there’s been a few reasons stated in the past for why we haven’t done that, one of the biggest reasons was always the highly proprietary and complicated nature of our backend storage systems. But now, with Pipeless, it will allow us to start moving data there, and then everyone has access to the same system/technology that is powering the devRant backend. The first step for this transition was building the new “subscribed” feed completely on top of Pipeless. We will be following up with more details about this open sourcing effort soon, and we’re very excited for it and we think the community will be too.

Anyway, thank you for reading this and we are really looking forward to everyone’s feedback and seeing what members of the community create with the service. If you’re looking for a very simple way to get started, we have a full sample dataset (1 click to import!) with a tutorial that Tim put together (https://docs.pipeless.io/docs/...) and a full dev portal/documentation (https://docs.pipeless.io).

Let us know if you have any questions and thanks everyone!
- David & Tim (@dfox & @trogus)

So, Facebook is acquiring Giphy. The amount of metadata they're about to get is fucking insane.

And since I refuse to personally use anything Facebook related... I won't be able to use the GIF integration of any messenger and many more products/services anymore, I guess...

Just fucking great. Fucking die, Facebook.

These guys are damn serious about fitness.

What do Laravel developers love to eat.

Look at this cable management at my work place.

😂😂😂😾the ways of the universe

Happy Thanksgiving! Thank you for waiting for this new release of avatar items! We have new pets, new computers, new eye wear, some fun shirts and a special treat for our #1 ranter @linuxxx. The required ++ pts for these are a little higher than normal to reward the dedicated people who have helped support and build this community over the last few years. Thank you all!

Better be good.

This is hilarious 😂😂

#InternetExplorer

Next will be j

True 🔒

Error...

That moment when you ask your friend if he/she has plugged it in and they say yes and your answer is ”send a picture” and they respond with this....

True story

Pro tip: If you are a junior, or senior but new at the company, don't start your conversations with:

"We're doing X wrong. At my previous company we did / at school I learned /in this book I read / according to this talk I watched, the right way to do X is ..."

Instead try:

"I'm curious why were doing X this way. I'm used to doing it differently."

I love flat-hierarchy teams, and people who think about flaws in procedures and proactively try to improve the tools we use are awesome, but the next kid walking up to me yelling we use git flow "wrong" will be smacked in the face with a keyboard.

If you come to me with curiosity and an open mind, I'll explain, and even return the favor by behaving the same way when I'm baffled by your seemingly retarded implementations.

Maybe we can learn from each other, maybe discover that "how I learned it" is sometimes good, sometimes bad.

But let's start with some social skills, not kicking off into every debate with a stretched leg and a red face.

Before an interview prepare a list of questions for them, they expect it!
My list to give inspiration:

Describe your company culture? - if the response is buzzword heavy, avoid.

What’s the oldest technology still in use? - all companies have legacy systems but some are worse than others

Describe your agile process? - a few companies I’ve interviewed with said they are agile but it’s actually kanban

Are developers involved with customers?- if they trust you to talk to customers you can infer trust to do your job ( I’m sure others will disagree)

Describe your development environment?- do they have such a thing as dev, test and prod?

These are the only ones I can remember but should give others a bit of inspiration I hope 😄

Conversation today...

Guy: "Hey I need a real quick script to pull some values out of an XML document...is that possible?"

Me: "Uh...yeah that's pretty simple if that's all it has to do."

Guy: "Ok excellent I'll send you some files and documentation."

Me: "Ok so is this like a one time use thing or do you need to parse multiple of these?"

Guy: "Actually it needs to run all the time, on this specific PC, watch directories for any files that are added, then generate a XLSX files of the values, and also log information to a database. Etc"

Me: "Oh that adds quite a bit of complexity from what you originally said. It's going to take more time."

Guy: "But you said it was easy."

Well fuck you...

Ran into a girl who I had a crush on in high school at a bar last week. Hanged out for a bit, but then I had to run catch the last train home.

Today I get a message from her that reads: "Hey, it was nice to meet you last week. Can I call you some time, there's something I want to tell you. 😉"

I think to myself -- sweet and say that I have no meetings today, call me whenever you can.

A couple of minutes later she calls me, and the first thing she says: "I have this app idea..."

fuck, shouldn't have hyped myself up.

This was my first freelancer project. Just dropped out of school, i think i was 17. No money, no proper hardware, i had a very old laptop & stolen wifi from our neighbor. I lived in a very small room at my mom’s flat, she wanted me out as soon as i turn 18. At the time my plan was to work on freelancer stuff and make my own games. “It will be fine, fuck school, who needs school? 😂“ I haven’t really finished anything back then, so i only had a few wip hobby projects to show ppl as my references. I saw a freelancer job posting. The task was to make a simple quiz game for mobile, it paid 350$. Back then that was a lot of money for me so i took it. I met the client, he said “2-3 week tops, i send you everything, you do the code” Cool. I finally had a “job”😃. The 2-3 weeks turned into a 8 month blur of all-nighting and just implement one more thing and its finished. I did not really have any experience on how to deal with clients and i really needed this project to finally have something on my porfolio. I motivated myself with “if i can finish this i can finish anything”. I think the story of my most definitive all-nighting was 3 months into the development. I finally got everything from the client so it was like just put it together and its done. The client wanted 300 levels, beeing a noob i was i started making all the 300 unity scenes by hand, aligning the pictures, the ui, testing each level, making adjustments to the code, etc.. after a really long night and a fuckton of caffeine i was done. I sent it to the client at around 9 am and gone to sleep. When i woke up i checked my emails to saw this: Cool! But can we do hints? (wich needed a fuckton of rework of my code) I think i had my first mental breakdown while working on the project. After that he wanted more modifications and because i made every level by hand i had to remake all of them like 10 times 😂
But in the end it turned out positive, he really helped me to start my carrier, we became sord of friends and the project gave me a lot of confidence and experience on how to deal with stuff when shit goes wrong because everything that can go wrong in a project gone wrong. It was the most valuable developer lesson. Plus it sounds so cool to say “i was born in development hell, b*tch!”🕶
I attached a pic of the laptop i worked on 😂
Thanks for reading 😃

Hehehe

Just gonna leave it here

Js developer will understand

My #wk143

I like to fold origami mostly following instructions from youtube-videos. It really helps to calm down and relax and it's a great feeling being able to fold figures without instructions after a couple of times.

Here's the little Yoda I've made as a christmas present

When you don't compile small code snippet and keeps on writing lines of codes and after writing large lines of code that one moment when you start compiling your code for the first time

Brace yourself for errors 😕

In a long queue of people always want to apply LIFO approach but ended up using FIFO approach 😔

Old but Gold

Code never lies, comments do

Where did not to save cookies for this site information store

In cookies? 🙄

If life gives you key, hash it without collision 😀