[bayindirh]

Actually, Plato is not wrong. I'm a big pen and paper user, and write everything down. While it allows me to turn back six months, I can't turn two weeks back without my notebook in some cases.

Brain has a strange ability to understand that information is stored elsewhere. Write it, and you forget it. Take photos in a concert, and memories become fainter. Talk about something important, you start to forget it part by part.

AI is something way bigger. It's a dumb system which mimics us without the essence of the human or personal style, yet does mundane tasks without questioning. So you trade your own fine tuned, honed, polished ability to some GPUs which runs a software which is tuned for the masses. Like trading your beaten tungsten tool with a shiny iron one. Looks nice but way inferior. The ability to do these mundane tasks is the foundation for not doing the same tasks in a mundane way, or doing more complex tasks built on these mundane tasks. You rig your own foundations with explosives. Not wise.

I'd not do that. I don't use any AI systems in any of my tools.

[fl0ki]

> Take photos in a concert, and memories become fainter.

I don't know about short- or medium-term, but long-term the photos can remain objective anchors for memories that reduce the memory drift for everything all around them. When you have a photo of an event, even if you didn't take it yourself, it locks in many facts that individually weren't important enough to memorize but do constrain other possible facts and thus keep memory more accurate.

When I got into photography I took high-effort high-quality photos everywhere I went. There are so many minor events I wouldn't remember at all if not for the photos, and even for events I do remember, I likely would have forgotten that certain people even attended.

Long term, I can be completely objective about the times, places, people, conditions, etc. of a great many events in my life, and every time I refresh and reinforce memories it's anchored in those objective details.

There's a less objective angle to this that I still acknowledge and enjoy. When you take a good photo of a good moment, and look back on that as representative of the event, it has a way of making the entire event look that positive. You scroll back through a timeline of photos like this, it can make entire years of your life look as good as you want them to.

That's part of why I think there's a big difference between scrolling a backup of all your phone photos vs hand-curating albums (regardless of the device that took them). When you choose what you'll see in future you influence how you're going to feel about it, and that's an under-appreciated mechanism for investing in your future headspace.

[bayindirh]

Note: I'll take short snips from your quotes to keep this comment tidy.

> don't know about short- or medium-term, but long-term the photos can...

You're absolutely right, however I said concerts for a special reason.

> When I got into photography I took high-effort high-quality photos everywhere I went...

This is also what I do. When walking around in a city, or taking photos in a vacation, etc. You can do this. Because when taking photos in a relatively serene environment (when compared to a concert, esp. an open air, festival one), you can internalize whole event before taking that photo, so that photo becomes an anchor for that event. In a concert, everything is so fast. Trying to concentrate to take a good photo makes you ignore a large chunk which prevents you forming that emotion and memory.

> Long term, I can be completely objective about the times, places, people, conditions, etc. ...

True, but as I said, you had time to internalize that event before taking that shot. This is what it creates the anchor and reinforcing effect. You can't reinforce a memory you didn't form.

> There's a less objective angle to this that I still acknowledge and enjoy. ...

Photos bring joy, but not always. There are many positive photos which makes me feel bitter, or even sad.

> That's part of why I think there's a big difference between scrolling a backup of all your phone photos vs hand-curating albums ...

I can relate to that, but I also take a different approach. If I have the time and feel for it, I challenge myself with "1 scene, 1 shot", regardless of the camera I have with me. This allows you to ingest the scene you're in, take a purposeful look and decide which photo to take, which forces you to create a relationship with your surroundings. When you take that photo and revisit it in the future, that frame will make you remember the whole area where you searched for that one shot, and will bring tons of memories and visions back.

If I don't decide to or can't do that, I curate albums as you do, yes.

If you're interested, my photos are available at

https://flickr.com/zerocoder

https://instagram.com/hbayindir

P.S.: That flickr page needs some cleaning up and tidying.

[jjav]

> Write it, and you forget it.

For me, writing by hand means remembering.

I still lug around an actual notebook to all meetings and take notes by hand. I approximately never look at those notes later, because I remember everything important that I wrote.

I've tried every variant of taking notes electronically and the result is I don't remember any of it. Counterbalancing, it sure is easier to grep a text file than search on paper pages in my notebook.

But, having the info in my head is still orders of magnitude faster than grep, so taking notes on paper wins for me.

[bayindirh]

> For me, writing by hand means remembering.

When you're writing about a subject or meeting notes, sure. When you're writing a 30-item to do list, your brain will say "Nope, everything is on that notebook, refer to that".

As I noted in my original comment and elsewhere, I'm a heavy pen and paper user. I finish approximately two notebooks a year, plus I do my thinking/research on their dedicated notebooks.

Personal knowledge base and other digital notes are just distillations of these notebooks in a synced/searchable form, and I'm slowly making these public, as I have time.

[williamcotton]

Can you critique my usage of ChatGPT?

