Joined devRant on 10/30/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
This year resolutions going to be rather ambitious. Hopefully not too much. :3
2.5kk steps this year, to get into decent shape and move more
finishing college - so fingers crossed for thesis writing motivation
and I want to have my first app published in Play Store this year, to start building portfolio
Also - get a new job, but after finishing thesis. :)
Good luck with yours, you guys. :)
!rant, but friendly advice.
I see all those jokes about Android Studio being too heavy, and while I completely agree, want to ask you guys something:
Have you increased the memory it can use in .vmoptions?
Mine lagged as hell, but was using only about 1GB of ram.
After slight change in that file, it finally started working like it should from the beginning.6
Ever feel like your boss is playing buzzword bingo with your project?
We have new project. Buzzword bingo words for us: microservices and cloud. We're moving our old, big, monolithic app to microservices.
And very strong demand that we keep all nasty solutions gathered in there for the last 10+ years working.2
I updated NDK, which resulted in some critical errors, because of outdated Gradle used deprecated NDK features.
I read about it, and decided to fix it properly, not hacking around - updatig that old gradle 2.2 to 4.10.2.
I spend about 6 hours fixing all problems and warnings that gradle had because of that, and then some.
At the end, some things still didn't work, but i was clearly missing some code from version control. I clicked update and left it for an hour.
THIS FREAKING BUGGY TFS PLUGIN RUINED ALL MY FILES I N THE PROJECT. WHY ARE WE STILL USING THAT F*King TFS???
Literally, I'm left now with .iml files in folders.
And my updated gradle files are gone too.
Using Bloodshed Dev-C++ and not wanting to change that for Visual Studio.
Transistion for VS wasn't simple, as I learned from the beginning od Dev-C++ and amount of 'hacks' that worked in DevC++ and didn't in VS were frustrating me. After a while I understood that DevC++ was a bad first choice IDE and things it did shouldn't have place, but habits die hard I guess.
Still like the lightweigh it had, tho. Wish VS was so simple in use at the beginning. :)1
What made you smile last week? Were you hyped for something or proud of yourself? What made you happy?
We had some frustration/fail weeks lately, so I thought we can talk about what brought us just joy. :)
Just share some joy with me!
I got accepted for a Android Developer Nanodegree and I'm hyped about it! Finally I'll have some good course with materials and motivation to learn more.4
Struggling to write my Engineering Thesis code. Not because I'm afraid of tech, but because I have no idea what it should do.
I'm testing mobile apps performance, but getting the right idea is pain in the ass. :(
Never been too creative, but always have been over ambitious and lazy.
So the deadline is coming slowly, I have specified my 'tests' (authorization, API connection, heavy calculations, graphics, database handling) and still don't know what my app should do.
And ideas or suggestions what else is to test?
Studying and working at tge same time is hard. I woke up before seven, spend 6 hours studying for exam I have tomorrow, now I'm going to office, and when I get back at 7pm I have to finish project for tomorrow and study some more for exam. Hate days like this one4
I am developing mobile version of c# app, completely alone in java/android. Still don't know how to use enums with int:string pair in java so I keep using arrays for this.
And I feel terrible everytime I add new thing like that.2
Why some people think it's fine to hire unexperienced people to do stuff, when there is no one in a company who could check if their code is fine?
Learning through active coding is fine. Until after two months later all you do is patching your code because you found out on stack that this is not a good way of doing it.