Here's a recent interview I had for an Android Developer job:
I: Interviewer, M: Me

I: hello, welcome
M: hi, thanks

I: do you know Kotlin?
M: yes, I've been working with it for 1.5 years and have written 3 projects in it

I: do you know RxJava, Dagger, Retrofit, and how to make Custom Views?
M: yes, I'm comfortable with them *explains*

I: do you know Room?
M: yes I do, I've done a lot of practices in it, but unfortunately have never needed to use it in production

I: what architecture do you use? Do you know MVP?
M: I'm currently using MVVM, but not MVP. I've debugged projects in it so I know what's going on in it

I: ok, do you have any questions for us?
M: how did I do?

I: I'm sorry sir, but you're not even a junior here
M: what? Why is that?

I: well you don't know Room and MVP?
M: I said I know them, just haven't used them in production.

I: well you have 3 years of experience but you dont even know Kotlin!
M: Kotlin was your first question and I said I have 3 projects in it. Did you even check the samples you asked for in the job posting?

I: SIR YOU'RE NOT A GOOD FIT FOR US, THANK YOU FOR COMING.

:/

We called it "Project Hindenburg".

A huge planning and logistics app with hundreds of screens and dozens of interwoven subfunctions, suddenly needed to be able to support multiple time zones. Our project was to retrofit every area that touched on dates or times, to allow the user to specify, and work in, any time zone.

At this point in the story I can tell whether you have had to work with time zones in code. People who haven't are butting in with something that begins, "that should be fairly simple, you just need to..." followed by some irrelevant noise that betrays their ignorance.

People who have worked with time zones are nodding in shared pain, like fellow attendees of a survivors meeting.

You see, programmers tend to think of time zones as arithmetic; in reality, they are confusing, ambiguous, chaotic, and individual. You can't translate everything into a central time zone (eg UTC) because you lose the user's intent. For example, if you schedule a meeting for 3pm and then move it to the next day, you want it at 3pm even if the clocks have changed.

Project Hindenburg ended up using the entire development staff of the company for well over a year. It smashed our release projections to rubble, made an already tangled code base completely unmaintainable, introduced mind-bending edge case bugs that reduced staff across the company to tears (literally), and led to most of the mid-level and senior developers eventually quitting (including me).

I am @fuckfuckityfuck, and that was the story of Project Hindenburg.

Interviewer : So what frameworks and library you usually use?
Me : i use volley for networking, gson for parsing, livedata/architecture components for architecture and observability , room for database and java for app development

I : ok so make this sample app using retrofit for networking, moshi for parsing, mvrx for architecture , rx for observability , sqldelight for db, dagger2 and kotlin for app dev. You have 8 hours

Me :(wtf?) But i never used those libs or language!
I : we just want to check how easily you adapt to different surroundings.

Me : -_-

Honestly i don't know of it was a great experience or a bad one . I was stressed the whole time but was able to adapt to almost all of those libraries and frameworks.
At the end i got selected but decided not to go for those ppl. That was just a lucrative opening of a venus fly trap, they would have stressed the hell out of me

Me, the only iOS dev at work one day, and colleague (who we'll call AndroidBoy), the only Android dev at work that same day (he's been working with us for less than two months). There was a change in one of the jsons we received from the server: instead of receiving a list, we now received a dictionary with strings as keys and lists as values. My iOS colleague had already made this modification on our parse function the day before.

AndroidBoy: "Hey what happened with the json?"
Me: "Oh, well instead of parsing a list, we'll parse a dictionary and get the list from each key. You basically have to do the same thing, only this time the lists are organized into categories."
AndroidBoy: "Oh, ok. But I don't know how to parse a dictionary while using Retrofit." (Context: Retrofit is a framework for request handling - correct me if I am mistaken, that's just what I've been told)
Me: "Sucks, dude, can't help ya. I've never worked with that and don't have that much exp. with Android."

I go out for a cigarette break. When I return, AndroidBoy is nowhere to be seen and suddenly I can't seem to get that data in my app. AndroidBoy comes in from the room where the backend colleagues work.

AndroidBoy: "Solved it!"
Me: "Solved what?"
AndroidBoy: "I told them to change back to a list and just put the key inside the objects of the list."

... he used the precious time of the backend colleagues to change the thing back hust because he was too lazy to search how to parse a dictionary. I was so amazed by his answer, that I didn't know whether to laugh, scream at him or punch him in the face. Not to mention the fact that now I had to revert just so he could avoid that extra work.

