darshan

> Never ask questions or attempt to keep the conversation going -- answer the questions directly asked, and give additional information where it is likely to be helpful, but don't offer to do more things for the user.

I've never had an LLM offer to do things or try to keep the conversation going with this in my prompt.

It's definitely not useful for the same things, but it has a lot of similarities and seems potentially interesting as something to compare and contrast with this.

This currently has 1215 points, and the link is no longer valid. It now just shows an image of Firefox's devtools and the sentence "Replay is an early experiment. We'll let you know on @FirefoxDevTools when it's ready for input." That's not useful, interesting, or informative. The MDN docs seem like an appropriate replacement.

They apologized to the person they said it to, and it all seems settled from my perspective.

I'd say it's rude in general to tell someone they won't find something interesting, and especially so when it's done as a way of disowning your own preference not to talk about it.

The way I read it is:

* 219-09-9999 is a made-up number that was never issued to anyone.

* The woman thought it was her number for unexplained reasons.

* She used the pamphlet as evidence that it was her number.

I must be missing something important. Is it a joke, with the punchline being that she thought the pamphlet was her social security card? If so, how was this the fault of the Board? Was it her SSN somehow? If so, how did the pamphlet prove it?

https://www.swapadoodle.com/d/5288420972691456

I think 9× is the best speed to watch it at. (I'm still thinking of adding a way for the author of a Doodle to change its default speed.)

Or am I picking up on confusion about my general model (which I'm certainly open to feedback about). If you draw and don't share, but press back or try to leave the page, you're prompted about destructively leaving. Sharing creates the doodle and makes a link for you to share (or bookmark, or whatever you like), so the contents aren't considered wiped at that point; they're considered successfully sent.

Please let me know if I'm failing to understand what isn't working as you expect, of if you think my model is confusing to new users. Thanks!

1) Much of the general idea is a sense of connection and intimacy -- it's not just the final product that you're sharing, but the process. When you see the mistakes, or the attempts to get something just right, it's a moment of connecting with the sender's experience while making it.

2) You can make emotionally evocative doodles by removing elements, so they're only present fleetingly but not present in the final image. (Examples of this are by friends I haven't thought to ask permission to share. But think: drawing a small plant, then undoing and drawing a bigger one, for several iterations, for example. You can sometimes do that by "erasing" the part you want to remove by drawing the background color, but if you want to remove something that's on top of something else, undoing is so much easier.)

When Flutter came out, I looked into it, wondering if it might be worth switching my approach (I figured most of the Dart code would probably be able to stay the same). There were other deal breakers at the time, but I don't recall them.

Maybe once Flutter for web is production ready, it would make a compelling alternative, but for now it isn't an option. I'm not sure if would have made things harder or easier. But I'll be curious to check it out.

The things that are in the native wrappers are things that would be iOS-specific or Android-specific regardless of zero shared code or maximum shared code. In my case, the bulk of the app is shared -- everything that can be a common code base is a common code base.

According to GitHub's rough metrics, that's: Go 44.7% Dart 32.8% Java 7.1% JavaScript 6.9% Swift 6.6%

I’m finally launching a product that’s taken me years longer than I’d anticipated to complete. It’s a much bigger project than anything I’ve done before. My first app was the first battery indicator on Android, back in 2009, which was very successful by my standards (I didn’t have a college degree at the time and made way more money from it than I’d ever made from a job.) I also have a free instrument tuner on the Play Store.

Swap-a-Doodle aims much higher, and was quite an undertaking for me. It’s a cross-platform app (Android, iOS, and the web) for social drawing. I knew nothing about computer graphics when I started out, and just a bit about web programming. I learned so much along the way. I’m sure I’ll learn a lot more as the app grows.

The front end is written in Dart. The back end is written in Go and runs on App Engine, with Compute Engine for the websocket servers for live drawing (sharing a canvas with a friend to draw together at the same time). The Android and iOS apps are fairly small wrappers around the web app.

Feel free to ask questions. I’m of course open to feedback, or I wouldn’t post here — but I do feel somewhat vulnerable in this surreal moment of finally launching, so please keep that in mind and try to be kind if you do have criticism, and maybe frame it as “something that could be even better,” if that’s not too much of an ask. Thanks!

When Android was pretty new, I got the myTouch (the second public Android device) and was surprised that there was no way to easily see the exact battery level. I'd been a hobbyist programmer for quite some time, and it seemed like a problem I might be able to tackle. The result was Android's first battery indicator app, which remains by far the most-used piece of software I've ever built, with over 8 million downloads.

http://www.cdc.gov/nchs/data/nhis/earlyrelease/wireless20151...

Personally, I've found the issue to be documented well enough, and it is easy enough to set GOMAXPROCS to whatever works best for a given program, that I'm content with how the team has handled it. And I'm thrilled at the work that is being done now to fix the issue once and for all.