[ my public key: https://keybase.io/stevewebb; my proof: https://keybase.io/stevewebb/sigs/j4kWJm1J_dc4RoE-7faulywvZtSrOfjkMQ1X2M1ompc ]
- scumolaclosed on mondays. :(
- mosh is awesome for ssh over iffy connections
- Things like "What is today's date" used to be enough (would usually return the date that the model was trained).
I recently did things like current events, but LLMs that can search the internet can do those now. i.e. Is the pope alive or dead?
Nowadays, multi-step reasoning is the key, but the Chinese LLM (I forget the name of it) can do that pretty well. Multi-step reasoning is much better at doing algebra or simple math, so questions like "what is bigger, 5.11 or 5.5?"
- I don't like that I can't connect to a RHEL 8 machine (that doesn't have a subscription enabled yet) without buying the Pro version of XPipe ($50). Definitely not in the open-source mindset.
- syncthing blows. Don't trust your data to it. Tons of posts on the forums about "out of sync" and no real answers other than "delete the database and start over". I've given syncthing a try over and over again for > 10 years and every time it fails to sync.
Use rsync.
- My concept for a modular shelter: http://badcheese.com/blog/2024-02-02-ideas-for-modular-homel...
- Take long lunches and get something done around the house. You're working at home. Might as well make it worth while. Do the dishes. Do the laundry. Wash your car. It doesn't have to be about work 100% of the time. If/when you do this, block some time off in your calendar for it so nobody is trying to contact you during this time.
- I just bought a 5 year old rugged Dell laptop on eBay for $50. Why would I pay a premium price for the top of the line laptop nowadays unless I was a game developer or my work is buying me a new laptop?
- This is just a map/reduce problem. Use Hadoop. It's Java, isn't it?
- 30.5 - the Internet went commercial in the summer of '94
- Articles are shared so quickly nowadays, the 'making it public when they get enough tips' might not happen fast enough and it'd be the same experience for most people...
- Nothing is stopping anyone from compiling C or C++ code into a single static binary too. This argument is bull$%!#.
- Nice! Is the kiwi API documented somewhere or did you just reverse-engineer it from the mobile app?
- I have a 1050ti and I can play it on low graphics settings at 1080 with no depth of field. I've gotten to about city stage #5 or so and I feel that it's playable. It's not pretty but good enough to get a feel for the game and learn about the new stuff.
- Agreed. The article mentioned duckdb and I'm her to thumbs-up the use of DuckDB wholeheartedly. If you like the world of public CSV files as data sources that you can query or cross-query, duckdb is the tool for you. Just follow the demo on the duckdb website and you'll be wow'd for sure.
- Fire Spez. Pay the people making the good apps to actually maintain their apps and keep up with the site's improvements, so there are multiple good apps, not just one crappy one. If they need money, there are already ads on reddit, charge more for the ads!
Don't fuck over the user base! Your users are what makes a site like reddit good! Don't they know that? Trim the fat (middle-management usually). Get out of the cloud if you're hosting servers in the cloud, move things on-prem. The cloud is great for flexibility, but for cost-savings, on-prem will always win. Whoever is the upper-management that approved the whole "charge for API use" - fire that guy too.
(rant) Too many websites have had upper-management take over and immediately change things that bring the site to its knees. This happens time and time again with new management. They think that they can bring some new life and revenue into the site and in the process, they cripple the product. It happened to evernote, dropbox, tons of great, cheap/free services that "couldn't support the freemium model anymore" so they cut cheap/free access to the product and people just went somewhere else. That's exactly what's happening now. (/rant)
- I'm 55. I plan on working until 70 (that'll probably be the minimum retirement age for full social security by then anyway). In January of 2038, the year I retire, the unixtime bug will show up for anything running a 32-bit OS and I'll charge a shitload of cash to consult to fix the bug for my last few months (from Jan (when the bug happens) until May (my 70th birthday)).
My house is paid off (bought in 1999, paid extra each month, just paid it off a couple of years ago (30-year mortgage paid off in 23 years)) and both of my kids will be finished with college in the summer of 2030, so that gives me around 8 years to save up. I'm not putting any faith in my 401k or any investments. If they pan out, then cool, but having cash-in-hand when I retire is much more comforting.
After retirement, I plan on staying un-injured and not falling for any money-stealing scams for as long as possible. I'll write software when I feel like it. I'll experiment with new tech if and when it's cool enough to pry myself away from chatting up my fellow retirees and drinking excessively.
- Maybe the acquisition will change the nummber of devices to > 2??
- I've used AWS for 12+ years. In the old days, we had one jumbo account that we separated by tags for projects and billing. It was a pain.
Then about 5 years ago, AWS suggested that we use the multi-account strategy. I changed jobs and decided to go with Control Tower, AWS Orgs and the multi-account strategy. I spent more time writing automation to supplement and write terraform and python code to build supporting infrastructure to tie accounts together, enable the proper services and networking in all accounts. The automation for build a new account grew and grew and became a behemoth. There's no API for Control Tower and the process of setting up a new account with MFA enabled and all of the bells and whistles enabled is such a pain in the ass that I consider the AWS multi-account strategy not worth it AT ALL anymore I don't care how much it reduces the "blast zone" it's a monumentally stupid idea.
You should try to put all of your eggs into one basket and manage access to your resources inside of IAM instead. Use tags smartly and you'll thank me in the long run.
- Switch to AWS. Store stuff in S3, use S3 select (SQL for querying data in S3). Write some lambda stuff for your "app" side of the web site. Your costs will be next to nothing.