I fucking hate installing shit on Ubuntu via APT when it's not provided by Ubuntu itself. ONE HUNDRED PERCENT OF TIME this will create problems with outdated keys or whatever. Then, to solve the problems of software that was supposed to be transparent, I have to go learn about layers upon layers of its inner workings and waste my fucking time. I suppose this is the Linux experience in general. But I don't want to know about GPG whatever whatever because there's no need for me to learn it outside of solving this stupid-ass fucking problem. I don't want to learn that sources.list.d is a fucking directory. I never EVER want to touch any kind of keys or whatever shit, I just want to follow some instructions and fucking install software in a simple way. curl whatever | sh it is, I don't fucking care.

All I want is to develop software, not dive into problems with my operating system because it decided to shit the bed.

If you just git add . by instinct, you're already dead inside

Instead, consider checking out the diffs of your changes before staging them, and then stage the files or directories individually

Of course I'm saying this to complain about my colleagues who stage and commit things they shouldn't, it probably doesn't apply to small side projects, but staging individually is probably a good habit to have

Nobody reviews my PR into test branch

The only guy who reviews it is the new senior dev who isn't yet used to how the company works, leaves comments about useless stuff and doesn't fucking approve

Jesus fucking Christ

Hooooly SHIT, is Redux ever so extremely complicated.

Got a simple task

Decided to refactor some related shit so I don't have duplicated code

Get loads of problems with the shit I'm trying to refactor, now I'm late with the simple task

Yes, yes, keep asking detailed "how are we going" pressure questions to me, surely that will improve my performance and not make me lose focus!

>new feature in application uses external API
>external API has unreliable response times, requires polling to get results, no way to set up webhooks or whatever
>tech lead proposes asynchronous system which will queue up user requests for processing and use websockets to warn frontend clients of finished query results
>higher ups say it will take too much time, make tech lead cut back in scale and treat external API like a regular synchronous REST API
>team dutifully implements feature within the constraints of the new smaller scope
>higher ups try out the feature, find the usage experience is extremely shitty, but don't back down, they only let tech lead scale back to original scope in small increments that still allow new problems to show up
>feature takes up same time or longer, but with more damage to the mental health of developers

At least I'm not in that team

Ranted about this before, but...

>have likely ADHD
>poor performance
>can't get raise because of poor performance
>can't afford treatment because low salary

It sucks.

Stop scrolling.

Turn your keyboard upside down, and shake it vigorously for a minute.

Now carry on.

Been put on debug duty, shit fucking SUCKS ASS.

Demotivating as hell seeing other people implementing cool features while you're doing this stupid shit trying to reproduce bugs that appear in production. Fucking hell.

I'm always a bit lost at sprint planning, and the tasks are not written very descriptively in Jira, in a way that doesn't help me "restore the context" of what needs to be implemented. I'm always kinda lost in this shit and now I gotta go embarrass myself and ask people what were we supposed to do again, after a couple hours wondering and distracting myself as a "coping mechanism" for my frustration with this.

I hate being this anxious. My tasks are late and I don't want to keep working into the night this year.

"You don't need to put a type annotation here, the type will be inferred by the compiler"

"We don't need to mark this function as async, since we are already returning a promise but not awaiting it yet within this method"

TypeScript codebase. Am I wrong to prefer that things be explicit rather than implicit? Sounds a bit tryhard to try and make things implicit, but maybe the async really changes behavior in the second case? I don't think so, and I prefer to mark an asynchronous operation as such, but I'm still doubtful; that's why I humbly ask you all what makes more sense here.

I no longer give a single flying fuck about whether this company I work for lives or dies, whether it succeeds or fails. My compensation has been piss poor compared to the level of dedication I have put in and the level of stress I've endured. Up until now, I was thinking like "well, it's a growing startup, maybe if it succeeds it can have some doors open for me". But fuck it.

I keep hearing about software developers doing pretty well for themselves, but I can barely pay my fucking bills with this shit company in this shit country.

I should've started doing this sooner, and I'm a stupid-ass motherfucker for not having been doing it, but I'll be looking for jobs with actual respectable pay now. I'm not bound by a notice time in my contract, so maybe I'll be telling whatever other companies that I can start with them immediately if they need me to.

Seriously fuck this company and its low-ass compensation. If I'm going to be paid this low, I might as well take a less stressful job with less skill requirements.

I will be jumping ship and I won't be caring one bit if it fucking sinks.

Sprint retrospective rescheduled, which means I can do actual work.

(Which I should have finished by now, but alas)

Amazing how leaders keep rescheduling 101's, but will find the time to do them as soon as they have negative feedback to share

Some marketing people function on a whole 'nother level. They write internally in the same way they write to represent the company externally, using all the bullshit-laden buzzwords, using exclamation marks all over to convey fake enthusiasm. I wonder if they feel exhausted after doing this for a whole day. I know I would. But I suppose if it helps them perform better, well, let them do it, I guess.

If your application uses OpenAI APIs, should your prompts go into version control? I reckon *some* kind of version for control for OpenAI prompts and configuration should be used as you improve and fine-tune them.

