Now we write tests and when all test pass we write new test for checking the tests
Care to expand on how is this accomplished?
HN user
Now we write tests and when all test pass we write new test for checking the tests
Care to expand on how is this accomplished?
Care to share the skill behind the Linus reviewer ? I tend to as it to do that but leave it up to LLM to decide what the means. Interested to see any specifics you might have included there if it’s ok to share.
That’s a little different, right? Using port 0 would imply that clients have not hard coded what port they should connect to and also we don’t mind having duplicate processes occupying other ports which are no longer on active use
This is amazing. Thanks for sharing. Did you ever look into capturing the states of where all the windows are once you are done with resizing them? So as to restore them later back into position if they ever get out of alignment ?
Thinking of the usecase where every task or a project deserves a certain arrangement of windows and it would be good to summon them into existence as and when needed?
And eventually it took 3 years.
A good use of LLMs imho is trying to get a start point for lookup docs, like
I like this and resonate with it a lot. Sometimes you don’t know what you don’t know or you you just a little about what you might not know. This helps at least give you a name for the thing which you can then verify from source.
Exactly that. Well said. I can control my learning but memory? Not as much.
Learning is one thing and being able to comprehend a piece of code at a glance is another. I might know them but wouldn’t immediately remember all the past and future short form of flags ever written. What is even the point of that? If I am comfortable with the essence of what they do, does it really matter that much if I have that ingrained in my memory that -r does foo while -f does bar?
Yes. It’s more of a convention. If a shell utility isn’t following it then it won’t mean what we think it would mean.
Also - it helps a lot when a utility accepts a path that may or may not contain hyphens.
Interesting. I didn’t know they did. Though can’t help but thinking that this is all going be a lot less valuable if your ovservability platform is on those mainstream cloud providers.