Asklemmy

43757 readers

1721 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

As a new, one year, software developer who retrained late. How do you know when you're ready to apply for a new role with more money? (discuss.tchncs.de)

submitted 4 months ago by dependencyinjection@discuss.tchncs.de to c/asklemmy@lemmy.ml

19 comments fedilink hide all child comments

As the title states. I’ve been a software developer for a year now and work for a tiny company, where the salary isn’t amazing. I got paid more at Apple Genius Bar, but it wasn’t as challenging.

I still feel like I’m stupid, I’ll rely on the owner lead engineer for help on the more complex problems and because we have a great set of conventions I’ll frequently be going back to old projects to extract the logic from their. Whether that be reading from Excel spreadsheets or the controller flow, as we use GraphQL api for most calls.

Does it just click at some point?

you are viewing a single comment's thread
view the rest of the comments

[–] cAUzapNEAGLb@lemmy.world 72 points 4 months ago (1 children)

Some advice that has taken me over a decade to learn myself:

There are no rules, the titles are made up, the responsibilities and requirements do no matter.

Get what you can from your job, and once you get something do your Best even if that best sucks, and stay until you have gotten what you want out of the job, or realize you can't or don't want to do it anymore, and then start again doing something else.

Don't ever limit yourself thinking you need to "level up" or something needs to get unlocked.

Learn by doing, try your best, you will make things that suck sometimes, but as you do more and more you should be making things better.

[–] dependencyinjection@discuss.tchncs.de 13 points 4 months ago (2 children)

Thanks.

I think you’re right in that there are no rules, and although this is something that I don’t cope well with, I like set paths and to know how to approach things rather than yeah just do you.

I guess it’s hard when one minute you feel like a god and the next you feel like an imposter.

[–] slazer2au@lemmy.world 12 points 4 months ago

I guess it’s hard when one minute you feel like a god and the next you feel like an imposter.

Honestly, that is normal. Even for those of us in other IT industries. If you have been there a year then they trust the work you are doing is correct or they would have had improvement plans.

What you can do is go to your tech lead and ask if he can point you at resources to improve your skills.

As for the pay, remember to job hop every couple years to bump it up to keep ahead of inflation.

[–] SamuraiBeandog@lemmy.world 8 points 4 months ago

I've been a programmer for decades and I still sometimes look at code I wrote 6 months ago like what the fuck was I thinking. Code is as much art as science.