How exactly is this rigging my "own foundations with explosives"?

https://chat.openai.com/share/927ac3b7-2b3c-46ea-a74b-d0dec5...

[bayindirh]

Putting that there's no guarantees for correctness for AI models aside, you miss the opportunity to read the docs and learn (or at least be aware of) the whole capabilities which may help you in the future.

You can bookmark the relevant doc page, and return to that whenever you need it. Instead you now have a buddy which you can bug and get answers in general, so you slowly wither your ability to do research, read more complex docs, and learn with collateral information (i.e. you learn something, and be aware of other features, so you slowly learn and internalize the whole subject).

Instead you ask, and get a nibble of information which is harder to connect to other bigger corpus you might have. You probably saved time this instance, but if you read the docs, you'll progressively spend less time on the subject, saving you tons of time down the road, plus you'll sharpen your ability to read docs and be faster at searching, reading and understanding them.

[saghm]

These arguments seem like they'd apply equally well to googling for the documentation to a specific function and then using the answer from the preview snippet (or clicking the link, reading exactly what you need, and then closing the tab without reading any further). I'm not saying that means they're wrong, but it's hard not to feel like it would be hyperbole to call that "rigging your foundations with explosives".

[bayindirh]

It's a matter of habit. I personally don't search for answers on the internet to begin with. I use Zeal/Dash to store docs of the tools I use locally, and directly read reference docs for what I need. If I need information from a very specific page, I always bookmark or take note of the specific page, and return to that automatically. I also always read beyond what I need to see whether I'm missing something or holding something wrong. If that's I use very frequently, I further document what I do, and how it works in my personal knowledge base.

In surface asking ChatGPT is not different using StackOverflow for everything, but I can argue that StackOverflow bears the same dangers, unless the answer given is comprehensive and written with collateral information in mind.

However, having a personal assistant on tap which can answer (or hallucinate) anything or everything will definitely make you lazy.

[williamcotton]

Here are the tools I will be using today:

F#, Jupyter, Python, R, MySQL, PostgresQL, ZSH (awk, sed, fill in the rest), VS Code, Excel, Word, git, and probably more.

This weekend I continued to work my way through Learn You a Haskell For Great Good, taking time to go over the functional programming concepts in both Haskell and F#. In addition I read most of Data Science at the Command Line, where I was introduced to ggplot2, so I then worked my through the online ggplot2 book.

I'm not very interested in memorizing the complete syntax, standard library, and common third-party libraries for the myriad of tools that I've listed above. I don't really see the point of learning how to read through the MySQL documentation.

Here's what I want to have in my brain: Most of Townes Van Zandt, Willie Nelson, and the Grateful Dead's catalog of songs so I can play them on acoustic guitar without a songsheet as I like to make eye contact with the audience.

So yeah, thank you for telling me that my approach is slowly withering my abilities.

I'll put this as nice as I can: You are very judgmental.

[itishappy]

Since you seem a bit touchy about the feedback you specifically requested, I'll take a tangent:

How are you finding ChatGPT for functional stuff? I found it to be unusably bad, unable to transform trivial programs. Have you found it helpful for Haskell or F#?

[williamcotton]

Oh, I have found it very helpful.

FWIW, it takes practice to get good at using ChatGPT. You have to direct it in certain ways and break up problems into bite sized chunks to do complex things like, eg, assist in writing a language server for a custom DSL using FParsec. If you don’t have a higher level understanding of the task and don’t break things into smaller tasks it won’t work very well!

[bayindirh]

> I'll put this as nice as I can: You are very judgmental.

Thanks for your direct and honest view. No hard feelings here.

Let me tell you. I know C, C++, Go, Java, bash, Eclipse IDE, git, Docker, Saltstack, Terraform, OpenStack, Kubernetes, some MATLAB and probably some other tools I forgot that I know, and I manage a big fleet of servers while I'm writing this.

I don't "remember" the syntax of anything. I somehow internalized them. I don't think about them. If I make a mistake, my text editor (which is NOT VSCode) politely tells me about it.

I also used to remember double bass parts of Bizet, Beethoven, symphonies of local composers, plus tons of songs, because while I had the sheets in front of me, I had to listen tubas & percussion to make sure that I'm in sync with them and watch the conductor to double-check the metronome in my head and get the tone cues if he's not happy with our tone. To make sure that our 100 person orchestra was playing at its peak performance I had to make sure that I know every kink and chicane of the traffic for our specific arrangement.

In these days I remember tango songs' traffic because I have to plan my figures 2-3 sentences ahead while dancing in a crowded hall.

Oh, I sometimes play a couple of songs in my bass guitar if I have time from other activities.

So, yeah, thank you for telling me that I'm judgemental.

I'll put this as nice as I can: The choice is yours, but you're underestimating your abilities. Plus, people who like to read docs and write code the hardcore way are not dorks.

Have a nice day.