Fuck Medium.

I just recalled I once had to explain to my CTO what’s the difference between stack and heap memory

It baffled me a little bit, but contrary to what one might perhaps expect, this was a guy who was already making a living off of programming for about ten years selling his software to various clients, so he was clearly competent enough to create software that works, and he had in fact put this startup on its feet operationally with it already being profitable before outside investments were secured

And here I was with my theoretical CS knowledge making zero bucks before getting this job

I fucking hate TypeScript

If you're part of the TypeScript cult, go fuck yourself too

Low performance because of shitty attention span and high procrastination
Don't get higher salary because low performance
With low salary I can't go to a professional to get a medication prescription and couldn't afford medication anyway

I just wanted to have a life and live it, be able to afford to go on dates or just do things, afford a car so I can go anywhere, I had this little online romance where I couldn't afford to go see the girl, she ended up just ghosting me and it fucking destroyed me

To get this low-paying job, I was forced to open a company to work as a contractor in order to circumvent labor laws (common practice in my country, encouraged by shitty labor laws and unstable local currency); I end up having to pay to get paid

To top it all, the government just wants more and more taxes and my pay is worth less and less

My mom wasted all her money and now needs my help

I should just find a way to kill myself

There will be a "great place to work" poll at my job... I wonder if I can be honest in it.

People who do remote work, what's your stance on making calls to get together to do things?

In my case, I have this tech lead boss now who's always available to start calls so I can share my screen and point at what problems I'm having, and I really appreciate that.

Other people at my job are really hard to get into contact with, they're never available when you need them, so if there's some conversation by the nature of which there needs to be a lot of back and forth exchange to get both parties on the same page, more than a day or more can be spent before work based on that conversation can be done.

I'm not talking about distribution of tasks, but rather "person with access to X, I need you to do Y". I invite them to have a call so we can explore how to do Y together, because neither of us know it too well, but they just do whatever, ask how it went, and it turns out wrong. In this particular case, I've got a marketing guy who has access to the company's business account in a social media platform. I need them to add me there as a developer, and make sure I and another developer have all privileges necessary to create and configure an application which will use the social media platform's APIs. Marketing guy just takes hours to respond and generally acts like we're not worth his time, but can't do the things we asked and dedicate the time to see with us if things are working before he sets out to do other work.

This isn't an isolated case, we've got other people who don't look at their messages and are just generally unavailable. Not sure if I have incorrect expectations. Everyone in the company works remote, but we're all in the same time zone.

I like my current job, but the pay is fucking garbage :(

I HATE automated messages on Slack

Remove fucking GitHub updates, Jira updates, all this stupid bullshit that pollutes actual communication between humans in all that fucking shit and makes me miss actual messages because I ignored a channel where that garbage cancer shit was set up on?

What's wrong with going to fucking Jira and GitHub and checking how things are going THERE?

I had a branch <refactor> where I changed the structure of some folders (and did appropriate changes in imports) for organization of the feature I'm developing; I then merged <refactor> into <feature> and created a PR from <feature> into develop. I let the PR be known in Slack.

Yet nobody reviewed the PR.

Whatever. I created <new-feature> from <feature> locally, and started working on it. Then I merged <new-feature> into <feature>, and pushed it into its remote counterpart... well, only now have I realized I haven't merged the remote <feature> into develop. Now I have a PR in which the documentation doesn't tell all the changes anymore. Because nobody reviewed it before and I couldn't merge it. Now instead of keeping on working I gotta come here to vent my frustration before I can do anything.

Got a guy trying to convince bosses of enforcing ESlint rules or whatever

This is the same guy that came into our repository forcing this shit on every single file he touched, when we had a different, established style

I shouldn't have let his new style enforced by ESlint defaults pass the first time in code review

Like, WHY the fuck do you want to be the enforcer of styles when you started shitting on what was there in the first place

Jesus fucking Christ

Purpose of Slack: communications (I suppose)

What management uses way too many channels for: updates of ANYTHING anyone does on Jira or any pull requests created on GitHub

What would be useful to get notifications of, such as PR comments, isn't there

I'd like to get notifications of when *people* talk to me, as I like to answer them promptly, but these stupid automated updates on Slack just makes me mute whatever channels they're setup in

Imma be honest with you, chief

Sequelize's associations confuse the heck out of me

Like I understand what one-to-one, one-to-many, many-to-many relationships in a database are, and I know how I can implement them with just SQL, but the whole thing with belongsTo, hasOne, hasMany, belongsToMany just fly over my head completely

Unless you're editing actual fucking JSON and not a JS object, do this:
{
name: 'John Doe',
phone_number: '12345',
}

Not this:
{
name: 'John Doe',
phone_number: '12345'
}

Note the presence or lack of a comma after the last field. In this way, when you add a new field, you only have one line change in version control, because otherwise you'd have to add that no-longer-last comma and thus make two line changes. Not to mention you can forget to add it and spend some time figuring out what is wrong.