lostintangent

21 ms·

1.
by lostintangent 1y ago
This is so fun, and I just learned a couple things from it :) Personally, I find “learning through demystification” really effective. So putting the humor aside, I’d love to see more things written like this.
2.
by lostintangent 2y ago
Out of curiosity: what size do you think constitutes a “team” vs. a “department”? GitHub Next is 18 people (inclusive of all roles), which seems appropriately-sized to be called a “team” (certainly in a large engineering company). But apolo
3.
by lostintangent 2y ago
We (the GitHub Next team) use and love Apache Spark. So we made sure to connect with ASF before releasing GitHub Spark, and confirm they were comfortable with us using this name. We felt like there was sufficient difference between the two
4.
by lostintangent 2y ago
If folks want to see what Copilot Workspace looks like, here’s a sample session where I addressed a feature request in an OSS VS Code extension I maintain: https://copilot-workspace.githubnext.com/lostintangent/gitdo...
5.
by lostintangent 2y ago
We definitely intend to explore a VS Code extension in the not too distant future. And we decided to build a web client + integrated cloud terminal, simply because that allowed us to create an experience that is one-click away from an issue
6.
by lostintangent 2y ago
I can definitely echo the challenges of debugging non-trivial LLM apps, and making sure you have the right evals to validate progress. I spent many hours optimizing Copilot Workspace, and there is definitely both an art and a science to it
7.
by lostintangent 2y ago
One of our main goals with Copilot Workspace is to help offer a "thought partner"/rubber duck for developers, and potentially even other members of a software team (as you said, PMs, designers, etc.). And code generation is
8.
by lostintangent 4y ago
Is this like Weights & Biases for prompt-based LLM experimentation (as opposed to model training)?
9.
by lostintangent 4y ago
> No one interacts with my tweets anymore. Meanwhile, I get response on Mastodon that reminds me of the early days of Twitter, before they betrayed their developer community and hired a legion of people to cut ad deals. Out of curiosity:
10.
by lostintangent 4y ago
Wow, this looks awesome! I noticed that the sample notebook doesn’t include SD 2.0 by default, and says that it’s too big for Colab. Is that a disk size/RAM limitation? As an aside, it would be cool if you versioned that notebook in t
11.
by lostintangent 4y ago
Understanding Michael Porter: The Essential Guide to Competition and Strategy This is a commonly cited book about “strategic thinking”. But despite that, it’s one of the few business books that I actually read every page (as opposed to sp
12.
by lostintangent 4y ago
True! But you don’t need actors to enable horizontal scaling?
13.
by lostintangent 4y ago
Ah! That makes total sense. Thanks so much for that additional context.
14.
by lostintangent 4y ago
Then how do any of these distributed systems tools/frameworks write a meaningful or concise landing page? Making informed trade-offs are obviously important. But in a world of saturated information, it seems like there’s even more valu
15.
by lostintangent 4y ago
Any insights that you’d want to share with someone not using Java/Scala or Erlang/Elixir? I’d love to get the benefits of actors in Node, Python or Go, but I’m not entirely sure what I’m missing yet.
16.
by lostintangent 4y ago
How much of the value in actors do you think is related to the awesomeness of the Akka framework specifically? I only ask since it seems like there’s a decent correlation between people using Akka, and those that identify as using “actors”.
17.
by lostintangent 4y ago
Are you using Akka for your explicit actors as well? And could you share the distinction between typed and untyped actors? Is that related to how the caller addresses/accesses methods on that actor?
18.
by lostintangent 4y ago
I _really_ appreciate this reply! Naively speaking, when I look at actors, I just can’t think of why they’d be superior to coordinated queues/channels, except for within an arbitrarily configurable, rules-based system (e.g. game NPC be
19.
by lostintangent 4y ago
Very dumb question: when you say backed by Akka, what exactly do you mean? That you’ve configured a “binding” between Flint/Spark and Akka, which spins up actor instances (Java/Scala classes?) whenever some events occur? Or that F
20.
Ask HN: Are you using actors in production? Why/Why not?
56 points by lostintangent 4y ago|27 comments
21.
by lostintangent 5y ago
Yeah good point! Though I was also thinking about the ability to easily create/edit/delete gists, by means of file system operations. For example, it would be pretty cool if you could create a directory in some “gists” mount point
22.
by lostintangent 5y ago
Very cool! I love using GitHub repos and gists for managing my personal notes/code snippets, and currently use GistPad as an editor-level virtual file system (for VS Code). But having an OS-level equivalent is _super_ useful. Any plans
23.
by lostintangent 5y ago
Out of curiosity: what is it about Observable that you don’t care for?
24.
by lostintangent 5y ago
This is awesome! And it’s so exciting to see folks investing energy into this problem space. Out of curiosity: did you add support for multiple backends because you don’t think Git will ultimately be sufficient for the experience you want t
25.
by lostintangent 5y ago
Looks really interesting! Thanks for sharing
26.
by lostintangent 5y ago
Yeah GitJournal is great. I used it for a while, and the dev is super responsive and awesome.
27.
by lostintangent 5y ago
Is cloud storage anywhere near as opinion-inducing as note taking workflows though? :) There are like a dozen new entrants each month, and so it’s probably meaningful for folks to get super clear on their core requirements. Otherwise, you’d
28.
by lostintangent 5y ago
It’s a little bit clunky, but you can use GitHub.dev/<repo> on your phone. I do a lot of browsing/quick edits that way, and it works well enough. That said, I also use Working Copy for iOS to sync my notes repo, and will use
29.
by lostintangent 5y ago
Congrats on the release! I _really_ love the simple approach this tool takes. Though personally, I view note taking as “commodity” enough, that I prefer to own my data, and use my existing editor setup. If folks are looking for a productive
30.
by lostintangent 5y ago
Speaking of education/CS50: we (the Codespaces/Live Share team) have actually been very excited/privileged to collaborate with the amazing CS50 team, as they've built their student experience on top of VS Code/Codes

More ›