ivan888

It’s probably not too important to choose a service that you think you can trust fully, because that trust might be broken at some point. But having an identifier that can be swapped to different backends, so people can find you again when the host inevitability changes, is a stronger strategy. I think the importance of owning domain names will increase, and using those as the canonical identifier of a project will give it more permanence. The procedures for seizure and censorship with domain names are better established and understood.

But consider how, in just a short few years, tools will have changed so much that even achieving this specific look will not even be possible (everything is in the cloud and normal users can’t even run them locally)

We’ll inevitably end up feeling nostalgic for these mid-2020s AI slop menus, much like how graphic design of the 90s and 2000s is revered (see other comments on this post) even while during its making was regarded as garish

Ah yes you are right. The policy I am referencing is for the Free or Pro tiers, Business is different

That's a good operating assumption, and I usually think this way too.

It turns out Slack actually requires legal process or consent of parties to provide private messages to admins: https://slack.com/help/articles/204897248-Guide-to-Slack-imp...

But of course yes, another party could simply take a screenshot

I find myself holding onto and preserving general ephemera and just happened to scan a moist towelette package over the weekend. My collection mostly consists of business cards and dry cleaning type carbon copy receipts. I need to better catalogue these and share online. A few business cards: https://ivan.sh/biz-cards/

Going to "modernized" restaurants is just a drag. I don't want to touch your tablet or scan your code. I much prefer the restaurants which only accept cash

There's also the global gitignore configuration (core.excludesfile=~/.gitignore_global), which for me contains things like: *.swp, .DS_Store, scratch, etc.

This seems very low. I have not worked in professional screenprinting environments, but all resources I have seen indicate potential for hundreds or thousands of high quality prints from a well prepared screen.

The ending reminds me of the “Americans are obsessed with protein” article

This is too close to Idiocracy

Yeah I’ve had this same idea for the same reasons, and came to the same conclusions that without legislation, no incentive exists to send statements as attachments in emails or to store them with a 3rd party where they can’t be tampered with when a mistake is discovered

Dubs

Not sure if anyone else noticed the item id of this comment does indeed end in 88?

I'm interested to hear more about this. I think I have a tendency to want to do this myself. Any additional reading on this concept?

Taking real disconnect breaks (more than one week) also help a lot. Some people, including me until recently, don’t seem to do this often or at all

To be pedantic, its purpose is for verification testing of systems that allow for testing of the type you describe

I think this is still possible with access points that require installing and trusting a custom certificate. The example in my mind is WeWork's WiFi

It seems like even the Startup School signup is limited to students. I applied anyway, and will comment again if I receive a response

Can it do React yet?

I think going from code to OpenAPI makes a lot more sense, at least for strong typed languages. And even if not directly translated from code, at least closer to the actual code, in annotations or something. Generating the spec from code removes a step, where you simply need to update code, rather than update the spec then update the code

vim-rest-console[0] has been my Postman alternative for years. It basically wraps curl and makes it super easy to make different requests from a single text file. Can even write YAML and have it converted to JSON before being sent in the body. Really great tool

0: https://github.com/diepm/vim-rest-console

Location: New York (NYC)

Remote: Yes, but prefer hybrid

Willing to relocate: No

Technologies: Java, JavaScript, React, Spring, Postgres, Neo4j, Kafka, Microservices, TypeScript

Résumé/CV: https://ivan.sh/resume.pdf | https://ivan.sh/ | https://www.linkedin.com/in/ivangreene/

Email: ivan@ivan.sh

Experience as lead software engineer at an early stage startup, as well as experience in larger organizations. Prefer early stage startups in NYC

So get rid of the stupid persistent red dot on review queues on Stack Overflow

Location: New York (NYC)

Remote: Yes

Willing to relocate: No

Technologies: Java, JavaScript, React, Spring, Postgres, Neo4j, Kafka, Microservices, TypeScript

Résumé/CV: https://ivan.sh/resume.pdf | https://ivan.sh/ | https://www.linkedin.com/in/ivangreene/

Email: ivan@ivan.sh

Experience as lead software engineer at an early stage startup, as well as experience in larger organizations. Prefer early stage startups in NYC

I'm very new to make(1), but became a fan quickly.

Rather than maintaining documentation that inevitably gets out of date, if a project has a Makefile, it self documents the build process, language independently. No need to read a README to see if people are currently using yarn or npm, or find external documentation on a build tool you haven't used before; the Makefile shows the targets and what commands they run.

I wrote a pretty simple wrapper around this that gives the keys easy names and can store the configuration in a human readable format: https://github.com/ivangreene/keymap

Was unaware of the --matching option at the time, could be an interesting extension but I personally have no need for it

My biggest concern with tools like this is reproducibility and maintainability. How deterministically can we go from the 'source' (natural language prompts) to the 'target' (source code)? Assuming we can't reasonably rebuild from source alone, how can we maintain a link between the source and target so that refactoring can occur without breaking our public interface?

Since we are now at the stage where it's difficult to distinguish well reasoned human discourse from that generated by AI, I think that deeply linked citation systems in the form of knowledge graphs will grow in importance. Otherwise it will be too easy for AI generated discourse to begin referencing itself, introducing biases and clinging to blatant falsehoods without an easy way to discover their origin and fix the problems

Yes, "how can we simultaneously protect while also healthily socialize children?" is a difficult question to answer as a potential future parent. Social acceptance (to a degree) is critical to healthy development, while some of the most common uniting social tools (for previous generations, high levels of consumerism and signaling; for now and the future, near-constant technology use) are viewed by some parents as unhealthy and lead some to want to abstain entirely.

Viktor Frankl's "Man's Search for Meaning" is a great read; it puts into many important words the capacity that we all possess for growth and large mindset changes, which you mention in your first paragraph

Rich content (anything that isn't a listicle or SEO'd fluff article) has become harder and harder to find