A revised book of computer terms from 1988. That was just a couple years before I became interested in computers. It's really fascinating to read through now.

How can I put it in a way CS grads can understand? If we were to apply time complexity to software development as an algorithm, coding would disappear as a factor, and you'd be left with a Big O that's all about batch size and feedback loops.

I think it's snowing

Prediction: Companies will be hiring a lot more testers

Meanwhile all these companies are bragging about layoffs because they've "become more efficient with AI". Like, dawg, you can't even keep your website online. Major outages used to fuel "omg it's a Russian cyberattack" type conspiracy theories, now it just become a normal Tuesday. 2/2

A tests intent should be extremely obvious just reading the test. I'd argue this is more important to get right than the implementation.

Stating what might be obvious but writing a test is the act of codifying your understanding of the problem and desired outcome. The solution isn't really involved here. Even with unit tests the test isn't (shouldn't be) concerned how the sausage is made.

I don't think using the image of something broken to show a successful test is sending the right message. 😅

Stating what might be obvious but writing a test is the act of codifying your understanding of the problem and desired outcome. The solution isn't really involved here. Even with unit tests the test isn't (shouldn't be) concerned how the sausage is made.

This is still very much a WIP but I'm interested in hearing thoughts or questions on the format itself (not the clients or tooling).

This is a great video on the nature of development, finances driving things, and topic of placing blame.

A tests intent should be extremely obvious just reading the test. I'd argue this is more important to get right than the implementation.

I (legitimately) love being able to say "I don't know" or to be wrong. Learning something new is far more interesting to me than being right.

Don't judge a developer by the implementation code they write. Judge them on what their tests (or lack of) look like 😭

On an unrelated note I keep seeing this idea that Rust doesn't let you introduce bugs or somehow prevents you from building the wrong thing...

It's legitimately terrifying that folks still can't tell the difference between building something correctly versus building the right thing. Those are VERY different things.

Consider the possibility that communicating is the work, and coding is the interruption.

Gods the Aussie social media ban breaks my heart as a person on the neurodivergence spectrum. Because as a teenager I can tell you that I got along with damn near no one at school and got bullied a lot. My friends were all on the internet. In forums. On IRC. That’s where my people were.

The bug you found that gets fixed in the code, isn’t the root cause of the bug. It’s the choices, decisions, assumptions, processes (or lack thereof), that caused the bug in the first place.

One of the many reasons AI can't produce good writing is it can't hate its own writing. It can't think to itself "Maybe I'm illiterate" during the writing process. And that's essential

Fuck *anybody* who formula-shames.

Prediction: Companies will be hiring a lot more testers

Someone asked at work if a flaky test is worse than no test at all. Yes, it is worse. Not having a test is a lack of information. A flaky test gives you unreliable information. Every time the test passes or fails, it could be a lie.

Someone asked at work if a flaky test is worse than no test at all. Yes, it is worse. Not having a test is a lack of information. A flaky test gives you unreliable information. Every time the test passes or fails, it could be a lie.

Enjoy using Postman? Insomnia? This isn't a direct replacement for those but rather a file format for encoding individual requests that I've been writing tooling for. Please check it out and let me know what it's missing for you (as a format, not as a individual tool).

How I Learned to Stop Worrying and Love the Autoformatter

It's hard to be consistent at writing long form content when you have my kind of #adhd. Even when I get excited and motivated to write something, it's still so hard to site down and focus on it and so easy to get distracted.

💯 Yes to all of this!

Much like March Of The Pigs, the extended version of this the superior version.

stop trying to show me my year in review. what i did the past year is none of my business.

The web client in action 🎉 This request just hit's the app's API to list the request files found in the current directory. Hopefully it's clear what this app does just from the video 😅

Rust's learning curve pays off when the time it takes to fix a compiler bug becomes less than the time it takes to identify, locate, and fix a runtime bug in another language. Obviously this depends on the bug.

I tend to interate on an idea by implementing it multiple times. - github.com/testingrequi... - github.com/testingrequi... - github.com/testingrequi... You can see how it starts with the seed of an idea.

It's amazing how many lower follower accounts post gold yet get little to no likes while big accounts post junk and it takes off. That was one of my biggest complaints about the bird site.

Part of letting yourself learn is not letting people who are being intimidating govern what resources you seek out and what questions you ask Who cares of Waldo thinks you're not very smart because you ask "basic" q's? What matters is whether you understand the what the Clebsch-Gordon coeffs are

It's never been easier to quietly and carefully teach yourself material that you never learned. Youtube is full of lectures and the internet is full of notes. PLEASE DO NOT MAKE CHATGPT YOUR TEACHER Pick human teachers & when I say learn, I mean to do things yourself, not to prompt wolfram alpha

IMPORTANTLY: Be honest with yourself about what you don't understand. Doesn't matter why you don't know. Could be something that was really unfair/not your fault. Racism in the classroom, sexist study groups, whatever. Go to therapy to deal with it! Don't let your pain be a barrier to your learning.

If you feel like you are behind or underprepared, the only way out is through: spend the time on the things you don't know, figure out who will answer your "stupid" questions. Then ask them, even if it's anonymously online Learn to do your own calculations, even when it's tempting to lean on others

I got a lot done on the web client I'm building for my request language. - Displays the templates request that was sent - Displays the diff in responses if an expected response is defined (no color yet) - Wired context data from the client in to the compiler and runtime interpreter

I love when I go to implement something and I had already done most of the work for it in the past! So these request files are read only in every client other than the in-editor client for VS Code. That's because "comment text" wasn't been stored in the AST, or so I thought!

Enjoy using Postman? Insomnia? This isn't a direct replacement for those but rather a file format for encoding individual requests that I've been writing tooling for. Please check it out and let me know what it's missing for you (as a format, not as a individual tool).

It’s a tough job market, but given that I recently transitioned roles after more than 4 years it was on my mind. New post for the lead dev is live! leaddev.com/career-devel...

I forgot to post this last week

If you generate tests, they will simply agree with the implementation already there. Not only is this useless but it's actively harmful to code bases. Can you imagine in the implementation was also generated? It's just the language modal agreeing with itself.

This is actually quite brilliant, up to and including the final sentence 🔥