Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
viking818433yYes, it could be normal. Depends on what you are writing code for.
If you are doing web, then you should be able to produce from scratch relatively quickly. If it's some proprietary software, deep in business logic - then it takes time.
Last job I had was with robotics. I was able to produce within a few weeks, but it took almost a year before I understood the whole system and was able to see big picture.
Hand in there, don't give up. You can't really jump to system design and architecture before you've bled over code.
viking818433yInjection can be a little bit of a mindfuck in the beginning. Try out Autofac on your own, great tutorials and easy peacy, just to understand what is going on.
Angular takes a bit to get used to, then suddenly is easy as f, until that special case..
I've always advised the junior's I've mentored to try stuff themself. It's harder in an existing codebase, so start a new project, follow tutorials. Delete it, try from memory again and again. Do this both Angular and .net. Google stuff you are uncertain about.
Use Google search a lot, all seniors do to.
Dude, same thing happened to me. Luckily in my first job they also need software testers. At the time, I was much better suited for testing software than writing it. I switched to QA, got promoted and received raises year after year.
Fast forward a few years, I switched back to development because in that time of QA work, I learned so much about development that I could get by creating software.
@anon81 Also, I started to enroll in Udemy courses online for any subject/tool/language that I didn't have a good understanding of. I watched this videos on 2x speed until I learned enough to get by.
After a while, I started to enroll in these courses not because I was struggling with something at work, but because I was bored and wanted to learn something else.
Thanks a lot guys. Your comments actually cheer me up! I really hope I get the hang of this really soon. It's really depressing and scary at the moment!
binhex4613yKeep at it. If you aren't going through pain you're not learning.
I also recommend distilling your tasks down to simpler ones.
E.g: 1. understand what dependency injection is. 2. Why do I need it? 3. What happens to my code if I don't use it?
Update: well, something funny happened today. My boss called me in for a meeting, and I was pretty sure that I would get fired.
He said something like: "Well, be both know that development and coding isn't your strong side... but I've seen a great potential in your ability to lead and manage. How would you like to go in that direction?"
An hour of negotiations later:
New job title: Manager and scrummaster.
@anon81 Bro! That's amazing! In light of this change, I suggest you learn the hell out of software development lifecycles, agile vs waterfall, Jira, Confluence, maybe some configuration management stuff.
Basically, learn everything else about developing a software product other than the actually coding. Because at this point, you'll be heading down a road where you'll be interfacing with developers and senior managers, so you basically need to understand the processes more than the actually code changes.