👍

😂😂😂

Yep. I would have re-recorded it except that was my second time because of that same issue and it was late. Stupid Windows Updates. I thought telling it "not now" was enough. Nope. It asks you again in 20 minutes, just in case you changed your mind.

Haha that's' cool to know more how is the set made

I'm glad my content has been helpful.

Thanks!

Thank you!

You are welcome.

You are welcome.

That's not typically an issue. If you find yourself consistently over-estimating how long projects will take to where it is a problem, you are probably not spending enough time actually working on finishing the project. Projects can work really early on in the process. The bigger issue is dealing with edge cases and ensuring that you have a really good user experience (not just a flashy UI).

My first suggestion would be to have you work through your feelings about development. Becoming depressed because of an unresolved problem in your code is really unhealthy. It sounds like you might be connecting your self-worth to what you can do with code. Please don't tie those two together. Who you are as a person should not be dependent on who you are as a developer. The vast majority of the time a developer spends writing code will be spent on fixing mistakes and tracking down problems. If your self-worth is tied to being able to fix mistakes immediately or not make them at all, you will not be able to work. If you really cannot disconnect the two and if not being able to fix a problem immediately causes you to be depressed, my recommendation to you would be to look for a different career. In the end, I really think you need to address the root issue because it will follow you wherever you go, but there are some careers that will be much more conducive to your mental health. Dealing with the constant problems in development will not be one of them.

@@IAmTimCorey What causes me the problems is because there is an app i really want but know if i can't fix the problems, then those apps would never be created. On the job its worse because if i am unable to fix the problems, then i lose my job then. what i find that happens is i get depressed but if i am able to fix the problems, then i get excited because i go it fixed and can eventually have the app i always wanted. i actually got into development because i wanted more automation and more custom apps and processes.

Go back and read my previous comment again. Your clarification doesn't change my advice. If this is how working in software development makes you feel, you either need to work with a counselor to change your viewpoint or you should not continue in the software development field. Tying your success as a developer to your self worth is incredibly dangerous.

Managers struggle with the same thing as everyone else - accepting the reality of what is rather than what you want it to be.

And how you know what steps should bem documenting? To avoid loosing time in the future. After collecting everything it gets so hard to find what you need.

It sounds like you could use practice in project management. Taking the initial requirements, identifying the assumptions and eliminating them, breaking the resulting data down into a series of tasks, completing those tasks, and then documenting what you accomplished. You are always going to struggle when working with other people. That's the nature of working with other people. The key is to get better on your end at knowing what to ask, how to document it, and how to execute on it. The way to get better is to honestly evaluate where you could be better. Not where someone else could be better at getting back to you. Evaluate how you could better organize the returned information next time. Then evaluate how you could ask better questions next time to get more precise answers.

I've been there, done that. Actually, I really like classic ASP. It is a culture shock, though, when you switch back and forth.

👋

It was always a pain.

Identifying the issue is a big step towards fixing it.

When has that not been true? You can always see the future as chaos. You can also always see the future as bright. It all depends on how you want to look at things. In my experience, things are never as bad as predicted, nor are they as rosy as others predicted.

Thanks!

Nope. And unfortunately, that was taught to them by the professor. The thing is, though, that's what happens when you code with "magic". When you don't know why things happen, it is magic. When it is magic and the magic stops, you are helpless. That's why I am so insistent on learning things fully and not skipping past something until you actually understand it. Doing so gives you confidence as a developer, which makes you better at what you do and makes you happier in the long run.

😂 She doesn't read these comments, does she?