I wrote an algorithm that incorporates a 3rd party API. and the algorithm is so fast and optimized that I started to get 429 status codes from the third party API, asking me to slow down my requests, which I didn't think was an issue when I tested on local env.

Now I'm on purpose slowing down my code, to prevent that from happening.

Talk about suffering from success.

Asked for Git repo details and my manager replied, “Let’s discuss and close this in the office tomorrow.” I guess Git and patience both require good branching strategies! 🤦‍♂️

so, I am trying to implement a caching solution for my CI/CD (because, you know, BitBucket CI caching sucks ass big time). This time I was writing a module in Python. I spent 2 evenings in the evening building it, debugging and testing, implementing several features making it a flexible solution.

So, yesterday I had a pretty much well working version. Before pushing changes I wanted to drop the cache and give it another round of testing, just to be sure I was pushing a truly working code. I rm-rf the cache directory, restart the engine and I'm greeted with an error message saying the module I was working on cannot be found.

wtf..?

Out of a sudden the IDE stopped showing all the project files as well.

wtf happened....?

oh, of course.. I rm-rf'ed my project directory, not the cache directory. Deleting EVERYTHING I had.

fuck.

I should not be working half-asleep

I give up. It‘s impossible to argue with Apple.

I tried to bring my unofficial iOS devRant app "JoyRant" into the AppStore. It was available via TestFlight for years and it wasn‘t a problem there, apparently. Now for the AppStore, it is a problem.

I talked with the Apple review team for 3 weeks and the discussion went in circles.
They said that my app tries to disguise as or to misrepresent another app on the store (the official devRant app, even though it‘s not available anymore, apparently).

I was asked to remove all of the mentions of devRant from any description or any place in the app. I did. Even though it was stupid because how are people supposed to know that they need a devRant account to use my app? I‘m not allowed to mention devRant.

After that, they said that it can not have the name JoyRant because it sounds too similar to devRant.
I changed it to devJoy everywhere, the app, the meta data for the app store, the github page where the required legal crap is hosted, and in the legal documents themselves.
Did it help? No, it didn‘t.

Apple then proceeded to claim that my app is trying to deceive the users into thinking that this is the official devRant app. Even though I have explicitly stated in the description that it is just an unofficial devRant client.

Now apple says that I should "revise the app content".
Which I assume means that I need to make it something different. Yeah. Great suggestion!

So, I will rename the app back to JoyRant and provide it via TestFlight, as it was before.

Thanks for reading. I needed to vent.

So I thought of applying for masters, mainly coz work's been boring af -_- i'm not having Fun. like. at all.

Masters in CS would need a research topic and the one I was/am interested in is "WebRTC", with the topic being tryyyying to figure out a way to hide the actual Peer IPs and come up with a Standard 2.0 of WebRTC or a derivative standard

I was looking into Research Papers already written on WebRTC to get a feel on what's already been attempted or tried
And omfg the word-vomit :v

The whole paper had 0 substance and their "research" was that "we'll encrypt Packets with SHA256 so it'll be secure" like bruh -_-

Some years ago i was getting some dev training at a medical analysis company. They made a performance report at the end. And well, they sent out the report to my employer before actually discussing it with me. Which would be ok if it wasnt horseshit and full of blatant lies. Apparantly they confused me with someone else. Atleast it got corrected in the end.

Some weeks ago i heard they were heavily sued by swissmedic. An org supervising all medical products within Switzerland capable of shutting down entire companies and hospitals for medical malpractice. Apparantly they fucked up programming a cleaning cycle when running a series of samples trough their machine. Hospitals reported this issue but they ignored it. I guess they had it coming.

I’m currently working as a frontend developer at my company, and our designer was let go about a month ago (the second designer to be fired within six months). Today, my non-technical CEO asked me to “give some love” to our internal admin application, which was primarily developed by my backend colleagues.

My CEO doesn’t want to provide a list of requirements. He said I should use my “common sense” and joked that without it, I could be easily replaced by ChatGPT.

I know what he wants, but the joke about ChatGPT bothered me a bit.

I’d like to know your opinions on this type of conversation.

Thoughts on the idea of including links/query starters for debugging or where the fucking logs are in AWS, grafana etc in repository READMEs?

I currently have a design meeting with the CEO. He joined the meeting on his iPhone mini and the designs are for a desktop app.

What a joke

has anyone developed a math formula for GitHub repositories using the stars, the issues open and the amount of PRs to judge how strong the project is?

I've had today a meeting with the CEO regarding some designs. Here have some quotes that he made:

