I maintain some of the top 10 most downloaded packages in the Javascript ecosystem - in the order of hundreds of millions of downloads a week. I've worked with hundreds of repositories, thousands of OSS developers, across a few dozen teams (professionally). I've seen just about all of it, for almost 10 years now.

With all that being said, I'll leave it at this:

I hate every facet of the Javascript ecosystem.

✨ I created a cli tool that brings my GitHub feed right to my terminal.

It's just a fun idea that I had since I have this habit of checking my github feed every now and then. So made this tool to do it right from my working terminal.

The project is open-sourced in Github
https://github.com/RocktimSaikia/...

Here is a preview of my Python devRant client

The client supports both CLI and GUI modes.

This is the CLI mode using the rant command.

CLI mode currently supports dynamic importing of custom commands (and creating your own command is documented already too).

If you do not like my rant command? Download or make another one.

Also, the command execution, import, and registration process all send events to the application object. This is in preparation for allowing mods!

Unfortunately, emojis are technically 2-width, so they totally fuck up the box I draw around the rant. Lots of work to do, but I was pleased with my first visual payoff today.

There is a very handy shortcut for us, the people who use the terminal every day. It's [CTRL]+w. It erases a word on the left.

HOWEVER, it is quite annoying to be used to that shortcut when you are in a browser. Especially when you've been writing a well-thought-out letter for half an hour or so.

DAMN IT!

The level of fucking backflips I have to do to get these morons to learn git and not share code via fucking emails, Jesus Christ, you'd think I asked them to switch religions. Why the fuck does this profession not require a fucking license in this godforsaken country.

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)

Here's a real tip for people new to the industry.

It's one of those things that's been said over and over again but very few can really seem to employ. I suggest you learn it /well/.

You are not your code. Criticisms of your code, ideas, or your thought processes, is not a criticism of YOU. You absolutely cannot take criticisms of your work personally.

We are engineers. We strive to seek the best solution at all times.

If someone has found a problem with your code or with an idea or whatnot, it is coming from a place of "this is not the best solution", NOT "you're an idiot".

It's coming from a place of "I'm closing this PR because it is not a change I feel suits this project", NOT "I'm closing this PR because it's coming from a woman".

It's coming from a place of "This feature request is ridiculous/this bug is not actually a bug", NOT "you're a fucking idiot, fuck you".

It's coming from a place of "I've already had to address this in a number of issues before and it's eaten up a considerable amount of my time already", NOT "I don't even know you and this I don't have time for a nobody".

You do not get to be bitchy to maintainers because they denied your request. It's not a reflection of you at all. But if you're arguing with someone who has maintained a piece of code for almost a decade, and they're telling you something authoritative, believe them. They're probably smarter than you on this subject. They've probably thought about it more. They've probably seen their code used in many different places. They have more experience than you with that codebase in almost all cases.

Believe me, if we cared about who was behind all of the issues, pull requests, etc. we get, we'd get NOTHING done. Stop taking shit personally. It's a skill, not a defense mechanism. Nobody has the time to sugar coat every little thing.

Let's normalize directness and stop wasting time during technical discussions into opportunities for ego-stroking and circle-jerking and back-patting.

Reinvent the wheel, then throw it away.
Best way to understand a concept

Just rebooted my work station during a video conference because the VPN was flaking out.

After reboot, launch Teams to get back to the meeting. The VPN credentials dialog then pops up, but IS NOT MODAL, so I end up sending my password to the group chat...

Time to change my password, I guess.

Who would have thought that Ben Award's VSCode stories would be sold at 9000$. That's almost my entire college fees for 4 years.

Code quality is not related to your self-worth.

Imagine working with some pronouncing git as jit but you don’t care about correcting him so pain continues, endlessly.

Am I the only one who when they are super focused writing code and debugging starts acting like Bob Ross painting a picture?(without a filter... of course)

And here we’ll add another little god damn breakpoint so we can watch our fucked up variables report the wrong thing..

Oh and over here will just add another little happy simple if statement.

Oh look at the happy if statements in a row.. maybe we’ll add little switch statement here.

So today, i talked to my manager about my burnout and she offered the extra resources to help my project. And if nothing goes wrong, i’m going to take leave for 2 weeks by next week.

My advice, we are human and developer is special human. So, talked to your manager or boss about your problem, it’s their job to help you on this.

On last thing, i hope you guys pray for me and i hope i can be a better person once i comeback. 👌

I just finished reading the last chapter of the DevOps Handbook, its an eye opener, but not an easy read. And still recommended.

I've been reading this book for the past year and a half, little by little. It was hard since I started understanding why my work was so frustrating (I'm in System-Cloud-Ops position). The book made sense, while the work did not, it got harder since the book provides solutions, but whenever I dicussed any solutions with management they dismissed everything.
I started to initiate improvements by myself:
Prioritizing tasks I thought were more important to improve the way of work - do now and ask questions later... I got yelled at, I got my managers angry, but afterwards more often then not they admitted I was right.
To make it possible I worked overtime and on weekends, trying to prove a better way is possible, by implementing a long term solutions to solve problems instead of workarounds, automating a lot of stuff, creating labs, preparing presentations and documentation.
Time and time again I tried to pitch more ideas related to DevOps but the managers didn't care...
I know now my burnout started 8 months ago slowly, my hairline started receding, I started clenching my teeth (the doctor said stress was the cause) which was very fainful.
I continued to work but I noticed I was also more cynical, frustrated, and tired.

In the process I neglected myself.
So finally after 2 years and a half I quit my job, to focus on myself, at least for a little while.
I hope in my next job will be better.

Treat your servers like cattle, not as pets

Oh my god...

Arrived today, hyped!

I have real-world experience with MongoDB, MySQL, Firebase, and caching with Redis.

A colleague in ops recommended this book a while back and I thought I'd give it a whirl to better understand what other options I have available.

When a company emails 8000 + employees asking 3 people not to be disturbed in DevOps for 3 weeks. You know those 3 people have been screwed over by unrealistic deadlines.

Devops though

DevOps is like development, except there is zero test coverage, everything is a race condition, and there are a million variables declared as global. 😡

Me trying to optimize my overloaded stack

On my twitter feed today.

Too true, too true...

The Fibonacci sequence also known as he fingerprint of God is the most efficient memory maintenance method in computing as well
#weirdcode

Software development lifecycle? Not Agile. Not even Waterfall. Here, it's Adhoc.

Commits are not objects of love, and should not be judged by their size.

Ughhh... I know how to, cant be fit.

So it's 11:32,
I can't wait to go to bed, finished development for the day but then my boss sez can you make a sketch up of how the building plans for the app would look?
Me:🙂

Have an 'anger' project open to the side, so when you get annoyed or tired of the paid work, take a quick break and jump into that project to clear your head, even if it is just a simple command line tool, done it before and it's quite a good thing from experience