When you're both a designer and a programmer at the same time

!rant

I know this may not be the typical post on Devrant and it may be a little off topic, but I could really use some advice from fellow colleagues here.

The thing is, I just finished engineering school and I got my first job as a software engineer. So far so good. I've never been a natural talent in this field, and I suck at writing code. I find things like architecture, system design, innovation, requirementsspecification, management and business development much more interesting.

These past weeks as a software engineer has been really challenging for me. I seem to be totally "in over my head", and fuck everything up. I can't understand how the code I'm supposed to write works, and can't solve even the simplest of tasks that are assigned to me if they involve any implementation of code, or fiddling with Github or build servers.

Is it normal to feel like this as an engineer with zero experience? Will things get better, or should I just resign or wait to be fired?

What would a natural next step for a software engineer who'd like to move more into business and management be? A MBA? Project management courses?

I hope to get some advice from you guys. Maybe you've felt like this when you started out as well? Anyway, any constructive feedback would be really much appreciated.

Question for devs who use Intellij IDEA.

How often do you use livetemplates?

I am a new android dev with ADHD and just discovered live templates. They make my life much easier, for example I have shortcuts for generating recyclerview adapter/viewholder/implementation boilerplate code.

In that way I am able to focus on implementation, and do my coding like building blocks, rather than memorizing every detail of implementation. Also I don't need to go to stackoverflow and copypaste basic things multiple times. Even for example during live coding interview having livetemplates seems awesome, copypasting from stackoverflow would be shameful (I think). Using my own custom shortcuts for livetemplates seems the best way for how my brain functions (I suck at memorizing tiny details, but I remember general idea/flow of a pattern and I would prefer memorizing what to use and when to use, instead of all small details of implementation).

Is getting to dependent on livetemplates a good practice to get used to? Do other developers frown upon a dev who has dozens of livetemplates and relies on them instead of writing all code from memory by hand?

I'm learning a new lang. Read all of the introductory guide. Have an algp to implement.

Suddenly I realize I suck at designing the implementation. Then I grab pen and paper and obssessively try to solve it all theoretically.

Or maybe I suck at this new lang? Who knows.

"if compiler can infer this, there is no need to add "x ->" , simply use it" ..AAAGHH FUCK YOUUUUU KOTLIN!! what else should i fucking not write? why do't you take a number of my employee and ask his requirements, maybe add a ShoppingKartApp.kt in your compiler next time? it will be completely inferred when i write "Fuck you" in the gradle.

And fucking companies are promoting this! I wonder how those devs are living there

Person A knows only that lambda is
{name:Type,name:Type->code}, and thus writes a clean code.

Person B comes says "This shit suck", writes "{ acc, i -> acc + " " + i }" ,goes away

Person A : "wtf is this shit? why it works?"

Please for the love of god, follow some rules! My first language was python, i love its zen:

- Beautiful is better than ugly.
- Simple is better than complex.
- Readability counts.
- Special cases aren't special enough to break the rules.
- There should be one-- and preferably only one --obvious way to do it.
- If the implementation is hard to explain, it's a bad idea.
-...

I just wish it follows at least one thing from python's zen : "There should be one-- and preferably only one --obvious way to do it."