Hacker News new | past | comments | ask | show | jobs | submit | semanticc's comments login

The new chat memory feature got enabled by default.

It appears you are correct, from https://help.openai.com/en/articles/8983142-how-do-i-enable-...

> Memory is on by default.

This is a disastrous default.


Internet != Web. E.g., an ebook downloaded from Apple Books is not web content, even if it comes from the Internet.


Until that eBook inevitably gets uploaded to a piracy site. The implication is that if a web crawler can find it anywhere then it's fair game, regardless of provenance.


I would start with Python instead of C++, if you just want to learn a useful tool as a hobby. The official tutorial is a good starting point: https://docs.python.org/3/tutorial/index.html


Why was the employees' common stock worth $0? Liquidation preference for the outside investors? Related: How can a regular employee joining a startup know beforehand that there isn't a high chance of their equity (which is probably a significant part of their total comp) being worthless even if a big acquisition is made?


> How can a regular employee joining a startup know beforehand that there isn't a high chance of their equity (which is probably a significant part of their total comp) being worthless even if a big acquisition is made?

You don't.

I've walked into every startup with big promises of stock compensation highly cynical about seeing any of that equity, ever.

Unless the cash is sitting in your account, it doesn't exist.


This wasn't a big acquisition, it was an acquihire. The company essentially failed. They raised ~$40M, and it's unlikely they sold for that much. Investors will get some of their money back, and the remaining founder will get some vesting equity at Airtable as incentive to stay post-acquisition.

But so long as you sell for less than your total raise, common shares will be worth nothing even with liquidation preferences of 1x.


Sounds like they raised tens of millions and had only $10M or so in the bank. Assuming the sale price wasn't in the tens of millions or greater, no common shareholders would have received anything.

> How can a regular employee joining a startup know beforehand that there isn't a high chance of their equity (which is probably a significant part of their total comp) being worthless even if a big acquisition is made?

Ask to see the cap table to understand what the company would have to be sold for in order for your shares to be worth anything.


You don’t know. Its a gamble. Sometimes it pays off. Most times it doesn’t.


assume it's worth zero

sadly, founders who are hiring don't want to hear that and typically don't want to compensate fairly for the high probability that their precious offering of equity is worth zero


I think that's a simplification. The upside is that there is clearly a functioning capital market for valuing and capitalizing high growth, early stage companies where you can make a lot of money very fast. The trade off is that if you don't want the high risk part of committing to a high risk asset, you shouldn't join the company in the first place. For this reason, most people shouldn't join most startups. Some people, of course, make a career from doing this well.

For those people, there's a blend of two things: 1) you think you know something the market doesn't -- it may be something cultural, the product-market fit, maybe you're just really impressed with the people and the momentum you're seeing, maybe you have really deep expertise and insight from previous experiences with the industry 2) you just plain enjoy it more, so the high risk premium is worth it to you overall over a more boring job where with a lower ceiling on rewards and career growth but higher risk-adjusted earnings

Working at a startup is often a mixed bag: an unpredictable, fast-paced, exciting journey full of variety and autonomy, with great highs and often even greater lows.

Most people are neither looking for that nor prepared for that day to day. Others believe they are open to it, but out of a desire to find the positive parts while avoiding the negatives, are fundamentally incompatible with doing what would drive success. I've never seen these kinds of folks achieve much consistently at startups.

It's the people who lean into rather than away from the risk that are instead the ones I've seen most success. They survive the notoriously high attrition and harsh pressure to deliver in high-risk situations without playbooks. They both can scale the company and hang onto leadership roles at scale. This, again, should not be and definitionally is not most employees.


If the product is being shut down, it is definitely not a big acquisition.

The only way to be sure it's worth something is if a secondary market exists for the shares. This is only going to be true for later stage companies, not early stage ones though.

I think the best advice on the topic of early stage options is this blog post: https://www.benkuhn.net/optopt/

