@TYML can't help you there buddy, I have no experience in recent freelance world.
But same idea applies: find out how you would attract clients, and try to figure out what potential clients need. If you plan to use a freelancing portal, check posts to see what's needed.
Also, keep in mind seniority. If, for ex, they look for more senior android devs, but more junior ios, pick one that suits you better.
Also this approach helps you check what kinds of projects are more common on which platform. This may guide your decision.

@TYML it really depends on your local job market.

If that's you, gz

Work agile. At the end of each sprint have a working app, so that in the end you have a thing that works, at least some of the features.
Don't overwork on it. Keep in mind that after that, there will be another project, or that same one with extended deadline. You'll be developing for the rest of your life, an endless stream of projects, not just this one for 3 months. Learn from rants about deadlines, stress and burning out.

@DonnyQuest being surrounded by many other tasks gave him away.
Sadly, good engineers are often offered the role of lead, regardless of organizational skills. Add to that more responsibilities than he can handle, and you get described scenario.

My main question here is why is he so preocupied, which enabled this to happen in the first place?
Is he bad at delegating? Doesn't seem like it, he delegated the whole responsibility of a small task to a junior.
Is he understaffed? Something else? Is there a PM in this srory, or is it also lead's responsibility?

@Devnergy wow, that's great. I knew I was getting slower as time goes by, but you're astounding. From that little bit of information you managed to deduce:
1. That this happens on every ocasion, so that there is no sprint planning or estimation
2. That this is company wide, not isolated to that project or lead

Wow

JS developers moving to C

That functionality takes up space on the device. It maybe takes some other resources.
I don't know how many users use it and if it should be enabled by default.

Whoever evaluates your work, do what he says

Ignore dev, qa and management (unless management is boss of your boss). Make your actions transparent to all, and redirect future communication to your boss
"My boss occupied me with this work, I'l do what you're asking as soon as I finish this.
In case management is direct superior to your boss, you need diplomacy, and, again, transparency about your actions
And be prepared to change direction a couple of times

I don't mind as long as I'm:
Either paid by the hour
Or charging change requests insanely

Depends on if it's 7 days 6 hrs, which i wouldn't like, or 6 days 7 hrs which would be fine with me

Beter if it's 5days 7 hrs, one day 5 hrs

Check Torvald's reasons for chosing c for git, mandatory reading imo.

I can say about one of those companies, one project: low lvl c,embedded, programming. Some sort of rtos is involved for sure.
So, I guess rtos and basic concepts like data structures, algos and pointers are a way to start. I always recommend kernighan and ritchie c, idk for rtos.
Any embedded c job could lead you there.
It depends on you how interesting it will be for you, and on your teammates. First one you can experience during learning and decide if it's for you. Teammates you can't predict.
Career is very stable, it's been around since there was programming, as oposed to javascript.

Depends on job market in your area. Check job postings. Android and java ee with its enviroments are main applications of java. Toptal, for ex, is looking for android devs, and it seems to me that that market has brighter future as java ee is strongly contested with .net.

Ah, RDD (resumee driven development) strikes again: questioning work we're paid to do because of how it will impact our search for a different job.

So that other projects can use them properly

Great job,congratz!
Don't mind the presentation in the meeting, it's purpose isn't to present things realistically, it's advertisement.
And listen to your boss, learn to deal with unrealistic deadlines in a way that won't lead to you burning out. Luckly, there are great advices and rants here on that topic.

I agree.
Also, it would be better to outsource rather than returning the money. That way it's your responsibility to find someone suitable, since you guarantee quality.

Did you multiply the estimate by 2 before giving it to them?

Or didn't want to bother

I'm on the side that if you're touching a piece of code, leave it in correct state, even if it was not part of your initial task. But do it as a separate task. Be aware of premature and over optimization.
Whether this appliies to your case, I don't know.

@CodeMasterAlex just over the weekend I checked on status of this, to be notified that they didn't contact you and that they won't have time to do so... What can I say, I'm sorry for not checking earlier.

Congratz!

@Root ballsy. I like it.

As with other skills I don't have, I learn before doing. When I was job hunting for the first time, I had no idea how cvs and cover letters work. Cover letter wiki lists one book in further reading section. I read that and resume book from same series. I would recommend them, or any other that cover simmilar topic. It's stuff you read once and use regularly after that.

Boss is never late, he is needed in other places.

So the client knows that you're not on youtube all day without lookin at the code.

If you take a look at how much ++ are general rants recieving, and how much serious problems, all should be clear. Not to mention cat picures.

Codility