My Workplace Honeymoon is oOver My Workplace Honeymoon is Over

The Workplace Honeymoon is over The Workplace Honeymoon is over

I have been working at my current company for half a yearsix months now. I have been working at my current company for six months now.

"Half a year" is correct, but most American native speakers will instinctively say "six months" before they say "half a year."

I have been working at my current company for half a yearsix months now. I have been working at my current company for six months now.

When I started, I was always excited, and. I couldn't wait to begin the day and work withgo to work and explore new technologies. When I started, I was always excited. I couldn't wait to go to work and explore new technologies.

When I started, I was always excited, and couldn't wait to begin the day and working with new technologies. When I started, I was always excited and couldn't wait to begin the day working with new technologies.

However, aAfter six months, my initial excitement has waned. After six months, my initial excitement has waned.

You can say "however" here, but "however" and "after six months" are both antecedents, and it sounds slightly awkward to have multiple antecedents.

I am a Junior Software Engineer, but sometimes it feels like people who have been working there almost for a decade have the knowledge and the experience of a beginner. I am a Junior Software Engineer, but sometimes it feels like people who have been working there almost for a decade have the knowledge and the experience of a beginner.

I am a Junior Software Engineer, but sometimes it feels like the people who have been working there almost for a decade only have the knowledge and experience of a beginner. I am a Junior Software Engineer but sometimes it feels like the people who have been working there almost for a decade only have the knowledge and experience of a beginner.

And eEven if I explain to them exactly what to do, they still don't seem to grasp it. Even if I explain to them exactly what to do, they still don't seem to grasp it.

Whenever I write "even if," I always end the clause with a comma.

And even if I explain to them exactly what to do, they still don't seem to grasp it. And even if I explain to them exactly what to do, they still don't seem to grasp it.

Weeks, —hell, even months —pass by, and they continue to ask the same questions with exactly the same issues repeatedly. Weeks—hell, even months—pass by, and they continue to ask the same questions with exactly the same issues repeatedly.

For clauses where you interrupt yourself, you want to use commas or em dashes.

Weeks, hell, even months pass by, and they repeatedly continue to ask the same questions with exactly the same issue repeatedly. Weeks, hell, even months pass by, and they repeatedly continue to ask the same questions with exactly the same issue.

When I tell themanswer their questions, they say that they understand it, but I already know that they don't, it. It’s just happened so many times. When I answer their questions, they say that they understand, but I already know that they don't. It’s just happened so many times.

"It's" can be an informal contraction for "it has." You could say "it has" instead, but I use this contraction when I speak!

When I tell them, they say that they understand it, but I already know that they don't, it justhas happened so many times. When I tell them, they say that they understand it but I know that they don't, it has happened so many times.

One of the most important aspects of my profession is to be experimental and play around a lot (If you f** around, you'll find out). One of the most important aspects of my profession is to experiment and play around a lot (If you f** around, you'll find out).

The phrase, "Fuck around and find out," is usually used as a threat or as a warning of bad consequences. For example, the speaker often means that if you are rude to them, they'll attack you. Or if you do something stupid, you'll face professional or personal ramifications. I wouldn't use that phrase for learning by playing and experimentation, which is indeed important for learning any skill!

One of the most important aspects of my profession is to be experimental and play around a lotexplore new methods (If you f** around, you'll find out). One of the most important aspects of my profession is to be experimental and explore new methods (If you f** around, you'll find out).

AND TheyYet these are supposed to be the Senior Engineers.! Yet these are supposed to be the Senior Engineers!

You wouldn't capitalize "they" unless it starts the sentence. I also modified the sentence to sound more appropriately angry!

AND Theynd THEY are supposed to be the Senior Engineers. And THEY are supposed to be the Senior Engineers.

I really don't feel entitled to tell them what to do as a Junior Engineer, and i. It feels odweird to have to explain things to them as if they were beginners. I really don't feel entitled to tell them what to do as a Junior Engineer. It feels weird to have to explain things to them as if they were beginners.

"Odd" works, but I would use "weird" or "strange" instead. This might vary by region, but in my area and dialect, that sounds slightly more natural.

As a Junior Engineer, I really don't feel entitlobliged to tell them what to do as a Junior Engineer, and it feels odd to have to explain things to them as if they were beginners. As a Junior Engineer, I really don't feel obliged to tell them what to do and it feels odd to have to explain things to them as if they were beginners.

I really don't know what is happening on their side,. I have had experienced thats whenre I couldn't do anything, and received no help, and i. It was a really painful experience, so. I don't want to be that person who doesn't give them the help, but when I went through this, I was an entry-level developer at that time, earning a minimal salary, not a senior engineer at a multinational company. I really don't know what is happening on their side. I have had experiences where I couldn't do anything, and received no help. It was a really painful experience. I don't want to be that person who doesn't give them the help, but when I went through this, I was an entry-level developer at that time, earning a minimal salary, not a senior engineer at a multinational company.

I really don't know what is happening on their side,. I have experienced that when I couldn't do anything, and received no help, and iknow what it’s like to not receive any help when you don’t know what to do. It was a really painful experience, so I don't want to be that person who doesn't give them the help, but I was an entry-level developer at that time, earning a minimal salary, not a senior engineer at a multinational company. I really don't know what is happening on their side. I know what it’s like to not receive any help when you don’t know what to do. It was a really painful experience, so I don't want to be that person who doesn't give them the help but I was an entry-level developer at that time, earning a minimal salary, not a senior engineer at a multinational company.

I have created documentation, and example code, toldwhich I've shown them countless of times, and s. Still no improvement. I have created documentation and example code, which I've shown them countless times. Still no improvement.

"Countless" is more like an adjective than a noun, so "countless times" is grammatically correct. "Still no improvement" is technically a sentence fragment, but that's how English speakers talk when we're exasperated!

I have created documentation, and examples of code, told them countless of times, and but still no improvement. I have created documentation and examples of code, told them countless of times but still no improvement.

I waste so much time just to debugging their code, create theseing documentation that they are not going to'll never read, and so on. I waste so much time debugging their code, creating documentation that they'll never read, and so on.

"These documentation" sounds strange in American English.

I waste so much time just to debug their code, and create these documentations that they are not going to read, and so on. I waste so much time just to debug their code and create documents that they are not going to read, and so on.

Have you ever encountered a similar situation, and i? If so, how did you go about improving or managing it? Have you ever encountered a similar situation? If so, how did you go about improving or managing it?

Have you ever encountered a similar situation, and if so, how did you go about improving or managing it? Have you ever encountered a similar situation and if so, how did you go about improving or managing it?