The TL;DR for me is: Be more picky about the company than the specific comp package. When you're there, find as much as you can about the revenue growth and retention metrics (assuming B2B), and quit after your cliff if it doesn't look like it is going well enough to justify the valuation.


Regex is the parser for regular languages.


Yes, truly curious. It's not like base 10 is used anywhere in our society.


In our society, the HN community, getting an extra bit at 16, 32 or 64 is more exciting than turning say 30 or 60.

At least in my household this is the case…


You are probably not running a 32-bit IoT device.


The [artificial] scarcity and [unjustifiably] high price are properties of almost all luxury goods. And those are exactly what makes them (watches, handbags, diamonds etc.) so desirable to many.

I fully agree that spending two months' gross salary on an engagement ring is way too much though, and I would never ever get into debt for that. But, similarly as I enjoy wearing a relatively useless but expensive watch daily, I didn't mind dropping approx. 2/3 of a month's net salary on my fiancé's diamond engagement ring, which she got to choose and now cherishes and admires every day.


The only problem with `apropos` is that it returns so many irrelevant results:

  $ apropos 'count lines' | wc -l
     167

  $ apropos 'count lines' | head
  AllPlanes(3), BlackPixel(3), WhitePixel(3), ConnectionNumber(3), DefaultColormap(3), DefaultDepth(3), XListDepths(3), DefaultGC(3), DefaultRootWindow(3), DefaultScreenOfDisplay(3), DefaultScreen(3), DefaultVisual(3), DisplayCells(3), DisplayPlanes(3), DisplayString(3), XMaxRequestSize(3), XExtendedMaxRequestSize(3), LastKnownRequestProcessed(3), NextRequest(3), ProtocolVersion(3), ProtocolRevision(3), QLength(3), RootWindow(3), ScreenCount(3), ScreenOfDisplay(3), ServerVendor(3), VendorRelease(3) - Display macros and functions
  EVP_PKEY_asn1_find(3ssl), EVP_PKEY_asn1_find_str(3ssl), EVP_PKEY_asn1_get_count(3ssl), EVP_PKEY_asn1_get0(3ssl), EVP_PKEY_asn1_get0_info(3ssl) - enumerate public key ASN.1 methods
  EVP_PKEY_meth_get_count(3ssl), EVP_PKEY_meth_get0(3ssl), EVP_PKEY_meth_get0_info(3ssl) - enumerate public key methods
  OCSP_REQUEST_new(3ssl), OCSP_REQUEST_free(3ssl), OCSP_request_add0_id(3ssl), OCSP_request_sign(3ssl), OCSP_request_add1_cert(3ssl), OCSP_request_onereq_count(3ssl), OCSP_request_onereq_get0(3ssl) - OCSP request functions
  OCSP_resp_find_status(3ssl), OCSP_resp_count(3ssl), OCSP_resp_get0(3ssl), OCSP_resp_find(3ssl), OCSP_single_get0_status(3ssl), OCSP_resp_get0_produced_at(3ssl), OCSP_resp_get0_signature(3ssl), OCSP_resp_get0_tbs_sigalg(3ssl), OCSP_resp_get0_respdata(3ssl), OCSP_resp_get0_certs(3ssl), OCSP_resp_get0_signer(3ssl), OCSP_resp_get0_id(3ssl), OCSP_resp_get1_id(3ssl), OCSP_check_validity(3ssl), OCSP_basic_verify(3ssl) - OCSP response utility functions
  OPENSSL_malloc_init(3ssl), OPENSSL_malloc(3ssl), OPENSSL_zalloc(3ssl), OPENSSL_realloc(3ssl), OPENSSL_free(3ssl), OPENSSL_clear_realloc(3ssl), OPENSSL_clear_free(3ssl), OPENSSL_cleanse(3ssl), CRYPTO_malloc(3ssl), CRYPTO_zalloc(3ssl), CRYPTO_realloc(3ssl), CRYPTO_free(3ssl), OPENSSL_strdup(3ssl), OPENSSL_strndup(3ssl), OPENSSL_memdup(3ssl), OPENSSL_strlcpy(3ssl), OPENSSL_strlcat(3ssl), CRYPTO_strdup(3ssl), CRYPTO_strndup(3ssl), OPENSSL_mem_debug_push(3ssl), OPENSSL_mem_debug_pop(3ssl), CRYPTO_mem_debug_push(3ssl), CRYPTO_mem_debug_pop(3ssl), CRYPTO_clear_realloc(3ssl), CRYPTO_clear_free(3ssl), CRYPTO_malloc_fn(3ssl), CRYPTO_realloc_fn(3ssl), CRYPTO_free_fn(3ssl), CRYPTO_get_mem_functions(3ssl), CRYPTO_set_mem_functions(3ssl), CRYPTO_get_alloc_counts(3ssl), CRYPTO_set_mem_debug(3ssl), CRYPTO_mem_ctrl(3ssl), CRYPTO_mem_leaks(3ssl), CRYPTO_mem_leaks_fp(3ssl), CRYPTO_mem_leaks_cb(3ssl), OPENSSL_MALLOC_FAILURES(3ssl), OPENSSL_MALLOC_FD(3ssl) - Memory allocation functions
  PKCS5_PBKDF2_HMAC(3ssl), PKCS5_PBKDF2_HMAC_SHA1(3ssl) - password based derivation routines with salt and iteration count
  RSA_set0_key(3ssl), RSA_set0_factors(3ssl), RSA_set0_crt_params(3ssl), RSA_get0_key(3ssl), RSA_get0_factors(3ssl), RSA_get0_crt_params(3ssl), RSA_get0_n(3ssl), RSA_get0_e(3ssl), RSA_get0_d(3ssl), RSA_get0_p(3ssl), RSA_get0_q(3ssl), RSA_get0_dmp1(3ssl), RSA_get0_dmq1(3ssl), RSA_get0_iqmp(3ssl), RSA_get0_pss_params(3ssl), RSA_clear_flags(3ssl), RSA_test_flags(3ssl), RSA_set_flags(3ssl), RSA_get0_engine(3ssl), RSA_get_multi_prime_extra_count(3ssl), RSA_get0_multi_prime_factors(3ssl), RSA_get0_multi_prime_crt_params(3ssl), RSA_set0_multi_prime_params(3ssl), RSA_get_version(3ssl) - Routines for getting and setting data in an RSA object
  TIFFFieldPassCount(3tiff) - get whether to pass a count to TIFFGetField/TIFFSetField
  TIFFFieldReadCount(3tiff) - get number of values to be read from field


