FLOSS virtualization hacker, occasional brewer

  • 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle
  • There is a difference between reviewing code and the feedback when you have the job and during an interview when trying to get a job. I’m not saying you should never expect to be pulled up on mistakes just that an interview experience is very different to the work experience.

    Maybe there are ways to ameliorate the stress during the interview to get a better view of how a candidate will perform once hired but I think it’s a tricky balance to strike.





  • In my first interview they put me in a room with a PC with Borland C and a copy of K&R and a sheet with a simple problem to solve and some extra enhancements if I had time. They said they would be back in half an hour and left me to it. That I passed fine.

    Some twenty-ish years later I was asked to write a C function to reverse a string on a white board and I failed because I’d misformatted the for loop. I don’t think it was because I’ve become a worse C coder in the intervening years.

    When I’m actually coding I’m sat with my editor configured Just So with completion, compilation and unit tests at my finger tips. My favourite coding music blasting my speakers and a handy browser window for looking up anything in unsure of. This is my most productive setting and expecting the same performance in a stressful interview setting is foolish in my opinion.

    Working through problems on a white board can work well but you are looking for the problem solving approach, not an encyclopedic knowledge of regex syntax. Those same problems get immeasurably harder when explained over a phone call.

    My personal preference when evaluating candidates ability to code is reading their actual production code, the break down of commits, the commit messages and the sort of unit tests they add with a feature. The interview is more focused on their soft skills, what about the work excites them and what they are looking to get out of the role.



  • Directors have a fiduciary duty to the shareholders and that includes a legal liability if they don’t do their job. That said if the chairman has a controlling majority of the shares they can run the company into the ground if they want to as it’s their money to waste.

    Generally if you want to bring investment into a company it will come with strings attached like nominated seats on the board of directors to prevent this sort of thing. Voting shares can be different normal shares or there can be several share types with different levels of voting rights. However the structure of the shares will be disclosed to the board and for a publicly traded company this will be public.






  • Are you familiar with the Korean war? There was a massive conflict which got drawn out into a stalemate and everybody agreed a temporary ceasefire was preferable to even more destruction.

    Trying to topple a regime that has nothing to lose and a highly indoctrinated population is not an easy ask. We can only hope that like most authoritarian regimes they eventually succumb to the weight of their own opression. It’s better than torching the whole continent in the name of freedom.






  • So back in the days of the Atari ST we had compact disks (sic).

    Most games shipped on a single floppy disk (so 720k or 1.4Mb) and rarely used compression given the base system only has 512k of RAM. The crackers would strip the protection, repack the data and patch the loading routines to handle that. Depending on the games they could fit 3 or 4 games on a single disk.

    Nowadays the dynamics are different - games on consoles do use compression but they have to favour speed because they are streaming assets just in time. The PS5 even had dedicated decompression hardware to keep up with the data rate on it’s fast SSD.