Last Topic: 10:18:09am, 02/15/2022
Last Post: 8:25:06pm, 12/24/2021
Sorry, I'm kind of just skimming over this especially when it comes to problem details, so you might have said this, but are you just doing these for practice, or are you putting the numbers on your resume? Do employers actually care about that at all? I think it's generally looked more highly upon to have some kind of side project, and you would probably get more personal enjoyment out of that too.
I'm in a similar boat, about three years of experience full time (though I have other job experience, and have programmed for 10+ years but not regularly) and am looking for that next job. I have decided that I hate programming outside of work though; I'm not even sure if I like it anymore at all, but that's the career path I feel stuck in.
IMO it's kind of a toxic part of the industry that you're expected to live and breathe it. I think it also causes people to put a burden on themselves to always find it fun, having that on my shoulders lately makes work miserable. I guess it would be miserable either way but eh. The interview process sucks ass too, real work is nothing like "reverse every other vowel in a string" or whatever.
I'd rather just hold out for a place that doesn't do these kind of problems and hope I get lucky, because they do exist, but if you want to spend your time on all these problems that's your prerogative. I don't think someone at the four-year level is expected to know a ton about the complexities of software inside and out though.