1. So you can click, click, click, click, click
2. numbers are so complicated so I just said something
3. I like the vibe in Amsterdam
4. We are doing a rebranding. Our rebranding document is the color of the 2 blues and one orange
5. I've to ask my wife for the design (with no design experience) to make the rebranding documents
6. In <the app our technicians/support use>, you can brrrrrrrrrrrrrrrrrrrrrrrrrrrrrrb
7. This is what differeniate us between most applications; FAVORITE SQUARES
8. I never watch that mess. I don't even know if it works or have ever worked with it. (talking about a simple table view)
9. You have been reported to the admins (in an admin-only application for our customers)
10. It's always nice to see developers think; when I don't think
11. But it's already an iPhone (when looking at android designs & cries in largest userbase in my country)

i am an unskilled pussy without strong opinions

sometimes you get conflicting feedback on code reviews from seniors

i'll do whatever you guys want (haven't encountered anything egregious enough that I do have a strong opinion on yet), but y'all may need to sort out how you want me to slice this cat

in your opinion, what is the most important feature of a programming language? For me it’s getting paid for using it.

team lead/senior telling you that you're probably going to break prod and have to patch it for the next couple of weeks when working on one of the first migration epics on legacy monolith, but we'll get good data from it doesn't make it any less terrifying

Do you think I can tell my coworker to stop deploying shit so early in the morning? It makes me look lazy

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

There’s something I gotta tell ya.
I posted this a while ago. This Friday, they removed a tumor from my lower lip. I never had tumors before, let alone on my face.
I’ll know if it was malignant or not next Friday.

Microsoft has the audacity to put "Get the new Outlook (It's free for Windows Users!)" on my lock screen. Extraordinarily annoying because:

- It's just the web app packaged in the SHITTIEST electron wrapper you ever did see.
- IT FUCKING HAS ADS

A service had/has been logging hundreds of errors in the development environment and I reached out to the owning process mgr that the error was occurring and perhaps a good opportunity to log additional data to help troubleshoot the issue if the problem ever made its way to production. He responded saying the error was related to a new feature they weren't going to implement in the backing dev database (TL;DR), and they know it works in production (my spidey sense goes off).
They deployed the changes to production this morning and immediately starting throwing errors (same error I sent)
Mgr messaged me a little while ago "Did you make any changes to the documentation service? We're getting this error .."

50% sure someone misspelled something in a config, but only thing they are logging is 'Unable to parse document'. Nothing that indicates an issue with the service they're using.

Company wants me to give a rough estimate of developing a new feature in a distributed legacy monolit. They told me they would inform me the next day and want the estimate on the same day for a project that will probably take 2 devs 3-4 months. I ask for more time and info, give the estimate and they say it "feels too much". I mean ok. Then why am I even estimating? If in the first place the client has only X money than do the project for X and it doesn't really matter how much work it is, does it?

More companies need to clamp down on hard-coding secrets. It’s not difficult to store them somewhere else, and there’s swathes of free tooling to stop you doing it in the first place.

Heck, set up a pre-commit hook. Link it to a shock collar.

If I had a nickel every time the unit tests failed not because something was wrong in the code, but because someone had messed up the unit test I'd be able to retire early.

I just spent the better part of 10 hours hunting down a bug in some production code only for the test to be wrong because the person who wrote it had mocked the http response incorrectly.

Nothing I did to "fix" the code worked, because nothing was wrong with it...

Took some time off with the Mrs for our crotch goblin's first birthday and it was wonderful. I properly switched off for the first time since he was born, barely touched a keyboard, went outside, slept. I felt great.
But Jesus H Christ trying to get my mind back into work mode is a slow and difficult process. More coffee please.

Cat of the day (mine, banana for scale)

Stop glorifying overwork and start prioritizing our well-being. After all, life's too short to spend it all at the office 🌟🏡

Don't bug your backend engineers please ... just give us what we really want!

User: "I emailed my spreadsheet to a colleague. Why can't I see their updates in mine?"

Please just kill me now.

RTFM

Currently working on a game for developers.
Two players compete on a randomly generated arena by sending instructions via a REST API such as "unit x move in the up direction and shoot to the right". So units can be controlled by manual user interaction but the idea is that the players create a smart program that controls the units automatically. So it’s about who can implement the best "bot".

The game is turn based and the units can move one grid cell per turn and shoot in one of the four directions. Shots require energy which regenerates a certain amount per turn.
Units can also look in a direction to spot enemy units which are not visible by default.
The winner is who manages to destroy all enemy units or the main stationary enemy unit "the gem" (diamond shape in the screenshot).
There are walls which block the movement, the line of sight and the shots (green cells).

Everything is randomized. The size of the arena, the number of units, max hp, max energy, etc. But it can be replayed by providing a seed.

There will be a website which lists all games, so that players can watch them.
Alternatively a player can also implement an own viewer. Everything necessary is provided by the REST API.

I’m curious about what you think 😄

Amigurumi cow, first attempt