To be fair, the author admits that including maintenance, a project is never really finished.
Instead, he says that a project should be _published_. Preferrably, on GitHub :P
385 karma · joined May 24, 2021
To be fair, the author admits that including maintenance, a project is never really finished.
Instead, he says that a project should be _published_. Preferrably, on GitHub :P
In my case I only ever used the concrete types and converted between them at some point.
export type LinkedWorksheetsRecord = Record<WorksheetId, Record<WorksheetId, ReferenceTypeId[]>>;
export type LinkedWorksheetsMap = Map<WorksheetId, Map<WorksheetId, ReferenceTypeId[]>>;
What I would rather have written instead is however something like this: export type LinkedWorksheets<T> = T<WorksheetId, T<WorksheetId, ReferenceTypeId[]>>;
...
const myMap: LinkedWorksheets<Map> = ...;
This is however not possible, because `Map` is a type constructor which expects two more type arguments `K, V` until it is a fully applied, concrete type `Map<K, V>`.With a library like this, this is probably possible (unless I've missed something which wouldn't surprise me). It would unfortunately surely be more verbose.
Still, I would be against pulling in a dependency only for something like this. The above example is simple I believe, but not exactly a "killer-app". And no, Monads aren't either (if you don't limit effects and don't have do-notation) :P
I think writing blog posts may be hard, but writing a constructive comment is hard also. People are not good at it, and I often find myself writing something and then just give up in the middle and deleting it again. Not just because finding the right words is hard (especially if you're not a native speaker), but some of the same questions go through my head as well (Who is the intended reader? Hasn't someone commented on this before? ...).
Thus I would suggest assuming the commenter has spent more time thinking about what to write than you might expect. And even if not, someone else may get some value out of their comment, so even if it isn't you, give them the benefit of the doubt. The point about assuming they're confused, not angry, is spot on I think.
There is probably a connection to the point about writing becoming harder with more experience. Each sentence you write will trigger more warnings in your head, or it might become harder to put yourself in someone else's shoes. To keep going, you probably have to learn to just accept and expect imperfection and just keep going, cut the editorial phase short at some point and just publish or you'll never get done.
The next presumably angry/ignorant/dumb commenter you encounter may have just done that, and by necessity. You never know.
I found this an interesting high-density read, and I think some of the advice can be applied to non-workplace situations.
There's unfortunately also the saying "Nicht geschimpft ist genug gelobt", i.e. something like "Not being scolded is enough compliments".
If things work, they are taken for granted and some people only speak up if they are irritated.
Which of course leads to a biased perception of how satisfied the people on average really are with your work.
Last week I wrote an email to an author to a blog I have been following for a year or so. Just wanted to let him know his work was appreciated and I hope he continues writing.
He replied and told me this little gesture made his day. So I guess I should do more of that.
Edit: I think I got this wrong. Most likely, this is due to some "Undo <action>" always being displayed.
Otherwise I found this a nice writeup.
Part of me is hopeful that this will have the effect of people recognizing that maybe a) The text didn't need to be written after all, or b) The bullet point you started out with, were enough after all.
There is too much content being produced out of a notion of "something has to be here" for layout reasons, or because its simply what somebody expects.
Probably, ubiquitous use of generative text model will worsen the signal-to-noise ratio we see in media today.
So if it's necessary to be careful about the defaults and to audit everything carefully etc. (i.e. if it's not idiot proof), I am doubtful this is as helpful in practice as one might expect.
I still agree with the general point of your comment though.
It might be a fool's errand though if the spam is not obvious enough to catch with a regex.
My first reaction was "why not a password-protected zip" and you already linked to a relevant stackexchange question. I think it might be helpful to add a "Why not a password-protected zip/rar/7zip/..." on your page when you have time for it.
Or maybe even explicitly make clear which security goals (confidentiality, integrity, etc.) are satisfied by this. The reason being of course that I would like to show this to colleagues/friends and not having to debate this myself :)
Which is why I never published it (although I have been using it for almost two years), and setting it up requires a series of laborious steps of activating the Google Developer Console, creating API keys etc., which I found just to embarrassing to put in a README :)
Do you intend to make the search limit a daily thing, or will it only apply over the whole month?
For me at least, I have spikes in my search behavior, like when I'm working on some difficult project, while on other days there's not much going on. While having a search budget would maybe get some getting used to, I could see myself working with it if I had a way to plan ahead.
It would help if there was UI support for this, similar to what mobile phones have in the "Mobile Data" settings (data used/remaining, usage graphs and so on). I'm also on the beta right now, but haven't seen anything like that when looking just now.
Writing publicly visible texts like even comments is a hard thing to do for me. Even if I am sure I have something of value to add, I mull over all the variations of how to phrase my point and in the end just delete it. Never mind writing a blog post, although I have played with the idea for a long time.
But sometimes you are forced to write, like for school/uni/work. And then I pretty much do all the things mentioned in OP's post, so this gives me something to think about.