Comments by "John Smith" (@JohnSmith-op7ls) on "ThePrimeTime"
channel.
-
27
-
21
-
12
-
10
-
9
-
8
-
7
-
7
-
6
-
6
-
6
-
6
-
5
-
5
-
5
-
5
-
4
-
4
-
4
-
4
-
4
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
3
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
1
-
1
-
1
-
1
-
Apps really aren’t more complex now than they were in 2005. 99% of the time it’s just the same basic CRUD front and back end.
We’ve added a lot more ways to do the same thing and a desire to support them all adds complexity. Why not let people log into your app with every imaginable 3rd party account in existence? Why not create a bunch of ML models to figure out what to show people, which totally isn’t worse than a basic search and sort? Why not spend 300% more on cloud services and training everyone on them, then complicating all our apps to support the, just to get a couples of tenths of a percent uptime, in theory of course, than being down that extra time would ever cost the business.
Learning over complicated things makes us feel smart and gives us the hope of more job security. Implementing over complicated things lets us pretend our employer needs us because otherwise they could get by with half the team or less.
We also have a thousand ways to complicate simple things because every dev just has to have a bunch of repos on GitHub, because a resume alone means nothing, but rehashing some else’s code to make a library that does almost nothing, or already exists in 100 other flavors, that, that’s what an employer should look for.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
@kneesnap1041 Most things are poorly and unintuitive named which adds to the learning curve and cognitive overhead, it’s not designed for for what basically everyone uses it for, things like open source OS and kernel development vs corporate/gov development teams, and those extra steps and options create lots of opportunity to mess things up.
And while I know that there are the type who think endless flexibility in how you handle your branching strategy is just the best thing ever, it’s not, not when when most people using it will be having debates of which is way of branching is better, none of them are ideal, and there’s no guardrails to ensure people stick to whatever you went with.
If you have a highly experienced team, you know from lots of experience a specific branching strategy is the best for your team, and everyone just does everything right, great. But for everyone else, simpler, opinionated, and standardized lets you just get things done and not have to worry.
And the complexity leads to difficulty in visualizing the history without GUI tools, and there’s so many of those, the ones built into a lot of IDEs aren’t great so do you stick with that or buy some better commercial app, learn that and your next job probably won’t be using it.
Mercurial is a lot better, hell, even MS TFS (while lacking some nice to haves) is just so much easier to use for what most orgs are doing.
I don’t work on an open source Linux distro, and I’m guessing most of you, pretty much all of you, aren’t either. Git just wasn’t made for how most teams in orgs operate or the type of projects they work on.
Why not use the right tool for the job.
1
-
1
-
1
-
1
-
@frank13621 The last time I applied for a job I accepted was 6 years ago. I applied again last year, out of 3 positions I applied for, I got 3 interviews and one job offer, which I didn’t take because their initial claim of being fully remote was, in the end, revealed to be soon changing to hybrid remote, which I had no interest in. 2 of these 3 positions, HR reps reached out to me about. I also had another job last year offered to me through a personal contact but the salary wasn’t what I wanted, but they did ask for my resume and wanted to hire me, no interview needed. I didn’t really apply for that so I don’t count it, I just wanted to see what they would offer.
There was one attempt at applying for a job which I never actually applied for, so I don’t count that. I never submitted a resume, I first wanted some questions answered about the job and pay as the company was outside the US. They never replied over their “careers” email. I tracked down the personal emails of both founders and emailed them directly and also got no response. Given how small this company is and how casual their operating structure is by their own admission, not being able to get some very basic questions answered up front is a big red flag, so moved on.
I spent time researching these companies from multiple angles, tailoring my resume for the jobs and the nature of the companies. All in, I’d say I probably spent around 8 hours to get 3 interviews and a job offer, which is nothing really.
None of these companies were high profile tech companies but they did range from established startup to Fortune 500. I’d never even bother with high profile tech companies. I do have friends at Amazon NYC who could almost guarantee me a nice paying dev role, with decent stock bonuses and a signing bonus, but they all hate working there and despite still being “remote”, they feel obligated to fly to NYC several times a year to sit in a pointless meeting that could and should be done over a call, if at all.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1