Beej Jorgensen @ beejjorgensen @lemmy.sdf.org

Instructor, author, developer. Creator of Beej's Guides.

---

Read more

Posts

5

Comments

381

Joined

2 yr. ago

Related: Internet Archive hosts zillions of abandoned games. Publishers are currently trying to sue it out of existence. They accept donations.

I'm sure it was possible, but I'm also sure my car doesn't do that.

My 25-year-old car is certainly not transmitting anything.

I just went in there to make a new account, and they want real name and salary before you can do much. (I work for a public university, so my salary is public record, but even so I just quit out. Too invasive.)

I always left it open-ended and that seemed to work. Part of the interview was seeing what they'd come up with. I'm pretty sure people always brought things they'd already written.

In the developer tools in the Network tab. FF sums it up at the bottom of the list when you reload (e.g. for this page "24 requests, 4.74 MB transferred"). Chrome must have something similar. Be sure to check "Disable cache" in the devtools.

My simple home page is 10 KB now. And you might not think that's such a big deal, but it has more content than Google's search page and that rings in at a couple MB IIRC. 😁

It never happened--since they knew in advance, they had time to whip up something cool if there wasn't anything else. It didn't have to be massive. I just wanted to see some clean non-trivial code and a clear understanding of how it worked. Fizzbuzz wouldn't have impressed. :)

One of my classmates years ago loved bash. They wrote a filesystem for their OS class in Bash. It was a really, really impressive and bad idea.

But how do you handle candidates who say something like "look, there's heaps of code that I'm proud of and would love to walk you through, but it's all work I've done for past companies and don't have access (or the legal right) to show you?"

It never once happened. They always knew in advance, so they could code something up if they felt like it.

I asked candidates to bring me some code they were proud of and teach me how it worked. Weeded out people really quickly and brought quality candidates to the top. On two separate occasions we hired devs with zero experience in the language or framework and they rocked it. Trythat with your coding interview, eh? 🙂

The double-edged sword of isolation.

On the one hand, poor communication between apps and waste of storage.

On the other, relative safety from malicious applications, or from otherwise-safe applications built on top of a thousand libraries none of which have been audited by the dev.

I don't know how it's going to go down, but I suspect something will come along to address these issues and snatch the market away from Flatpak.

Hadn't tried it before, but went through the tutorial. Seems like a good editor; only modal editors for me, you know? :) I'll probably stick with Vim for now, but it seems like something to watch.

No, they're inside my home directory, alas.

Sure smelled like a bubble to me. But I think like before, it'll come back around.

This is the fun way. I have a ton of configuration files in git and I symlink to them from various places with an install script. And zshrc has enough brains to determine the OS it's running under and the hostname. Between those two, I can have it do all the Right Things no matter what system it's on. So far, it deploys to my personal Mac, my work Mac, my personal Linux box, my SDF account, and my Android phone with tmux.

Basically I clone the repo into .local/share/beejsys and then run the install script and everything just works. And I don't typically have to rerun the install script after a pull.

mpv also works well from the command line.

The old C++ FAQ book was over 500 pages, and that was decades ago. Those were the "frequent" questions.

I drove deep into C, a much simpler language, and there's all kinds of wild stuff in there that most C devs don't know. Of course, it's not applicable to 99.9999% of C programming, so who practically cares, but to learn 100% of C++? I don't have that kind of time.

That said, it's totally possible to learn enough C++ that covers 99.9999% of its use cases.

Another approach to thinking about it is that draw() does two things. 1) it draws the line that's 1 shorter than itself, then 2) it draws itself.

The for loop happens after it draws the line that's 1 shorter than itself.

The author said they wanted maximum accessibility, so they didn't opt for a particular platform's voting system.