13,233 karma · joined October 12, 2007
Twitter: http://twitter.com/mbuckbee
email: mike@expeditedsecurity.com
Pre personal computers, this was a viable career: taking notes in meetings, typing up and sending letters, dictation, filing, etc. functions that, for 99% of folks they just do themselves.
Despite the somewhat creepy title, I found it to be a very sincere look at personal communications.
- It's very hard to know what other people are going through so don't assume
- Be genuinely interested in other people, don't just wait for your turn to talk
1. So it's not so much "not providing power" for some political or philosophical reason but "not providing all the power they want."
2. The miner wants the equivalent of ~500,000 apartments worth of power...which is substantial.
3. The reason the miner wants this particular power from this particular provider is that it's cheap.
4. If the miner got all the power they wanted it would be enough to drive up local utility rates.
5. The local utility + government aren't keen on this as it's a pretty blatent resource extraction with no local jobs being created.
In 1912 (the last time we added more), the US population was ~90 million, and it's currently at around ~340 mil and we still have only 435 representatives.
1912: 1 rep per 20,000 people
2024: 1 rep per 780,000 people
This doesn't "solve" gerrymandering but it does blunt the effectiveness of it (among hopefully some other positive effects.)
My understanding is that the study has been fairly conclusive in proving that maintaining blood sugar levels as close to the normal range as possible has a positive impact on many of the previously thought "inevitable" side effects of diabetes (like losing your vision, losing feeling in your extremities, kidney failure, etc.).
He's justifiably proud of having helped in some small way improve the outcomes for lots of other folks.
- Google for creating a mention tracker I was distributing as a mac dashboard widget
- Netflix for creating a DVD barcode to Netflix queue ios app (they were trying to to antagonize their retail partners too much at the time apparently)
- Microsoft for abusing some of their early text to speech DLL's for a really crappy RSS to Audio "podcast" app (they were meant for server side telephony apps)
- LinkedIn + Salesforce for linking their data with a Chrome extension
- Hubspot for mentioning their Inbound conference and saying that my software worked with theirs
Thinking back now these are all quite old, I don't know if the companies have become more lenient or I've become more cautious.
It was explained to me like putting salt into a freshwater pond. It can take some but the salinity eventually reaches a point (boundary) where the fish die and you can't really "go back" and take out the salt.
Over time each was identified as something unique, given a more precise name and treatment methods and eventually nobody is diagnosed with "consumption" anymore.
It generally gets around 1000 users a day.
Over the years, it's gotten me consulting gigs and the occasional job offer (amidst other projects).
Today, it sends a decent chunk of the traffic and sign-ups to my startup, Wafris -> https://wafris.org
OP's asking for a strategy with these, and the advice I'd offer is to treat them like assets. You make these various side projects to learn something, take the extra 20% of time to package it up buy a domain, and spend $10 on a logo or something to make it a little more like a project and not just a repo.
If it's not something directly usable like this, take some screenshots and collect them into a gallery on a personal site.
You stack these assets over time (and like my example above), they pay off over years in all sorts of ways.
Here is a cross-section diagram of the canal showing the lakes:
https://www.marineinsight.com/wp-content/uploads/2018/09/pan...
User PII and especially sensitive data suddenly was viewed as "toxic" and that having it around was something that could only bring them hassle.
California's data privacy acts are similar (but much more narrowly focused).
Also, I always like to sum up what the intent of these acts typically are and what compliance means:
- Tell people what data you're going to collect and, what you do with it, who you share it with
- Keep their data reasonably secure
- Delete it if they ask
- Inline chat about code blocks
- Inline instructions on modifying/creating code
- Import of documentation to the local project for better suggestions and referencing
You highlight the code you're interested in and hit CMD+K to have it do modifications for you.
This kills the copy + paste of code from your editor to ChatGPT and back, which beyond being a pain also loses all the context of where the code is in your project and is also a step ahead of Co-Pilot which is more just super intelligent code completion.
In general, I've found a great deal of dev productivity improvements in using it as a coding assistant where I'm still orchestrating and guiding the work and using the AI assistance to very rapidly blow through boilerplate tasks, reformatting things, double checking if I'm doing something right, etc.