Even tho we are all software engineers, everyone needs to specialize and become really good at a particular discipline.

What are you good at?

I've had to do everything myself for 10 years so I've had to get good at almost everything. But if I had to pick the thing I'm best at it would be backend web stuff and desktop development. Design is definitely not my strong suit.

Good in most things i care about but hopeless in design. Never made something beautiful myself. The lack of design skills is often frustrating. It makes me dependent. We don't want that right.

My specialty is overall performance, in general I work hard and I deliver. As soft skill I do the administration (tickets) part quite well. Documentation could be better, not a hobby of mine. I can talk endless about my projects but describing them in a professional way is hard in someway.

My preference is to write in C, but i don't have professional experience regarding that, in other most common languages I do have professional experience. Also, I like to write things from scratch (reinvent the wheel) where nobody wants to pay for. Sadly, it's mostly web because that's popular in the job market. But I realize that not working with the preferred tech is just a minor issue in comparison with people doing complete jobs they don't like which is common too.

I'm happy.

I also really enjoy tuning performane and memory usage. Im looking into cuda programming right now. I tinkered with openCL in the past but now It's time to get serious about these optimizations on gpu.

But overall I think Im good in most software dev stuff, except frontends, I hate frontends

Yeah, after doing almost everything like a whore for decades, I decided to specialize in native iOS development. I‘m much more happy now.

telling "agile solution architects", "ux experts" and other members of "middle management but with extra steps"-roles that their ideas are bullshit, and that it will fail in this and that way.

then later, telling the same people that things failed in this and that way because their ideas were bullshit.

For me, it's important to have the big picture of what I'm doing. It is changing constantly as I adapt to new challenges, learn from experiences, and respond to the evolving needs of the market.

@hightower you sound like a bot and/or an ad spammer.

Code theft

the "impossible"

I know how to break / reverse systems, rules, and for some reason people always think things are impossible to do when I can come up with at least 3 different ways to achieve that thing. or they just plain shout "wrong!" but if it works it works so I don't see the issue 🤷

I'm also very dumb though. like super lazy. but creative I guess. low patience. bad at paying attention to details, dislike wastes of time. either people think I have brain damage or think I'm impossibly intelligent

I remove redundancies anytime I get comfortable in something, and previous co-workers had a meme that I was perfect (due to my architecture) and memes about how I anticipated everything

as for what I'm doing it depends what I want to achieve from it. I just have goals and then pick up expertise in domains from that. Jack of all trades. I can do UI, backend stuff. I don't understand theoretical math but neither do the mathematicians frankly so I think it's something to do with them

I don't do much "normal" development anymore, specialized in reverse engineering, web + binary exploitation etc instead

also people tell me I teach things well

I dumb things down, can understand people's existing specialty and willing to describe things in analogies they may find familiar (though I'm sure awkwardly), and I guess I don't have the typical arrogant "you're beneath me" snobby perspective lots of educated people or people with some level of expertise do

I am good at asking questions. Seriously clients these days want everything now and they dont even know what they want. If they know, they don't know how their current software works. So in the end I end up asking the questions noone dared to ask and everyone is acting "it's fine"
The questions usually include
"Have you considered this also affects that part of the system?" "I know it's urgent bit is this deadline even feasible?" "We have these options, which way would you like to go". You could call that requirement engineering. I call that sanity.

I'm decent at a lot of things but I'm not good at anything. I aim at perfect balance by being boringly average.

I can climb an easy route and play an easy song. Write an easy program and eat an easy bow.