• 1 Post
  • 32 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle
  • It’s not good. Sometimes the only computer a kid has is a chromebook because their parents got it for them for school. I’m seeing more and people just don’t have computers at all. PC isn’t moving fluidly to the next generation as a result. I’ve told parents about steam deck hoping they’ll pick that as their kid’s game console, but it’s not as easy as when I was a kid where you just had a computer anyway and it was about if it could play the game you wanted to play. With the indie scene that concern when away a lot, but now a lot of kids just don’t have PCs





  • That is a difference people make in their mind. I don’t see a difference. The criticism is the critism. If you receive enough negative feedback on PRs after being hired, you will be fired for not be good enough.

    The only way to take away the stress of an interview is to not care about the outcome. I don’t and interviews are stressful for me. I present myself as I am and if they don’t like it oh well, but that is a confidence I think most people don’t have. I have been like this since I was junior so it’s not the arrogance of experience. It’s not even the confidence of easily being able to get jobs because in my early career it would sometimes take months to get a new job. I’d ask for feedback if I could get it and accept or disregard it. Some feedback amounted to, “this wasn’t the job for you” and that’s okay.

    I just don’t think it’s worth worrying about any particular job when hiring is like dating. You can be perfect for one job and an obvious no for another, so it’s not worth worrying about the outcome. They like you or they don’t.


  • Your post was about stress not anxiety and theu are different things. My point is that these these kind interviews approximate what you will actually do at work. If someone finds them stressful then they should think about if this is the career for them. Feeling anxious is another thing, but you can feel anxious while being confident because anxiety is about fearing and unknown outcome.

    My point is that people should fine these interview styles stressful and that has always been my point and what I have been replying to since you never brought up anxiety until now.


  • The literal point if interviews it to judge. The point is to find people who will work in the environment you have. I have done work on codebases where bad code means people die, by indirect or direct results. This probably biases me. For example, I have coded in front of a group several times. This year in fact. Sometimes a problem involves multiple people thinking through it. That’s probably why I don’t care about panel interviews as well. I have had to explain myself in front of a group several times.

    These are things that people find stressful, but they are part of my job and have been at nearly every one of the little over half a dozen jobs I have held. My current job isn’t even doing anything important. No one dies if I make a mistake and I’ve still experienced explaining myself in front of a group and coding with several people onlooking. I just assumed that’s how the job is as my friends in the same field have similar kinds of stories

    People can be stressed I guess, but is normal and common events in your job are highly stressful, then I still say that’s a sign that it’s not the career path for you. For all we know, these jobs have these things because it’s common on the job and a candidate should really feel at ease doing it. That’s my opinion anyway. We can only form opinions based on experience and apparently, mine differs from yours.


  • I don’t agree at all. I’ve definitely been in lair sessions where the other person has been assigned to babysit me to the correct answer. It’s just an experience that mostly happens with juniors. I’ve babysat juniors to the solution myself.

    There can also be zero trust between colleagues forced to pair, especially in debug sessions. I have worked a lot of jobs, so maybe it’s just my experience, but I would not say that if categorized every single pair session I’ve had in my entire career anywhere near half involved two colleagues who trusted each other and didn’t judge.

    I’ve definitely been judged as a senior for dumb dumb moments and that’s okay. If you care about people’s opinions too personally as a software engineer, I’m not sure this is the career for you. It’s a career that involves a lot of negative feedback even as an experienced professional.


  • I guess my question why should anyone feel stressed from live coding? There are some jobs where this is legitimately a common occurrence at your job. Some jobs are big on pair programming. And I don’t think I’ve ever had a single job that at least a couple times a year didn’t have me living coding through a problem. It happened way more often when I was a junior and needed a lot of assistance. If you are stressed by being watched while you code, that’s not great because you are going to have to do it regularly or semi-regularly at your job. That’s whether someone is sitting right next to you or they are screensharing. It’s why I personally am comfortable with live coding. It’s literally a thing I do at work, albeit not with toy problems.


  • The problem with only hiring people you have met personally is that you miss out on a whole world of people who would be great to work with but had no chance of ever meeting you or your network. I agree that network recruiting is the safest route, but having diversity in your employees is great. If you only hire through your networks you’ll see quickly quickly how you only get one kind of person.

    I have seem this happen a lot in smaller companies. It’s also the story of how I’m typically the sole woman in the department. I by happenstance happen to seed my professional network from college with a lot of men (because I accidentally picked a college that like 80% men). I’m a unicorn because many men’s networks include so few women since in IT they tend to be non-traditional and/or generally excluded from younger men’s social groups.

    I get tapped via my network all the time. But if the company basically only does referral based hiring me and perhaps one other woman is there for the whole engineering department. It’s way more balanced at 20%-30% of the department at companies that don’t do this. There is some value in shotgun hiring even if it has a higher fail rate than referral hiring. Different kinds of people can bring fresh perspectives and considerations.



  • Nope. Because I know I’m going to be a complete purge and I know that no one has uploaded any media, I just nuked the folders after being reasonably certain nothing bad would happen. I think that I’m going to end up writing a periodic proper purge script that is going to directly talk to pict-rs and will be awful for me to do because I know fuck all about docker, so some experimentation will be necessary.



  • That’s a good point. I’ve just been assuming that the media is the issue, but perhaps it’s just the pure database 🤔 Does doing a truncate purge the media? If not, wouldn’t I just be orphaning all these pictures, etc that have been downloaded? Also what about the fallout of your own users? I don’t really want to drop the content that was created on the instance itself



  • Because it’s inescapable. Web development is by far the most common type of programming work and even if you’re a backend developer you tend to have to touch javascript at some point, so everyone knows the pain of javascript’s foot guns and javascript has a lot.

    The fact that it’s mandatory to do your work invokes bitterness in people. For backend, you can kind of switch around until you find a language you like. For frontend, it’s javascript or nothing at all.

    Javascript as a language is very out of sync with other commonly used languages. Its footguns are very easy to run into. As a result you have a lot of rituals around just not shooting yourself in the foot. The rituals, libraries, and frameworks around avoiding Javascript’s foot guns have been very shifting and changing. Of course, because the javascript ecosystem changes far faster than other languages, there are a lot of rakes for developers to step on to add to the naturally existing foot guns.

    Javascript as a language probably shouldn’t be the sole language of the internet for a variety of reasons. It’s a very hateable language because of how easy it is for newbies to make new terrible code and how common it is. Until something like WASM takes off, the downpour of hate for javascript will continue.



  • I feel like this is only true of internal or enterprise software where switching is expensive. For business to consumer, the impact of bugs can cause a company to go under or at least become a zombie. For any type of company, the thread of a competitor is high and can cause your company to stagnant and slowly go under or bleed and rapidly go under.

    There is a real impact to a high amount of bugs, it just doesn’t happen in one quarter. It happens over years and results in higher stress foe the developers. A stagnating company doesn’t hire. It doesn’t give raises and slashes benefits. A lot of terrible things happen before a company goes under. We can watch Twitter speed running this.


  • I wasn’t talking about rewriting an existing system either. I’m talking about adding to a system. In order to do that effectively, you need to understand the system as it stands and consider how any requirement could clash or be impossible with the current set of requirements. This is why I bring up the AI needing to pull a set of requirements from the existing code. You cannot add requirements without knowing the requirements that already exist.

    I think that hallucination is still a massive issue. I don’t even like to call it hallucination because what it really is bad guesses. We should never forget that all any AI does is guess. It doesn’t reason about anything or connect information together. AI will hold contradictory positions because of this.

    Currently we have no way to make an AI declare that it just doesn’t know or even very often ask for more information in order to make a decision because the method of training an AI is literally guess and check.

    For that reason, I don’t think that AI will ever be the tool for the job when it comes to any kind of requirements gathering. I mean I guess you could, but I always run the risk of being like that lawyer who had made up cases in this result. AI made things up because all it does it make its best guess and it doesn’t care I’d that guess is grounded in much of anything at all.


  • I feel like AI would fall down even harder here. A lot of long running applications have “secret” rules in them that developers have as either tribal knowledge or they have to reas the code and see is the case. Will AI be sophisticated enough to read a massive repo probably dependent on several others and have a realistic understanding of the requirements inherent in that code system? Because that’s what we pay senior devs to be good at quickly figuring out. I find myself skeptical that AI will be able to do that in a trustworthy way with how it “hallucinates” now and doesn’t have the concept that it just doesn’t know sometimes. If a developer has to spend time checking the AI’s assertions about the rules, is that actually going to be faster than just keeping them in their mind or doing the research themselves?