maccard

22 ms·

601.
by maccard 8mo ago
Oh absolutely. The wireless for gaming headsets isn’t Bluetooth either. If your argument is Bluetooth isn’t suitable for real time, I’m on board - I’d even go further and say Bluetooth isn’t suitable for anything other than fire and forget.
602.
by maccard 8mo ago
Real time covers a lot of different things, and have a lot of different solutions. Do you mean real time like games? “Wireless” headsets are perfectly fine and usable. Real time audio? Wireless transmitters and receivers exist and are used
603.
by maccard 8mo ago
I’m with you. It’s very telling when all of the tools are being rewritten and seeing orders of magnitudes of speed ups. It just shows that people don’t value the actual performance of what they’re running.
604.
by maccard 8mo ago
There’s a middle ground between node and rust. Dotnet and Java are wildly productive places to work but they’re not as exciting as rust. Also, writing JavaScript for the backend is needlessly underperforming for anything with any load.
605.
by maccard 8mo ago
I’ve ran MP game servers that follow this pattern. A good rule of thumb is you should cover 75% of your peak load with your cheaper steady state pre allocated machines, and burst for the last 25%. It really is that expensive to do.
606.
by maccard 8mo ago
I'm not OP but - an interview typically has a power imbalance. They have a job and you want the job, therefore the balance tips in their favor. If the candidate is a headhunted candidate (imagine a video game studio trying to hire a cr
607.
by maccard 8mo ago
> You say "likely familiar with" but interviews are conducted as if it's a pop quiz. Which I never understood. Sure - the point of being familiar with it is so that we don't have to spend a chunk of the very limited t
608.
by maccard 8mo ago
> why not buy anything else that is Linux friendly and you get software updates I don’t want to use Linux at home. > do yourself and the world a favor and buy this instead: It’s 50% more expensive when you add in the memory and the ha
609.
by maccard 8mo ago
If the interview goes: > What would you do if two different people were emailing a spreadsheet back and forth to track something? > I’d use google sheets > Excellent answer, that is what I would do as well, now what if we wanted to
610.
by maccard 8mo ago
> I am, just to be clear, not defending people being willfully obtuse or contrary jackasses The comment I replied to said: > "now what if we wanted to build it in-house?" > "Well I would probably go home and work on
611.
by maccard 8mo ago
> when the moment calls for it In an interview when you’ve been explicitly asked to discuss a topic to have a technical discussion about something is not when the moment calls for it. Doubly so if you’ve been asked twice. If you’re not w
612.
by maccard 8mo ago
Yeah - for sure. When I’m interviewing I want to give the candidate the best chance of success and to show off both what they know and how they will work with me. I generally give it three goes with questions like these - the initial ask, a
613.
by maccard 8mo ago
The question isn’t should we use gsuite, it’s can we talk about a tech problem. If you don’t understand that you’ve failed the interview.
614.
by maccard 8mo ago
I’m not hiring on compliance. I’ve accepted that his answer is correct but asked for the purposes of the exercise if he can put that to a side so we can talk about it. I’ve worked with and hired people like this and they tend to turn every
615.
by maccard 8mo ago
> While you consider it a huge warning sign, have you ever employed someone who would answer that way or are you assuming that you're not capable of making hiring mistakes? I can't help but think this "huge warning sign&qu
616.
by maccard 8mo ago
I’ve interviewed a few hundred people. Probably approaching a thousand, if not already. An interview is a scenario, and if you aren’t willing to engage in the scenario that we all agreed to partake in, that’s a huge warning sign that you’re
617.
by maccard 8mo ago
This is an absolutely solid buy I think. My wife's macbook is no longer receiving MacOS (and as a result Safari) updates, and all she needs it for is "big laptop tasks" and occasional video calls. This is the absolute perfect
618.
by maccard 8mo ago
> At this point though, after Claude C Compiler, Perfect example. You mean the C compiler that literally failed to compile a hello world [0] (which was given in it's readme)? > What do you consider simple issues? Hallucinating AP
619.
by maccard 8mo ago
> I don’t think that’s true. Claude Opus 4.5/4.6 in Cursor. Opus 4.6 has been out for less than a month. If it was a big shift surely we'd see a massive difference over 4.5 which was november. I think this proves the point, you
620.
by maccard 8mo ago
> Have you tried it with something like OpenSpec? No. The parent comment said I needed a new model, which I've tried. Being told "just try something else aswell" kind of proves the point.
621.
by maccard 8mo ago
I’m not OP but every time I post a comment with this sentiment I get told “the latest models are what you need”. If every 3 months you are saying “it’s ready as long as you use the latest model”, then it wasn’t ready 3 months ago and it’s n
622.
by maccard 8mo ago
Really? I’ve noticed that the AI overview is full of glaring issues repeatedly. It’s akin to trusting the first Reddit post that is found by Google.
623.
by maccard 8mo ago
> if the return type is `Result<MyDataType, MyErrorType>`, the caller cannot access the `MyDataType` without using some code that acknowledges there might be an error (match, if let, unwrap etc.) I think you can make the same argum
624.
by maccard 8mo ago
I’ve got two machines for work - a desktop with an i9 and a laptop with an i7 and 32GB. The laptop is honestly a disgrace - I can’t believe it is sold as it is and marketed as a premium device. It’s “fine” for some light development but it
625.
by maccard 8mo ago
> The poor performer gets singled out, which is just fine. he's not a poor performer, he's just an asshole. And you can't fire someone for being an asshole > So instead of punishing everyone for some lying asshole'
626.
by maccard 8mo ago
> That sounds like the real problem was the lack of an employee handbook. That's my point - we didn't have one because we didn't need one. 30 people is still small enough that you can be on first name terms with every sing
627.
by maccard 8mo ago
Nope.
628.
by maccard 8mo ago
He did ruin it for everyone. Management called him up on the sick days. he responds by saying that there's no policy for sick days, and to show him in the handbook where it says he has a limited number of sick days, or that he needs to
629.
by maccard 8mo ago
A combo of management control and a very tiny number of people who abuse any freedom given to them, then blame you for not telling them they couldn’t do it, and then blame you for singling them out. As an anecdote - we had no sick leave pol
630.
by maccard 8mo ago
It’s been a while since I worked for a bigger company (not meta) but the problem there was you would have a team who was responsible for feature A and a team responsible for feature B, and if there was any weird interop between the two it j

More ›