lazylester

The process is more important than the ingredients.

almost all 2-stroke engines have had plastic flapper valves and a plastic fuel pump for as long as I can remember.

Sounds like you are trying to tame your thoughts? It will not work, they just don't succumb to effort. Noticing them is all that is required and it's the only thing possible.

Instead of a how-to course, I suggest you look for Dharma talks on the practice of meditation. They can be very, very profound, there is a lot of material available. On just one site, the first one I looked at, spiritrock.org, there are over 100 talks for beginners.

A how-to app is doomed, which fact can be hard to grok. It's not like learning to drive or learning a programming language. A teacher or a retreat can be very helpful to get you past the initial missteps and misapprehensions.

phone calls and texts. It's not just metadata. You can switch to WhatsApp and Signal, but your whole Rolodex (remember them?) needs to switch too.

"...hard to imagine scenarios where [file-level compatibility] is useful" what am I missing? Surely dropping a more performant dbm into an existing project would be the application? No?

imho the vaunted readability of custom elements has long been available with haml, with added readability by virtue of the indentation rules replacing closing tags. Not sure why it didn't really gain much traction, maybe the pre-processing is problematic when there's no server-side framework like Rails?

beneath the fancy graphics there's zero explanation of how these are manufactured, how they're constructed, or the magnetic field patterns. No actual deployments or demonstrated applications, just graphics. It's a 3-person company that "expects to begin testing of this exciting new technology early in the 2nd quarter of 2023".

your rage suggests that you think ChatGPT is making value judgements about elegance or simplicity. You surely know where it picked up those concepts don't you?

"...but will constantly run in to situations where another gems code is using the method that just changed". I've worked with Rails for 20 years and haven't seen this. Have I just been really lucky? I'm sure your test suite showed the warnings about the Redis `exists()` change for many versions prior to its actually being changed, right?

Try idealist.org But mostly there's not enough $ in non-profits to pay a s/w dev. Another approach is to work hard, retire early, and then do the work pro-bono. I have been doing s/w for non-profits since I retired at 51 20 years ago.

The daily structure of work life allows one to avoid facing some questions that otherwise arise. Financial independence forces one to explore how one wishes to spend one's time when the work constraints are eliminated. This can be a very exciting, fruitful and rewarding endeavour. I highly recommend it.

I got a lot out of Jennifer Widom's "Introduction to Databases" MOOC from Stanford. Particularly the normalization concepts. (Don't take them too far, though, as they say "Normalize until it hurts, denormalize until it works"!)

Yes this is exactly what you need to do. And yes it takes some careful design to eliminate power supply noise.

NeuG has some low quality sources of entropy, and also provides analog input for the user to supply with whatever they wish. It does not address the design of a good white noise generator, unfortunately.

Is condensation a problem in a freezer? There is no moisture in the air b/c the temp is less than freezing, no?

Condensation happens when moist air hits a cool surface, how much power is your circuit consuming? You may not have a problem.

I have designed a number of telephony products (e.g. T1 repeaters) for use in outdoor environments, we never coated the circuit boards.

I too had poor experience with support and also weak documentation, but I pushed through it and I'm very happy with the product now that it's integrated with my app. They seem to practically 'own' the space and I have some confidence in the longevity of the product.

I have been writing software, pro-bono, for non-profits for over a decade now. I get most of my "work" through idealist.org, which is a trove of opportunities. You might have to monitor for a few months before you find just the right project for you. Be patient.

My most recent gig, however, was found through the United Nations volunteer program. I can't find the link atm but I'm sure it'll come up for you with a bit of Googling.

It has been incredibly rewarding, and you might be able to write off some of your computer, conference, books, internet and travel expenses.

I love this kind of work for many reasons, but from the developer's perspective it's rewarding because the client is always very grateful for what you are doing and there's never a deadline, so there's always time to do it right and not take shortcuts.

I have traveled to some very interesting places, albeit mostly (but not always) at my own expense, with this work. I am fortunate to be in a financial position that I can do it, and I can't recommend it highly enough.

What problems do you see with yubikey? I just finished deploying an app with FIDO 2FA using yubikey and it went pretty well. Had to restrict users to Chrome, though, but in my scenario this wasn't a problem. My biggest problem was adapting my (rspec/capybara) integration test suite. Do you know of issues that I may not yet have seen?

Typically the error messages that I include for my "this is where I left off" or "still to do" tests are like "page not yet implemented" or "haven't figured out the bug". No definitely don't delete failing tests! Make them pass.

Personally I use TDD (or more precisely BDD) for this purpose. If I leave the project overnight, or for a week or a month, I can come back to it, run the tests, and the failing and/or pending tests tell me what I was doing when I last worked on it.

So I always leave an in-process development project with failing tests. If they're all green, I don't know what to do next!

seems to me the risk of having the backdoor stolen is an overstated vulnerability. Isn't it the same risk as having the iphone source code stolen? Hasn't happened yet has it? If the source code were stolen, someone else could engineer a backdoor. I don't think the overall security risk increases by the existence of a backdoor on a single phone. Amiwrong? That said, I'm happy that Apple is pushing back, but let's be clear about the technical facts.

Israel has as much as it needs of Syria... it occupies the Golan Heights. You can see Damascus from there on a clear day.

OK, let's try ternary. Oh, why not go to quaternary, or quinary (I mighta made that word up), and so on. Before you know it, we're back to analog!

well I for one am proud to have been an LSD user. It was amazing, but after about half a dozen trips I started to see "the dark side" and stopped doing it. I have no regrets, it's friggin awesome.

I switched to vim after seeing the astonishing speed possible in Gary Bernhardt's ruby screencasts. My vim chops just get better all the time, the depth and breadth seem limitless. It always gets faster and easier.

I just can't reconcile that a man of science (Brantly) credits magic ("God") for his recovery! Don't you get cognitive dissonance dude?

How about just re-using, by writing on the back, the reams of paper that is printed on one side, that your printer spits out, and much of which is discarded. Reduce, Reuse, Recycle.

DS1 clocks are not required to be synchronized, they are interleaved into DS3 with lossless bit-stuffing.

When there is a loss of frame sync, signalling channels are inhibited. There's no transient synchronization recovery condition where channels are misaligned, the frame sync must be recovered first, and when it's recovered, all channels are correctly aligned. I used to design this equipment. I'm afraid this explanation is not correct.

I'm pretty sure the bytes are sequentially addressed, but the program (memory contents) may contain branching, conditionals etc to load the next address. Just like assembly language. If I recall correctly, the microprocessor logic on these missions was RTL (resistor-transistor-logic) which was the predecessor of TTL.

idiomatic shmidiomatic, give me faster always!

In the video, the author moves a block of code by: 1. going to the start of the code block 2. changing mode to visual 3. moving to the end of the block 4. deleting the block 5. moving to the insertion point 6. inserting the delete buffer

I'd like to suggest that using absolute line numbers shortens this considerably. For example

:43,48m63

removes lines 43 to 48 and inserts them after line 63 regardless of the current cursor position (no need to move cursor).

Not saying relative line numbers are bad, just, there's a quicker way, at least for the demo use case.