dangarbri3

The old internet is actually still around. There's just so much noise and Google isn't going to direct you to it.

Neocities is a platform that promotes those quirky personal homepages.

There are chat room/irc platforms like matrix and libera chat that still go on.

You could look into some git GUIs, I'm only aware of gitk and github's app. But I'd bet if you look around you could find a gui that abstracts "git" away from git.

How to get leverage

We may also associate you with information collected from devices other than those you use to log-in to the Platform.

Same here, books on specific technologies are useless to me because you can learn more from the official manuals and playing with it than from someone else's interpretation of it X versions ago.

The tech books I do get are more meta, books about programming in general or design in general, things that you can't just find in a manual.

Learn a new stack, doesn't matter how simple the project is, it's for you. Then slap the new stack on your resume and apply. You can honestly tell the recruiter about a project you did in the stack they're looking for and then interview with the team where you can also talk about your project you did with their stack and the work you've done in the past.

I recognize the problem, this is how I managed to go from embedded systems firmware to sys admin/web engineer.

So PlantUML

NFTs are digital, not physical. So you need to make sure you can associate the NFT with the product. An NFC tag isn't enough, because like others mentioned, you can move the tag to a different bag so it doesn't actually prove authenticity.

But NFTs are more collectibles, so arguably you could sell the bag WITH an NFT as a bonus (not as proof of authenticity) and I think people into NFTs would like it.

Or make sure the NFT metadata has something to associate it to the physical product so you can prove that it hasn't been tampered with.

I think valid points are bad about typescript being bad, like without a real debugger it's going to be hard to debug anything.

But I firmly disagree with how the article begins.

> In effect, we are shifting complexity from end-developers to library developers.

That is the whole point in creating a library. To hide complexity in a nice easy to use interface/API.

Counter story, when I was a senior I found I missed a freshman requirement. The teacher saw me in the class, I was fine with having the blow off class but the teacher recognized me as a CS student and said I shouldn't be there since I was a senior. Had me schedule and take the final for the class, I passed, and I was able to skip it for the semester.

Doesn't hurt to ask either.

The method that works best for me is from code complete. McConnell argues (correctly, IMO) that tests are a technique, and writing tests means more code to maintain and debug. Tests can be wrong, and if the test is wrong, the code will also be wrong. Thus, a bug is introduced. He advocates first making sure you have good software design, i.e. components are laid out, how they're going to interact with each other is well defined. So before writing any code at all, make sure you have a documented design that works conceptually.

Define the systems that make up your software, the classes that make up the systems, and then the functions they'll use to talk to each other. Once it works on paper, start coding. If the design is good, the code should be so brain dead simple to write that a monkey could write it.

I find doing this I do end up with long call stacks, because each module will do something, then pass the data on like an assembly line. In each step my functions are super short and I don't find it worth writing a test for 3 lines of code that I can tell is correct at a glance. For those few meaty functions that do more heavy logic, I will write tests for, though.

The problem is that no one food, including potatoes, has all the vitamins our bodies need. If you do this diet, make sure you're taking a multivitamins and supplements for the vitamins and minerals not present in potatoes