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.

Doing some Christmas shopping.

Creating some throwaway accounts in various e-shops

Some e-shops send me my password via email upon registration.

I've spent the better half of a day emailing those e-shops to revise their IT security policies.

Haven't bought a single gift yet.

Time well spent!

A few months ago: "please lock down the app so clients can't upload new images once an order is in progress"

This morning: "why can't the client attach more images when they ask to revise an order?"

I've talked in past rants about how marketing loves showing off features to customers that are still in Beta to give us devs more pressure to finish them earlier, but it really just ends up screwing up our schedule since we have to push back on other features.

We had warned them not to do so for a series of reasons. But this time, this time their bad practices has come back to bite them in their butts.

They've been bragging all over to customers about this API integration we've been developing. They caught a reasonable amount of customers whose main reason for hopping in with us was this API integration. We finished the code on time, and submitted to the API provider for them to revise our "app". It's been a long back-and-forth conversation clarifying purposes and trying to fix tiny details and, of course, the providers' emails take almost a week to come back. We're waayy past the deadline marketing had promised customers, and they know they can't really blame the devs.

Sucks to lose these customers, but it feels so good to show these marketing pricks a lesson.

// 2011-05-13 - no idea why we're doing this, revise later

Wow thanks, take your time.

PM wrote a really high-level requirement doc and asked me about estimates.

Me: Well, functionality-wise it will take 4-5 days provided the design is ready.

PM: Our designers are really full on schedule; Just do it! Expand your creativity. I believe in your taste of UX

Me: Listen, the implemented design will take much more time to change if we go back and forth. It's better to revise on the designer's screen.

PM: Oh don't be so modest! I trust you already. Just focus on the functionality, get it done first. For the design we'll talk about it later. Move fast and break things!

Me: ..Sigh. This is gonna end up badly.

My hardware professor from first year at uni

He wasn't the best lecturer (which he openly admitted), but he was always willing to go an extra 10 miles to help you out, including essentially writing up the entire module into a nice document (70 pages long!) so we'd have good notes to revise from

Okay. I don't get quiet the idea why Project Manager doesn't want to enhance or revise the current format to proper format clinical prescription. I deeply understand that we have lots of bug fixes and enhancements to do. But, you know, one suggestion of a client can make a difference literally, compared to the previous one and can benefit to all.

For me I was so amazed by the fact I could control computers it was pretty much a morning til night thing every day for a month (which happened to be my study leave for exams I didn't want to revise for but hey! I landed a job in dev so
¯\_(ツ)_/¯ )

Gotta revise MySQL and Java for my IT Matura exam on Wednesday...

Reading/writing from/to files in a Java 8 manner,
LOAD DATA (LOCAL) INFILE "blah.csv" LINES TERMINATED BY "\r\n" DELIMITED BY ";' etc.,
Java Comparator,
clean Eclipse install...

No Internet, I'll have javadoc and mycli though.

Today I was forced to write spaghetti code.

When your database structure isn't set up properly, that happens...

I'm already sure I will need to revisit this piece of literal shit when we revise that structure. Though, it'll be much easier and logical, and I'll probably be able to just delete a big part of the code and implement it as intended.

My Data Communication & Computer Networks (DCCN) teacher was the best teacher I've seen.

Teaching can be super hard. You're one against like sixty others who aren't interested in being there. To make that good learning environment, making the subject interesting etc, it not easy. Some justify that, "I can only bring the horse to the water" & proceed to just regurgitate whatever is on the book. Others cross question you & impose punishments - try to make you learn by fear.

But my DCCN teacher - she had the right balance between strictness & humour. So kids took her seriously (did homework, weren't late), yet never feared her - we felt comfortable asking doubts/questions.

She had some good tactics, like asking us to teach certian chapters - that made us learn better. She would revise them in the end also, incase we missed anything.

My best moment with her was when I scored the highest in my internals. She picked up my paper & showed the class - "see? Just two pages & he scored so much". There's was always those students who pump out a lot of stories/essays or whatever that comes to their mind about the topic in question. Lots of teachers just blindly give marks - "oh, s/he wrote this much, so it must be right".

But my DCCN teacher had zero tolerance for garbage. If you're wrong, you're wrong. Some even believe that the number of marks = number of lines you have to write!! Doesn't matter what you write. So, I was super glad when this teacher upped the standards.

I have a ton of nostalgia for ROBLOX, but everything seems to get broken over time. As ROBLOX updates, something changes about the way the code works. Enough to the point where things that usually work stop working. I mean, look at literally all of the old gear; Many of them are completely broken. I've seen many old, fun games completely die because the devs stopped fixing the problems the ROBLOX devs were causing by constantly revising the engine. I'm afraid to make something too big and complicated because then it'll eventually stop working, and it will be a nightmare to figure out what I need to revise.

so which company is the new faang among developers? you know, the one where there is a good WLB, nice pay , 5-7 hr work/day and other benefits , but with a high entry barrier?

I am thinking of starting to revise DS/Algo for some interview prep

Codecademy is a great resource for beginners!

My final exams are going on and I'm cramming textbooks all day. It's currently midnight and I still have another 50 pages of reading to do. Plus revise everything before the exam tomorrow morning. I'm exhausted! And this is going to continue through Christmas and New Years Day! What the fuck is my University thinking!?
Anyway, I have to go back to finishing this chapter. Just came here to let off some steam. Thanks devRant for seeing me through this.

Web API: "Oh, I see that you're trying to update to our new design with a category and sub-category dropdown layout. Here's one api endpoint that provides you the whole table without fucking input parameters to filter per category and sub-category. Goodluck! And Have fun filtering through the json and sub-json response!

And btw, don't even bother asking me to update the endpoint. Cause admin already said that the UI SHOULD ADJUST TO THE API AND NOT THE OTHER WAY AROUND. AS THE APIs ARE HARDER TO REVISE"

It's not our fault your api design is crap. You piece of shits.

Every freaking time I think I've fixed my bug and can continue, I see a secondary bug showing up making me revise the code that I previously fixed..

At least I keep myself busy I guess.

!rant felt like a zombie all of last week and today, damn this brain fog. All I want to do is sleep lol. Had to revise my code countless times

!rant
Any thoughts on what i should revise for a first time interview as a Android dev for a ticket selling company :/

In need of a job where I can make the kind of money I want, I applied to xteam (I'm not based in the US which makes a big obstacle to getting a job there) and no reply. I applied to G2I and they said they only want full time (So I guess my profile is good). So, I'm hoping to finish my current project quickly to apply again.
@xteam, you really should revise your hiring process, it's really disheartening to not receive any feedback from a platform that says it focuses on community.

Every time I find something to revise on stackoverflow