Before that I worked on military software
8 karma · joined April 28, 2020
Before that I worked on military software
Any if you can't find mentoring at your current position, try some books. My first mentors were Andrew Hunt (The Pragmatic Programmer) and Martin Fowler. Start with them, or find your own.
Code mindfully, go deep to understand every little detail of the code you write or read. Ask questions. A lot. Don't stop at the first draft. Don't stop a the first pass of questions.
Keep at it for a while. That one day you'll wake up with the feeling that the code you write yesterday was good. And hell if it's not a beautiful day to make it even better!
Get some CS background if you feel you miss it. https://teachyourselfcs.com/ gets one Hacker News every now and then.
Work on architecture/design. Try to understand design patterns for example. Be critical. Try to understand architectural decisions of the code you read.
Don't understimate the efficiency that comes with really being fluent with a language but do not give fluency too much credit either.
This is a lifetime journey. Improve step by step, little by little, every day. But improve mindfully. Get a direction. Get learning goals.
It's not a "try harder" it's juste question of better orienting the energy maybe.
That's my 2cents.
Good luck, I'm sur you can get, better you just need guidance.
The guy in charge of those before me was the kind that use aha question with no relevance whatsoever. Pure ego trip. If that guy had interviewe me I would have said "I don't know" a few times and eventually get up and leave.
For my candidates, I tried a few things. Now I've got it down to explain to me your last project. I ask questions until I've understood every little detail of the project. Then we code a few simple "exercises" with increasing "difficulty". The candidate is allowed google, documentation, questions, anything. Then we read code. A piece of code with a "bug" or a feature to add.
The key is to make them talk about concept from impérative, fonctionnal and object paradigm and interact like a junior and senior dev would in a dev team.
I found that junior candidates react pretty well to these. Some of them thank me for having had the opportunity to learn about new things like functionnal programming. It's pretty cool and I feel that make them want to join us most of the time.
The stones released a classic blues album lately. That was purely for them not so much for selling. They can afford that because of their huge fame.
I firmly believe animal rights movements should discourage pet owning but it's often the other way around, at least from where i'm from.
When you see an upside down toilet in a museum and art enthusiasts in awe and say "I could have done that" you express you incomprehension : why is something so trivial admired? I thought I had to do something exceptionnal to get admired. The answer you get is "But you didn't", yeah because I didn't think a toilet had value.
You feel mocked by the artiste. Cheated.
So yeah, creating is hard and it's pretty hard to understand how hard before you tried it yourself but still people should be able to express their total incomprehension of the enthusiastic response de see around them for weird stuff without getting dismissed by a "but you didn't".