As the title say I am looking for some advice.
I’m almost 6 months into my first role and it really isn’t what I expected.
I’m late thirties and always had an interest in tech, but personal circumstances and a late start in life left me unsure if I was good enough.
I did too many boot camps and in all them they discussed how in your first role you would get lots of support to help develop your skills.
I work for a small company < 10. I don’t feel I get the support I expected.
A lot of time the spec is kept in the lead engineers (owners) head and when given a task I get no timeframe, the task is given verbally with 100 words when I need 1000 words. It’s confusing to understand their vision so I’ll do something and either be told great or no that’s completely wrong.
If wrong I’m not called out and they will spend a little more time going over what they want.
The boss is always so busy that sometimes you feel like a burden asking for pointers.
The tech stack is great but as a mature company they have refined the process over numerous projects and the newest will start as a copy of the last one, keeping all the shared hooks and stuff, so naturally it’s second nature to them and I feel stupid.
I guess my question is is this normal and how do I write an email expressing these concerns and to gauge how I am doing?
As an aside, there is no remote work and no headphones in the office, even though nobody really talks about work that often. So when is a good time to start looking for your second role.
I feel like I flip between I am a god and can code anything and omg I know nothing show me the nearest bridge.
Thanks.
You’ve got this bro.
Getting my first role was the hardest thing I’ve done and a little soul destroying. So much so that after the first bootcamp and many rejections I did another bootcamp and then loads more interviews.
I suck at interviewing as I have ADHD and I’ll either be too open and honest or I’ll just clam up and seem like an idiot. The more you do it the easier it gets.
If I can get a role, then anybody can.
Don't want to invalidate people with actual mental health issues and neurodivergence, but I also have some sort of undiagnosed issues. Suck at socializing, have some sort of behavioral OCD. I remember how I fucked up my interview by blurting out the name of the company incorrectly cuz I was nervous. The co-founder was so furious, he left the video call.
I've wasted an entire year trying to create a developer portfolio, and the entire cycle is hilarious. I wanted to create one of those advanced interactive OpenGL site with the most modern technology, so I went with Svelte, Tailwind, Threlte and DaisyUI. Worked on the project last December, gave up during January, because I didn't know shit about ThreeJS.
Tried again around March, was able to make a decent gradient mesh, but I didn't know anything about managing scroll in 3d, managing resize with canvas and stuff, so I preserved the 3d part, removed the entire stuff done with DaisyUI, and tried creating a fullpage site. Failed miserably, because now, it was very hard trying to make it responsive, now that both the horizontal and vertical screen were fixed.
Removed all of that, came across a Svelte video that was in favour of making components, so I did that, and tried making one of those generic rolling text SaaS page like portfolio. At last, I was so overwhelmed with ThreeJS and Threlte, and also the component thingy, and since the site was making my shitty phone lag hard, so I removed the entire 3d work. Now the website looked so generic, I removed everything and used the most simplest style.
Alongside that, I was also working on bunch of other projects, but completed them halfway and gave up.
So this entire year, I wasted on creating a single project. The design part of my home page is complete, and I'm satisfied with how it looks. Now for the blog and portfolio section…
Keeping it simple and moving on was a smart move. Your portfolio doesn't need to be super fancy unless that's the specific skill you're selling (fancy designs and UI). Most jobs aren't doing anything with threejs. Most jobs are crud apps, so focus on demonstrating skills to do with that.
Svelte is also cool but the majority of jobs aren't for svelte Devs, and most aren't for Greenfield projects with bleeding edge tech. Where I am for FE it's something like 60% react, 30% Angular, 10% Vue/svelte/whatever else. Just focus on building things which show you can do what the jobs you're looking to apply for need.
If you're going full stack then just focus on one stack and focus on building (preferably novel) actual things that all work together. If you have full projects showing you can self direct and implement semi complex systems from start to finish in a stack that's close enough to what employers are looking for you'll have a lot more luck landing a job.