Details
-
AboutLead mobile app developer and architect
-
SkillsReact native, JavaScript, swift, flutter, iOS, android, c++
Joined devRant on 2/10/2021
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Why do I get the urge to do 3-4 side projects just when I don't have time for neither of them and when I had time to do them I was just doing nothing all day...4
-
My Senior Just asked me not to copy from stack exchange and his wife (Also my senior) suggested to copy from stack exchange to reduce work load. Wtf I am supposed to do🥲16
-
So today , a company phoned me for a job I applied in Jobstreet. So the conversation goes like this.
Com " Do you have any experience in Android studio? "
Me : " Yes . I develop android application, it is compulsory to know actually."
Com :" ok... Do you have experience android SDK?"
Me : " I believe you are referring to the Android studio, yes."
Com :" do you have experience in Android programming"?
Me :" Yes. I do android application for both native and hybrid. As for hybrid, I use flutter."
Com :" Ok...but I was asking about android."
Me :*explaining what I just said *
Com: " you no understand! We need android programmer! Not native or flutter programmer!"
Me *explaining what native and hybrid is (in simple terms)
Com : " it is ok then.. our company prefer those who can develop android app , not native programmer or anything flutter programmer.
"
(Btw , I transcript how exactly that person talk to me)
My question to this person is.... WHAT THE F*** IS THIS? WANT AN ANDROID DEVELOPER BUT NOT NATIVE OR "FLUTTER"? WHAT THE FUCK DOES THAT EVEN MEAN ? IF ANDROID IS NOT WRITTEN IN NATIVE OR HYBRID THEN WHAT YOU EXPECT ME TO USE THEN? USING ASSEMBLY X64?14 -
naiive idealism to the max:
medior+senior to junior: "hey, buddy, we need you to do this, here's the codebase, here's the button, here's what needs to happen when that button is clicked, here's the relevant files and classes, make it happen."
medior to senior: "so what you just said about how we should redo the whole order processing pipeline, na-ah, not possible. i've been in those parts of the code many times, and based on what i've seen, you either leave that thing mostly alone or nuke it from orbit and build a completely new module in its place, but these "medium adjustments" you're proposing... not feasible...
senior to medior: "okay, i've seen how slow your progress was on even the most basic-sounding bugs in those systems... looks like what you're saying makes sense."
senior to *EO: not possible to just do these changes with this budget and deadline, that wouldn't even cover the "unexpected bugs" overhead, either you let us do it properly as a new greenfield project, almost, or you're stuck with what we've got.
*EO: mmmkay, so that's 20 times more time and budget that is in the proposal?
senior: yup, something around those numbers.
*EO (with a pained but understanding expression) : go for it, imma explain to the rest of the EOs at the end-weeks's meeting.4