[EnderMB]

The advice already given is good, but a few other points I'd like to add:

* I also have a degree in Computer Science, but with 18 months of professional development experience I'd still consider you a junior-level developer. 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.

* I wouldn't expect a junior developer to fully understand an existing code base without significant time workng on it. I'd also say that the only remedy for being good at this is to spend time working on large projects. CS degree or not, this is a new skill for you, so don't feel stupid for struggling with this. The only way you'll improve is to get a system set up locally, and to debug your way through the system until you understand what individual parts are doing. Some systems make more sense than others.

* I'd agree with the other users on going to see a GP, but I'd also add that you're not the first developer to have their mind wander in a meeting, and you certainly won't be the last. It sounds obvious, but have you considered writing notes during these meetings? I'm sure your PM's and lead developers would be grateful for the notes, and if it helps you to retain knowledge in those meetings then it's a win-win.

[m3tr0s]

> 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.

[EnderMB]

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.