Speaking from experience, every time I hit a wall with my projects, I would instinctively visit the project's repo first, and check on the issues / discussions page. More often than not, I was able to find someone with an adjacent problem and get close enough to a solution just by looking at the resolution. If it all failed, I would fall back to asking questions on the discussion forum first before even considering to visit SO.

Comments URL: https://news.ycombinator.com/item?id=46171236

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42987951

Points: 2

# Comments: 1

As for the non-technical stuffs, I'd like to at least breach the 25-minute mark in my 5ks (just under 26 minutes flat is fine). Running's been such a revelation for me this year. Definitely agreed with the idea that avoiding burnout is mostly a matter of doing the inverse of what you do on a regular basis[1].

[1]: https://gwern.net/backstop#burnout

(I’m 30 btw, so this site’s quite old by internet standards.)

Some genuinely interesting bits about how the committee sees the entire Javascript ecosystem today and what they envision the future will (probably) look like.

Comments URL: https://news.ycombinator.com/item?id=41795190

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=37609193

Points: 1

# Comments: 0

I happen to be handing that data over to airlines, which has some of the less forgiving, yet fragmented name requirements. If you handle this incorrectly, your customer can't fly, even after they paid for the flight. And for those who say that this doesn't matter as much: It absolutely does. People do get confused by this more frequently than you think. I've seen people losing an entire trip that they saved for, all because of unclear naming requirements.

The way I deal with this is to provide a country and locale specific name fields. You don't have to detect the geolocation or track the user for this, just let them choose whatever locale setting they want, and give them the "sensible" layout. Here are some examples:

- In Vietnam, we use last name then first name.

- In Indonesia, we use first name, then last name, but also give an option to declare that the person doesn't have a last name.

- In Singapore, we use a single field to input the first name and last name.

Even when you've handled the layout convention carefully, the 3rd party you're handing the data to, if one exists, might not give the same care and attention that you do. In my case: some airlines just haven't gotten around the idea that some people simply don't have last names. When a person with a single name wants to fly, airlines want the customer to use the name for both first and last name (e.g. If the person's name is David, then the airline expects "David David"). If you require First Name and Last Name as the input, and don't elaborate on how to fill them, the customer might simply fill the last name with a dot (".") character. The airlines / any other 3rd party won't accept that. For this, I suggest to detail out the ways in which you handle the data and go talk to your providers, if any.

All in all, it's a pretty tough challenge, and the wisdom around this isn't going to fit inside a single HN post. I do commend you for actually thinking about this problem. Good Luck.

Wondering what they are :)

It extracts the page's title, the url, and even prompts you to give it some tags if you need some.

You still need to host your own webhook to save it, but that too should be straightforward. Just use firefox's readability.js to strip the bloat elements and save it in your database. You could save it into Airtable like what OP's been doing, or even save it as a file in your cloud storage.

I don't appreciate their move towards "social" feed sure, but the reader has genuinely gotten worse. I remember that it used to have the options to adjust:

- Line Height

- Page Width

- Text Alignment

- Fonts beyond the defaults (for paid subscribers, which I am one).

In the new app, it was all gone. Yet, I'm still paying the same premium price for it. The web app still has those perks, but it's probably because there hasn't been any update to it for the past 2 years or so.

I haven't had any use for the app for some years now. Like what many say in this thread, it's not that hard to build a system that replaces it well enough. You just need to make it scrape links, turn them to markdown (personal preference), and index the entire content for FTS in SQLite.

Thanks to the OP for reminding me to cancel my subscription. Now I just need to find a way to export my huge pocket archive before the subscription renews.

Comments URL: https://news.ycombinator.com/item?id=36020508

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=34225009

Points: 2

# Comments: 0

The improvements are a lot more apparent on desktop. I love the fact that I can do pretty much anything using the command palette and keyboard shortcuts. Feels like this is the kind of browsing experience that I'm most contend with. The GPT-3 "ghostreader" feature was also great; most of the summary / text generations fulfilled my expectations.

If I have to pick on something: the mobile app browsing experience isn't that much better from Pocket or Instapaper. The scrolling and animation feels a bit laggy in my iPhone. The "ghostreader" feature in the app feels very limited and awkward to enable here as well.

Comments URL: https://news.ycombinator.com/item?id=33705182

Points: 3

# Comments: 0

Say that I generate a table using asciidoc's built-in syntax, the output will always generate HTML elements with the CSS classes already defined:

    

      
        
        
      
      

        

          
Column heading 1
          
Column heading 2
        
      
      

        

          
Column 1, row 1
         
Column 2, row 1
        
        

          
Column 1, row 2
          
Column 2, row 2
        
      
    

I prefer markdown's (and markdoc's) approach to styling, in that it doesn't really try to define any. My take on this is that stylings of the output should be be coupled with the toolings, as opposed to being bolted into the language standards.

edit: formatting

Google's process, while not perfect, made it at least transparent that the process is going to take a while. And at least in our case, the process involved some real people at the end to point out the specific concerns that actually lead to actionables.

Apple's process is slow, and seems to be worse in my region; it's clear that they're severely understaffed here. We spent a good 30 days trying to fix a crash, and they were all spent for either submitting a new app version to Apple, waiting for the review to finish, getting it rejected for some very vague reasons, and waiting for a response from them to elaborate their reasons for the rejection.

Comments URL: https://news.ycombinator.com/item?id=33333704

Points: 1

# Comments: 0