... obviously then a floating canal train, would beat both of them. The best of both worlds!
466 karma · joined January 14, 2022
One of them is CO2.
In my heavily forested area it reads 79 PPBV. I'm confused because I've always thought we're in the 300-400 PPM for CO2. But if I got this right, 79 PPBV converted to ppm is .079ppm CO2... No? I was expecting a higher number. Something wrong about the V here in the number, volumetric meter I am assuming?
if you click around in the metro areas around the country it does read what I think is 200-400ppbv as expected.
Maybe somebody here can explain: What's the difference between ppbv and ppm?
https://www.windy.com/-Show---add-more-layers/overlays?cosc,...
Soon as I saw this headline, I was completely shocked and dropped everything to check my usage. Luckily I had 'cdk destroy' the big projects, but I had dozens and dozens of lambda and S3 buckets it failed to clean up. I spent probably 1 hour clicking through the web interface deleting them in fear of what happen to OP
I think I'll just stick to LocalStack and VPS.... actually my datacenter friend said I could bring up my deep learning station to this DC might just abandon AWS idea.
To get over the procrastination I would set up a Pomodoro timer and set it to 20 minutes, and just write something, any code. I made it a joke to write the crappiest code I could, to make it fun, as long as it works. Inline copy pasta, etc. Later on it turned into the goal of the most understandable code, over everything. I would never have done this out of the university, but this was 10 year later. Before I would come up with a "plan" or "design", but at that point, I would just hack something up.
What I found was with starting with an excellent blank CI/CD project, and a good BDD end-to-end testing strategy, I could write "dirty code first" to "just get it done" ... then once I got into a OODA loop, refactor it into amazing products and services while having fun. This reduced my cognitive load and emotional overhead. Coding is actually 5% of the work, the rest is QA, requirements gathering, meetings, UX/UI designs, and overhead.
So far I can't rely on copilot because at any time for any reason they can cut off access or change the functionality. Also, the waitlist.
A requirement of the GPL is that they are supposed to release the model but so far I have been unable to find it. There's some kind of "debate" about this but the GPL is absolutely clear in this regard. I'm confused.
copilot is awesome for (lazy) senior devs who want the no-code experience, meaning not having to look up easily forgettable things. How many times have you've forgotten RegEx or how to check for a file exists in bash? Simple put "#Check if file 'filename.txt' exists if not error" and it will complete the bash line. Convert dates in javascript without going to the mdn docs, etc.
It's almost exactly what the author is describing to want!
BUT... when I lived on the grid I paid $.13/kwh. At 77kwh per gallon that puts us at $10.01/gallon. It is unknown if this is just syn gas or ethanol, or what the BTU of that gallon is. And this definitely isn't diesel, which would have the biggest impact. I know when my friend did bitcoin mining he was able to get $.03kwh so... let's use that 77 * .03 = $2.31. So between $10 and $3 a gallon is actually possible.
With gas over $5 or $6 (the company is in Santa Cruz? Their gas is probably $7 or $8 at this moment, I bet) ... this will work
The other issues are... United States uses 30TW of oil a day (convert barrels of oil to BTU and convert BTU to watt hours... to convert oil used per day in watts to speak of)... and 10TW of electricity a day.
To replace 'fossil' fuels we'd need ...70TW of electricity after inefficiency conversion.
There isn't enough copper, nickle, and silver to make all those solar panels. There isn't enough public support or political capital to build nuclear reactors either. This is another flaw.
Another commentor suggested, just replacing Russian's oil at 4 million barrels a day. That's possible. And it makes it exciting.
* Better frameworks. If a framework adds complexity, it needs to enhance the feature set and developer experience by 2x. Otherwise, I just stick with the basics. Example: I was working on a react codebase with insane level of hooks, contexts, 7 layers of abstraction. Solution: Axios/Fetch right next to the form, entire backend functions in the controller: no f's given.
* Business requirements first: I hack off 90% of Agile methodology and just do what makes sense. Which is a balance of acceptance criteria and user stories, or contract driven development to pull the features into production and deliver.
* Thursday and Fridays I don't work, and if it do, it's on something completely new or exciting. Last week I played with DallE as an API. Unfortunately this means less pay.
* In the winter if its sunny out, I leave around 2pm. And come back and work 7pm-10pm.
* One meeting a day, or every other day. And Monday's meeting I come in fresh and excited, cite what I am grateful for, and talk about how incredible everyone's effort is. It can sound cheesey but it works for me.
Last burn out was right before the pandemic. I took a position at a startup that told me they were light on meetings, but I ended up spending all of my time in meetings and getting absolutely nothing done. So I left, and took a big break. I forgot a lot of things but realized what I forgot were skills didn't matter. Attitude matters over skill. I am not interested at all in React 18 and instead focusing on Vanilla JS, HTML5, just regular CSS, and just SQL. Day in day out skills. Stuff that won't change in 10 years. If I forget something like a new feature in React 18, then my mind is telling me it is useless in the long term.