Comments by "John Smith" (@JohnSmith-op7ls) on "ThePrimeTime" channel.

  1. 27
  2. 21
  3. 12
  4. 10
  5. 9
  6. 8
  7. 7
  8. 7
  9. 6
  10. 6
  11. 6
  12. 6
  13. 5
  14. 5
  15. 5
  16. 5
  17. 4
  18. 4
  19. 4
  20. 4
  21. 4
  22. 3
  23. 3
  24. 3
  25. 3
  26. 3
  27. 3
  28. 3
  29. 3
  30. 2
  31. 2
  32. 2
  33. 2
  34. 2
  35. 2
  36. 2
  37. 2
  38. 2
  39. 2
  40. 2
  41. 2
  42. 2
  43. 2
  44. 2
  45. 2
  46. 1
  47. 1
  48. 1
  49. 1
  50. 1
  51. 1
  52. 1
  53. 1
  54. 1
  55. 1
  56. 1
  57. 1
  58. 1
  59. 1
  60. 1
  61. 1
  62. 1
  63. 1
  64. 1
  65. 1
  66.  @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
  67. 1
  68. 1
  69. 1
  70.  @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
  71. 1
  72. 1
  73.  @cewla3348  You get jobs by learning the skills for what’s in demand. Dev work is over saturated. Especially front end dev. You can accept the reality and get the skills for jobs that are in demand and have long term demand potential, or you can insist the universe bend to your will and give you a high paying job and life long job security without you having to change. I can tell you now which one won’t work. Companies lied for decades about an IT worker shortage because they wanted to drive down wages. They lied about how they couldn’t find qualified American workers so they could import dirt cheap foreign labor with indentured servant like sponsored visa schemes. When there was a crackdown on that, they convinced everyone they needed to learn how to code. People who didn’t bother to research this stuff fell for it. It was all just to saturate the market so that these companies with lots of expensive tech workers could cut salaries and make more profits. Not only that but they can be super picky and demand 8 years of experience for a Jr role, or if they don’t call it a Jr role, they pay the salary of one. This is only possible because of labor oversupply. So you need to decide: Do you want to kill yourself trying to endlessly compete with more and more people for less and less pay, fewer jobs, and less job security? Or do you want to bite the bullet and make a career change to one where you’ve got some leverage? Most people change careers at least once in their life. Might as well do it now if it’s going to give you life long benefits rather than later when it’s harder and you’ve lost a decade or two in earning, saving, and investment ROI potential. And by making the change now while all the other deer are still staring at the IT job headlights, you’ll already be set and experienced in a solid field when the rest make a stamped for other fields as IT job demand plummets over the next 20 years.
    1
  74. 1
  75. 1
  76. 1
  77. 1
  78. 1
  79. 1
  80. 1
  81. 1
  82. 1
  83. 1
  84. 1