Girlfriend wants to start a fight almost ending the relationship while I have to finish an app in 2 days and the Volley library is starting to get too complicated (should've learned Retrofit instead).

I'm doing the project alone because half of my group literally quit the course to study Advertising and Marketing in the middle of the project.

This is going to be one of those weeks...

Today I was told I can't use the word retrofit in a sentence because I have to 'use words a nice year old would understand'

There's being an effective communicator and then there's becoming a soulless, creativity killing nazi

API response.
For a week been working with my project manager remotely.
Then yester night had a tough one.
Me:Please send me the API endpoint so that can test it and see the response.
Him:On my side all is set just consume the response.
Me:As a practice I did first test the API using postman and the response was okay.
Me:As I had already prepared my Retrofit code to consume and parse the response I head to it.
Me:Fast forward 20 minutes into the application I realise getting some unexpected errors thanks to the guy who didn't follow my response format.
Me:I call him asking him to check how he formatted the response .
Him:He claims he formatted it as requested .
Me: Double check my work and am damn right and now raise my voice as I talk to him again and requests him to send me a screenshot of his response and I send mine.
From the screenshots turns out his response is okay as he is working from a damn localhost and my response was coming from the live server.
Feel like strangling him for wasting my previous 30 minutes

Boss: convinced the client to rewrite his ancient procedural PHP prototype to .NET MVC.
Next day:
Boss: Actually he decided to just retrofit it... again.

PLEASE RETROFIT THIS ISSUE TO THE BRANCH NOW! THIS NEEDS TO BE IN TODAY! NO EXCUSES!

Uhh, that would be ok if it weren't 40 commits over several JIRA issues in over 12 different modules... or if you had given me more than half a day to accomplish this task. But no. So here were are, at work at 7:30 pm spinning builds. Missing date night with my S.O.

And now the build is red.

Kill me.

The monotony of begging management for budget to retrofit unit tests which should have been there in the first place is starting to piss me off.

We've been working on a big application on-and-off for the last year (whenever we had time.) It was 99% working, and we left it to work on some other apps. We come back to it, only to find that some big features have magically stopped working. We dig into it and find thT some other dev team completely changed the functionality of one of the existing off-application microservices were utilizing without telling us, and then we had to spend days reverse-engineering what they did so we could retrofit our application to communicate with the microservice again.

We were able to get it fixed, but I just know that they're going to change something else in the future without telling us and it's gonna break again. A little interdepartmental communication would be greeeeaaaat!

Why is angular universal such an arse to retrofit?

> 2018
> yay, let's write some android code
> oh look, socialRepository.getMember(memberId);
> let's see what this method does
> ctrl + click
> goes to an interface ಠ_ಠ
> find the implementation
> oh look, apiClient.getMember(memberId);
> let's see what this method does.
> ctrl + click
> goes to an interface ಠ_ಠ ಠ_ಠ
> find the implementation
> oh look, apiService.getMember(memberId);
> ctrl + click
> goes to an interface ಠ_ಠ ಠ_ಠ ಠ_ಠ

At least the last interface was the implementation of the api service with Retrofit.

for android mobile dev
do we really need to learn retrofit?i know that is part of RestApi, but retrofit is really hard to learn and less tutorial about it,maybe if anyone good information its really helpfull for begginer like me,thanks.

Question regarding android. I am having a problem with retrofit (I am using moshi converter factory) and hope that you can help.

Basically I have a screen with 3 checkboxes. User is able to select any of these checkboxes, and also user is allowed to select none of them.

When user doesn't select any checkboxes and click complete button, I send a PATCH request to backend with a model which contains 3 null values.

Problem here is that PATCH request which is being sent doesn't include any properties which have been nulled.

I spent some time researching why retrofit/moshi doesn't serialize nulled properties and I found a fix.

So I have this line

.addConverterFactory(MoshiConverterFactory.create(moshi))

Which I replaced with

.addConverterFactory(MoshiConverterFactory.create(moshi).withNullSerialization())

Now nulls are serialized and I am able to send a PATCH request model with nulled values. However now I'm facing another problem. Across my app I'm using only one retrofit client and I don't want to serialize nulls for all requests. Also I don't want to create another retrofit client.

How can I fix this problem? As far as I've researched it seems that I need to add an adapter with toJson() and fromJson() methods and then somehow enable nullSerialization only for that adapter. However I don't completely understand that solution and not even sure how to handle it.

Retrofit + Gson is faster than Volley + my static helper class for parsing JSONArrays -.-

I feel defeated //android

I need a library for use rest service in cpp. Like retrofit or volleybin android.
Someone help me

Darth voor the hedgehog
Favorite drink: Red Bull sugar free
Favorite color: black
Tried to marry Cocteau twins lead singer
Carries an m14
When picked, can instantly retrofit your tv with a subwoofer that is really a guitar amp

Irony - (noun) Switching to a new framework to do more with less code. Spending obscene amount of time and LOC to retrofit rest of the code to work with the said framework.

hey guys i need your advice about backend integration for android. I have this junior and I want to teach him about integrating REST API and handling it with volley+caroutines or retrofit+rxjava. currently the junior is using firebase for authentication and firebase realtime db for all CRUD operations. problem is that by using firebase backend the junior won't learn networking/multithreading stuff. Is there a way to use firebase realtime database like a REST API?

some help in butternkife and retrofit for Android apps

Hey android devs ! Just learned MVP architecture and some libs ( Dagger2, rxjava, retrofit) now can anyone explain why do i need 'testing' and how does it benefit and what should i know about it ?