65 karma · joined December 31, 2012
I made a ruby script that can take a graphic and scale it to whatever size, then it uses a closest color match to substitute colors for the _very_ limited Pico* palette and applies dithering to make it look attractive. I like Stenberg the most, but have played with Atkinson and am still feeling around a bit.
My solution, after looking into every off-the-shelf option, was to take an esp32 running esp32home + Home Assistant and hot wire it to buttons and status LEDs on a remote + base unit and stick it on the shelf in the garage. It's not pretty, but it works reliably.
There was a form of contactless magstripe (MSD) that was not encrypted and has been phased out of usage as of like, late 2019 via card update bulletins.
In the US, the way we do tip on receipt is a lot more natural if you're asking for a signature. Without a signature, you're just handing someone a tip option, which is awkward with our current way of doing things.
Some merchants opt to keep signature enabled because it gives them a fuzzy feeling and it's a point of closure to a transaction.
[1]: https://wallethub.com/credit-cards/chip-and-pin/ I discussed each of the cards noted here with the issuers, not one is actually chip+pin credit.
One email address... And i use one password for audble, one for amazon, one for aws, and one for amazon affiliate. If I password reset on any one of those services, my accounts are all bricks. I've made that mistake once and had to frantically call audible support & climb through the support chains until someone could basically undo my password change.
During the process, they offered to try and deduplicate my accounts, but I think we're going to need a team of senior-level DBAs to sort this shit out.
Some of their example code: https://github.com/VisaDeveloperProgram/SampleCode/blob/mast...
Docs are incoherent in just so many ways - and their quick start drops you right into like a 9 page guide for generating two-way ssl docs. Not exactly a quick dev onboarding path.
Request docs list attributes as required that aren't in their examples or runnable sidebar thing (the only cool part). Returns an error body with no error messages, codes, or info. You use some "correlation-id" (called "correlationId" in other places) to apparently get your error messages for a failed request.
Final rating: 1/7, would not play with again.
In High School, I really enjoyed shop class... after graduation, I bought random small tools and handled some household work, but always had some mental block about going out and buying wood and big tools to build the things I really wanted to tackle. The first project I wanted to take on was to build a replica of the picnic table my grandfather built about 90 years ago. I remember sitting with him at that table many afternoons, planning projects, talking about cars, life, etc. So, this table means a lot to me and even though I've taken care of it, the years have caught up and it is rotting away.
I built a Sketchup model of the table in its exact form, then I made a copy and started making minor upgrades (I think he'd approve). Here's the original table along with one of the benches, along with what the updated version is going to look like: http://cl.ly/image/2a2T0S1W280r http://cl.ly/image/1j2q3P2d3V2X
There _is_ a certain process and inherent knowledge that people who shop for things like wood, tools, supplies, etc., just inherently know that seem like huge hurdles for nerds like us. It's "just wood" just like it's "just typing" for us. When we're rude to a n00b, think about what "old timer" thinks of you going into his parts store or lumber yard in your khakis asking about stuff you don't know about. MOST of them are encouraging and want to share their knowledge, but it's really up to us as newbies to take initiative and learn how things work.
I had an opportunity last month to buy some shop tools (table, radial arm, band saw, sanding equipment), so I decided to finally give it a real shot.
First, I got the equipment set up and watched dozens of youtube videos about each piece of equipment - from keeping them clean and working well to calibrating every possible alignment & went to work making sure they were all perfect.
Next, I bought a set of precision rulers, protractors, etc., and made some practice cuts on scrap wood I had in the house/garage/etc.
Finally, it was time to buy wood. I must have watched 25 youtube videos about not just buying wood, but learning about the various cuts and ratings of wood. All very interesting, and I felt like I could at least identify a good bit of lumber from the bad, and it helped to catch up on some of the terminology & etiquette of the lumberyard. To make a long part of the story short - if you walk into a Lowes or any real lumber yard wearing shop-looking clothes and are carrying a notebook & pen, nobody's going to bother you. You can spend all the time you want looking over the selection, noting prices, etc. Seriously, this was a major milestone for me to realize. I ALWAYS feel rushed when I'm in a store... there was something different and nice about taking time to pick through and find the wood I thought was going to be great. Of course, if you do this, don't make a mess and put everything back the way you found it.
Another hurdle was that I didn't think (at first) I could fit lumber in my car. I drive a crossover and discovered that the passenger seat folds flat, leaving plenty of room for 8' lumber. I can fit 10' in diagonally if I let it touch the dash. You might be surprised what you can fit in your car when you fold the seats down & give it a measure.
Anyway, with the wood all loaded up, I got home and started planning my cuts. I printed the sketchup model and started documenting everything - making notes of how I can get the most of each board, figuring out which order I should tackle them in, how I'd arrange the mounting bits, etc. Honestly, I probably spent 5 minutes planning for every 30 seconds of cutting. I don't know if that's normal, but it was actually kindof exciting to make some cuts, get out the protractor, and find that I was dead on with what the model said I should be.
I wrote WAY more than I expected. This particular post and topic really hit me though. Here are some more pics of the work - I have most of the table completed and ready for assembly. The benches are finished & ready to be sealed, though. They came out pretty well, especially for my first project.
http://cl.ly/image/3z2C2F072M1K http://cl.ly/image/0Q06180Q2y3q http://cl.ly/image/2U3f3q1n2Y1W http://cl.ly/image/1Y3d0l123L35 http://cl.ly/image/1X410N281K11 http://cl.ly/image/3g2k3j3f3E1P
I hope Sony actually goes through with this. I currently use an ipad mini & notesplus with a jot pro - it's a good setup and works well, but I still find myself reaching for legal pads half the time.
We've found that going this direction leads to cleaner models, faster execution, and more decoupling of the entire front end from the entire back-end. We can query & build our data delivery however we need and feed it to the presenter as fast dumb objects (typically as Hamsterdam structs).
edit: removed redundantish wordery.