home depots site is seriously one of the worst. Mobile phone that is from this year, on good wifi, and it takes many seconds to load any page, HOW!?!?
326 karma · joined July 23, 2023
home depots site is seriously one of the worst. Mobile phone that is from this year, on good wifi, and it takes many seconds to load any page, HOW!?!?
Also ai helped me build an offgrid setup for said garage because the garage has no power. Helped me size things out, gave me diagrams, etc. Also has already provided me with a way to setup an automatic generator startup when the battery is low. I havent set that up yet, but its in the pipeline.
I started and then abandoned a really deep circuit simulator, which was going to be able to emulate full actions and code eventually.
aaaand lastly, ive spent the last 2 months in the evenings with ai building a complex rts game in godot, its almost 1.0 ready. Sadly the ai im using has been really struggling to turn out quality 3d models, so thats probably going to be on me, which will delay significantly.
I frequently do the same, but not everyday; only when i think its something actually useful/helpful beyond the everyday crap. Most recently, we have had a huge push to use ai (just like everywhere else), ive been getting pretty creative with it, and at this point have a well polished setup that i can give a shitty sentence on a problem, not only does it understand the task, but theres a full ticket->branch->work->pr review->ready comment flow that it uses. My team also uses ai but they havent quite wrapped their head on ways to really work with it. I have built and shared a number of helpful things with the team to try and help them grow. One such thing was a doc i had my ai instance write, based on how ive been using my setup. This alone has started to get the rest of the team up to where i am.
My team doesnt share the same types of things i do, but they still share helpful things.
Call it what you will; I think if youre not helping your team grow by providing insights and helpful things, then youre not the kind of person i want to work with.
Ive concluded that unless the person is 100% passionate about openapi, the spec is a mess, and compatibility is a joke contained in an afterthought
Was a devops engineer, whole app team (who only ever wrote nodejs) got fed up with pacemaker/corosync. "we are going to write our own" they said, and proceeded to try to whip out nodejs for it, i laughed and laughed, and then told them fuck no, dont do it.
When all you know is a hammer...
Denvers original airport was built in the "middle of no where", for noise reasons. Continue on for 30 years and lots of housing built up around it. People start complaining about noise. City decides to move the airport. Moves it 30 miles away, in the middle of no where (now DIA). Yep, you guessed it. People start building close to the airport, and then complain about the noise. I fully expect it to move again in 15-20 years
with this ive been able to, with some minor adjustments and "oh that would be a good feature" additons, oneshot a flask app at work with everything ready for oidc, ldap lookups, bunch of other stuff - from a single 3 sentence paragraph.
With some rules in its configuration (more markdown its written by it for it, at my guidance of "always do x and remember this for all sessions"), it has a whole flow and i barely have to feed it anything to get out useful results quickly.
I will say though that the ai operates however the user says, so if you dont take steps to ensure survival of info at the start of using ai (or even from now on as a fresh session), youll get mixed results, but you can shape it and mold it into amazing flows that do remember
I have a base docker container and a shell script that "customizes" each instance for where its running (making sure user id matches for permissions, etc). Runs as non root in container, has minimal privileges, and only access to the repo or dir where the shell script was called
You definitely let the ai shoot your legs off all on your own.
"That takes up so much space!"
Worked until reboot. And thats the start of my dive into IT
Had the original plan been simply "extend address space" instead of "extend address space and while we are at it revamp and rewrite every part of the whole scheme including assignment, discovery, and everything else we see wrong with ipv4"; we would be in a much better place.
Adding extra address bytes would of course require new changes across the internet, but that change would be easier to swallow compared to having to rip and replace large swaths of processes to make ipv6 work because of all of the other changes that came with ipv6.
Also, the stupid idea of turning addresses to hex as the default, and more specifically the dumb :: shortening methods really made it confusing for everyone and didnt help at all in the efforts.