As a general content I agree it's a bit off putting, but I find it a lot of fun when generating content among friends like internal jokes and educational content. I got my kid to drink some meds by generating an image of a hero telling him it's important to take.
Maybe you wonder what it is
Makes people good or bad
Why some guy, an ace without a doubt
Turns out to be a bastard
And the other way about
I'll tell you what I feel
It's just the nickel under the heel
Oh you can live like hearts and flowers
And everyday is a wonderland tour
Oh you can dream and scheme and happily put
And take, take and put
But first be sure
That nickel's under your foot
Go stand on someone's neck while you take him
Cut into somebody's throat as you put
For every dream and scheme, depending on whether
All through the storm
You've kept it warm
That nickel under your foot
And if you're sweet then you'll grow rotten
Your pretty heart covered over with soot
And if for once you're gay and devil-may-care-less
And oh so hot
I'll know you've got
That nickel under your foot
Yes but it seems the order is taught is important. Without actual industry experience, it never occurred to me it could be useful.
After some years working, it's clear it's useful in some capacity but it's easy to overdo it (like require every detail of the system to be in those formats) or misuse it (sequence diagram improperly documenting async flows).
Generalist can be a specialization in itself. Imagine someone that can do a bit of front-end, backend, infra, design, would be a specialist in bootstrapping a startup.
Don't get too attached to market/industry defined roles.
Another way to raise rates is to take risks (like deadlines, promises) but every person had their own risk profile.
This is absolutely true. Someone who is comfortable chasing down a problem no matter where it leads, and learning what's necessary to handle it if they don't already know, can provide a great deal of value.
Many clients don't need a specialist in X, they need someone who can do X, Y, Z, A, B, C, and oh we didn't realize we needed D and E but we're glad you're up for that too.
It's a fairly rare set of skills. People in these positive usually are bad in most of them and it becomes harder to ramp up the team later (mentoring, quality).
I think the biggest issue deep generalists fall into is that they can be above average in the entire stack, but not exceptional enough to make the cut for a specialized role in any single thing (i.e the vast majority of publicly advertised roles).
Going down “specialized in boot-strapping startups” route is an interesting remedy. I would imagine the only way to find these opportunities is word of mouth.
I didn't go through, but have seen quite a few. It's indeed a less advertised position since it might be more common in smaller companies (less money/reach) and it might be a founding opportunity (less pay, higher risk), so it goes under the radar compared to very specialized positions.
Or change the language. Instead of 'generalist', sell yourself as a senior developer, architect, lead developer, etc. Nobody asks "what programming language are you an architect in", because the job is supposed to be much broader than that.
I can't tolerate OOP stuff that `obj1.calls(obj2)` and changes `obj2` anymore. I didn't care before, now it makes me want to refactor everything or not write it at all.
Using Elixir kind of made me not want to use anything else.
