Great service, I advice you to take a look on your page from an iPad, about the whole left half of the landing page's top area is out of the viewport by default.
Thanks for the feedback. Yes, that will certainly be fixed. The reason is that Safari doesn't support .webm format that we are using for recording. We will need to serve .mp4 to Safari users.
I use Bear, which is a note app for iOS/macOS. It uses Markdown, it has all the features I need, and it is fast with sync. Because it has a really clean, minimalistic UI, I don't get distracted. This is my main tool know, but as most of the people who are even thinking about this, I'm not fully satisified. Separation of personal/work stuff is questionable, sometimes I feel I need better visualization (like mindmaps), and I regularly use it for todos too which is not the best if you also use a standalone todos app (TickTick).
Thank you for your answer. I got fired from my two last development jobs too.
I didn't like the first place, I haven't got too much help to even onboard, not talking about learning the codebase or the framework. (One thing I will never ever do again is trying to learn a completely different framework at a new job...)
At the second place however I felt I was pretty good. They mentioned areas to improve (productivity, meetings), but most of the feedbacks were good. Then they fired me. They "expected more improvement".
What is the mistake I shouldn't make again? Am I a bad developer, having problems or just unlucky?
I think the second place might have been a bit of bad luck, bit of not reading between the lines. It sounds like you can code well enough and your co-workers like you if you got positive feedback except for productivity and meeting issues which sounds like you're a good developer, but maybe have issues as an employee.
Are you currently employed and if so is your current place complaining, and if so is it the same things? I know after having been fired I get a bit of anxiety just thinking about those kinds of things even if I am doing well.
As others said on the falling asleep thing, do ask a doctor about it, you may have an attention disorder or sleep disorder.
Also do you participate in the meetings? If not, why? I found if its a meeting I don't need to be in, or can't participate in then its harder to focus and stay awake.
I also find that I am not good at 'using' my ears. I had trouble learning by listening when I was in class, and also by listening in meetings, I need to read something to have a chance at following along often. If you have a similar thing, ask if they can provide some notes or info about the meeting so you can prepare better. That may help.
I find on productivity, making sub-tasks for the day helps a lot. Something like:
* send email about x
* ask Y about Z
* look into A for project B
* do ticket D
* fix issues from PR for ticket Q
* do PRs for persan M and N
and then I just do those as well as I can each day and break them down into smaller tasks if need be. I don't care if I don't finish them really unless it happens a lot, and I add new things as they come up. I also normally make that list in Slack to myself so I can access it wherever I need to. This will give you a good baseline of where you are in terms of daily productivity. Also be sure that if you're doing a whole bunch of non-dev tasks, and they are measuring you on dev tasks, to talk to your manager about it. That's not fair or they be unaware of all the non-dev tasks.
But it sounds like the commonalities that happened in both jobs were not producing enough, and also sleeping or not being attentive in meetings. Work out why those are and fix those.
> In terms of skill level, you're absolutely fine, so don't worry too much about whether you should be better at certain things than others.
They fired me after 2.5 months working on the project, that's why I started to "worry" about my skills. They hired me as the only junior developer and as I think about it more and more, I'm starting to be sure not me wasn't enough, but a junior developer wasn't enough there in general.
Ah, sadly that's fairly standard - hire a cheap junior developer, expect the world of them, and fire them if they show even the first sign of not being able to do everything they ask with 100% certainty.
It may not seem like it, but it's a good thing to experience a shitty company, because you'll learn as much from how to not do things as you will from the "right" way.
A lot of people have touched on the focusing part. To be honest, I think that you sound like an absolutely normal developer, and all you need is an opportunity to grow at a good company. Out of interest, have you considered working at an agency? In my experience, they're a nice place to start out, because you get to work on numerous small to medium sied code bases over the space of a year, and the breadth of work allows you to build your experience while keeping time pressure on.
