nixCraft π§
ππππππ@nixCraft
So true π
Kevin Karhan 
@nixCraft true, true...
Finnley Dolfin@nixCraft I really needed this.
Iβve had major imposter syndrome every time I tell someone I code Python because I still need to look things up, even the most basic stuff.
Thomas H Jones IIOr.. "Last time I had to do <PYTHON_THING> was in Py27 but that now errors in Py39".
Or "Last time I had to do <PYTHON_THING> was in Py36 but the linter now errors because the Pip module I'm used to using has been deprecated in Py39" (or you've been working a Py39 project and get asked to help on a Py37 project and the module that allows you to do something in 3 lines rather than 30 isn't available in Py37 so you have to look up the old/harder way).
basisbit π¦πͺπΊπΊπ¦ π KnSt@nixCraft Not true for many cases. If you stay in one field and one tooling and one language and one framework for a few years, you'll eventually stop searching for solutions online because at that point they usually are not helpful any more, or you just find your own questions from a few years before on Stackoverflow or issues at GitHub and still no one answered.
Ordinary Wonder@OrdinaryWonder @nixCraft Just recently I had a support case where we decided to pay external consultants to fix an issue, I explained the problem with a sample code and everything, and a week later, they came back with an almost usable solution... and a github pull request as source... which was written by myself approximately 3 years ago.
@OrdinaryWonder @basisbit @nixCraft
Once you reach a certain point in your career, those 20% jumps get really rare ...but a 5% annual bump at your current job eclipses a 20% jump from one of your earlier jobs.
@ferricoxide @basisbit @nixCraft it makes sense to me that those opportunities shrink over time. However every complaint Iβve worked at has made the average raise about 0.5% less than inflation. Which of a big part of the reason I end up with 20% on the job change. We shall see about my new company. They claim to be different.
@OrdinaryWonder @ferricoxide @nixCraft I definitely suggest collecting some offers from different companies every 2 or 3 years, and then asking your current employer if they want to approximately match it or rather loose you... Also, ask for an interim report a few months before asking for that raise.
@basisbit @OrdinaryWonder @nixCraft
I continue interviewing, if for no other reasons than to stay in practice and to see what it is other organizations are shopping for (so I can better guide my efforts to keep myself current and in demand).
Down side is:
β’ it exposes that there's a lot of organizations out there that only need a subset of that experience and only want to pay for that subset, even though they'd like to get access to the greater set
β’ Most of the places willing to offer more don't want to pay significantly more (and make the jump-risk worthwhile) or the likely stress levels are frighteningly obviously no less than the current position (meaning they're probably worse)
@OrdinaryWonder @basisbit @nixCraft
I've been in consulting most of my career. That's meant I've seen how other companies work on anywhere from a weekly change-basis to tens of months. Mostly, what I've observed is every organization is broken, just in different ways. Consulting means that I can escape a given flavor of organizational brokenness without having the hassle of actually changing my non-customer employment terms.
@nixCraft
Though, what happens tends to be, "I *know* how to do <THING> in <LANGUAGE_1> but I've been asked to write this program in <LANGUAGE_2>: what's the equivalent code look like".
See: the bajillion regex implementations or ability to state equality and/or equivalence.
π¦ππππ¦
Pete Gamache@nixCraft Three or four years ago, I wrote a ~20 line web page, including styling, and it came out right the first time. Felt great. I have been doing this since 1995
Taylor Parizo
stuwares (@[email protected])
Attached: 1 image @[email protected] tryhackme day 17 was all regex