Well, staple utilities typically have short names, so sorting the results by name length might help:

    $ apropos count lines | awk '{print length($1), $0}' | sort -n | head
    2 gc (1)               - count graph components
    2 nl (1)               - number lines of files
    2 rg (1)               - recursively search the current directory for lines matching a pattern
    2 sa (8)               - summarizes accounting information
    2 wc (1)               - print newline, word, and byte counts for each file
    3 box (3x)             - create curses borders, horizontal and vertical lines
    3 cvt (1)              - calculate VESA CVT mode lines
    3 gtf (1)              - calculate VESA GTF mode lines
    3 rev (1)              - reverse lines characterwise
    3 sum (1)              - checksum and count the blocks in a file
Side-note, there are a bunch of neat utilities here I didn't know about!


Are you talking about web components?


Web Components are generally considered to be a set of standards, and Custom Elements is one of them. The others are Shadow DOM and HTML Templates (the <template> element).


Was wondering as well. You can just go ahead and use your own element straight away. You just won't get tag omission and other short forms, but you aren't getting those by using the questionable JS API for declaring elements (or proposed new APIs for HTML fragment parsing in browsers) either.

The use case mentioned - custom list bullets - can be implemented using CSS btw [1]. Not that I'd advocate for it; like all things CSS, it involves lookup of obscure and rare custom syntax, questionable layering a la "content:", suggestion of orthogonality that isn't really there, and browser support troubles.

[1]: https://web.dev/css-marker-pseudo-element/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: