andsmedeiros

So Ruby Central will still be running rubygems.org?

I am implementing a baremetal USB device stack in an embedded application and an having a really, really hard time. The device in question is a decoder for sportive chronometry and uses lots of DSP for detecting and measuring when vehicles pass through the finish line.

Depression is killing me. I'm losing this war.

There is no green meat. There is no ethical meat. There is no acceptable meat.

While we discuss this, Rio Grande do Sul, Brasil's southernmost state, has had more than 80% of its territory flooded; whole cities are completely destroyed. It is one of the most significant animal producer states in Brasil.

I don't think the quote suggests that a programmer would mentally design a whole system before writing any code. As programmers, we are used to thinking in problems as steps needing resolution and that's exactly the 90% there. When you're quickly prototyping to see what fits better as a solution to the problem you're facing, you must have already thought what are the requirements, what are the constraints, what would be a reasonable API given your use case. Poking around until you find a reasonable path forward means you have already defined which way is forwards.

This was very informative, thanks!

Sweet

I have been playing exclusively on Linux for about 2 years and haven't thought of going back to MS yet

The downside of targeted ads, besides the targeted thing, is the ads thing.

I've used many times for small programs and such, even though I don't use any wine program on a regular basis. However, I do play games on Proton all the time and everything mostly just works.

I was quite ready to hear some Qt rant

TDD can be valuable but sometimes hindering. I find myself often with an incomplete idea of what I want and, thus, no clear API to start testing. Writing a quick prototype -- sometimes on godbolt or replit -- and then writing tests and production code will actually yield me a better productivity.

I usually test all of the public API of something and only it. Exported functions, classes, constants and whatever should be tested and properly documented. If writing tests for the public surface is not enough, most likely the underlying code is poorly written, probably lacking proper abstractions to expose the adequate state associated with a determined behaviour (e.g.: a class that does too much).

In the programming realm specifically, following a trend can be foolish and, at the same time, as a bigger community usually means better support, documentation and maintenance, clever. It is bad, but if it was better, it could be worse.

Life can be very paradoxal at times.

It must have been such a beautiful city...

I just don't use out parameters and avoid bare references altogether, const lvalue and rvalue references express idiomatically whether a parameter is to be copied or moved. Structured binding makes it trivial to consume returned tuples, so I don't find this a big issue.

C++ is just too big nowadays to be fully useful, or even applicable to every environment. Specifically on exceptions, I wish there was a GCC flag to disable exceptions in the sense that any `throw` calls `std::terminate` and catch blocks are completely ignored.