One simple way is it has superseded google/SO on my priority list for some reference lookups on topics I need to dabble in for work. (Like “Django custom function generate uuid”) Practically speaking, I’ve found this (most of the time) reduces the cognitive overhead of context switching. Less clicking, sifting, looking for recent answers, etc.
For slightly more complex reference on topics I’m dabbling in (Like “what’s the right way to use React hooks for this component”) the benefit of leveraging ChatGPT increases. In many cases you’re able to skip the step of generalizing your problem and you can address your needs from the “inside out”.
Inside out example: starting at some API method names and sample code for some libraries, rather than starting with a list of libraries or worse not knowing what kind of library you need yet.
Finally the place where it has had the most impact for me is as a force multiplier on efforts outside of my comfort zone as an engineer. If I have a side project idea, or if I’m trying to be ambitious in design at work, I can often discuss approaches at length with ChatGPT and walk away with several ideas, or even conclusions about how best to proceed without exhausting myself.
Tangential but may be of interest: a cool book (compilation?) that somewhat addresses this topic is ‘Ideas That Created the Future’ edited by Harry R. Lewis [0].
Is this a summary or the entire text? I think I saw messaging from Coinbase in anticipation of this proposal earlier this week. [1]
Not a lawyer but the definitions and language seem a little shallow to me considering how lofty the proposal of a new regulatory agency is.
Wouldn’t one expect a higher level of detail, supporting evidence, citations or legal precedent from consultations with “30+ crypto firms, 25+ members of congress and/or staff, 4 major law firms, and 3 trade groups”?
What is the worst case scenario that the author imagines happening to Rust due to Amazon’s influence (or anyone’s influence)?
This is unfamiliar to me - are there notable stories of what poor steering has done to a programming language? What were the consequences?
I can parse the basic grievances here on power dynamics, losing control of something you helped build…that’s familiar enough…but I’m having trouble understanding the gravity of what the author is passionate about preventing.
(In case it isn’t obvious I’ve never been a long term contributor to an open source project - genuinely curious about the context here)
This looks cool! I spend half the day in terraform and AWS and I’m looking forward to trying this out later today.
Regardless of how that goes, it’s really nice to see a project that addresses this specific area. Way to go!
The AWS console is (at least for the popular services and API endpoints) super effective.
That said, when you’re deploying a project that has components that span almost a dozen services in AWS that can quickly become a dozen tabs just to assess the state of the project. Not very fun - looking forward to seeing how this handles that.
So there actually is a very quiet functionality hiding in MacOS Notes.app I noticed recently.
If you take any screenshot to clipboard that includes some text, then paste it into Notes, it will silently name the resulting image file using the text pictured.
Not terribly useful but I did find it helpful once while taking screenshots for documentation.
In the past I’ve felt the opposite of your sentiment.
I’ve found my email to be unwieldy. I’ve felt like I have to apply constant hygiene and maintenance to keep it from becoming useless.
Checking out on an e-commerce site, trying out a new tool, registering a free trial...these are things I guess I do frequently enough that it seems to doom me to sort and sift through noise.
I know the common solutions are a good set of filtering rules or separate emails/aliases. I lean toward the latter and it’a definitely helped but I still find it all a bit of a pain and time sink.
That said, you make a nice case for it and I can definitely identify with some of the ‘zen’ of email you’re describing.
I feel like I’ve tried every email client out there, but is there some solution I haven’t thought of of where I get a friendly GUI but can configure mail filtering in code (i.e something I can keep in git) rather than clicking around?
I’ve toyed with ideas of bundling by sender - or quietly placing new senders into their own ‘message requests’ type bin for me to approve or deny.
Or some kind of intelligence for identifying, for example, a receipt or confirmation email (which I want indexed) vs a promotional email from the same vendor (which I do not).
For slightly more complex reference on topics I’m dabbling in (Like “what’s the right way to use React hooks for this component”) the benefit of leveraging ChatGPT increases. In many cases you’re able to skip the step of generalizing your problem and you can address your needs from the “inside out”.
Inside out example: starting at some API method names and sample code for some libraries, rather than starting with a list of libraries or worse not knowing what kind of library you need yet.
Finally the place where it has had the most impact for me is as a force multiplier on efforts outside of my comfort zone as an engineer. If I have a side project idea, or if I’m trying to be ambitious in design at work, I can often discuss approaches at length with ChatGPT and walk away with several ideas, or even conclusions about how best to proceed without exhausting myself.