I have just downloaded and set it up to talk to Anthropic. I have some unused API credits that I've been trying to find a use for. Haha.
To be honest, I was very confused by the the @'ing. Is it possible to always pin the current open file to the context, perhaps in a FIFO fashion? (Other than the manually pinned files). The UX around pinning / @'ing is not super clear to me.
Otherwise still getting the hang of it, and generally pretty neat.
From latency perspective, not really. As someone who used redislabs at a previous company, the requests got routed through the Private Network proxy (whatever AWS calls it) which minimizes any networking overhead.
You may feel less enthusiastic about it once you watch the linked video. I wouldn’t exactly call it a roundabout. That’s only what’s at the center of it.
Assuming you’re asking in earnest I would begin with S&P 600 Small Cap companies, and see how they got their starts. These are all profitable companies with various levels of earnings growth and indebtedness.
Also commercial real estate fits your criteria almost perfectly.
For such applications, isn’t the parallelism count usually static and limited? I think there will be good benefits for distributed system frameworks for python. Id agree.
A couple of years ago, I implemented in process parallelism for a system I was maintaining at $JOB. I was happy the system was in Go and not Python. But it was an exception to the rule in my experience.
What a great article from LWN. It was well-worth reading. As someone who was excited about the NoGIL from Sam Gross when it was first posted here, I think I'm beginning to change my mind after reading this article and reflecting on my own personal experiences.
My experience is with writing backend systems in several different languages (including Python) at various volume/latency/throughput levels. I've basically worked on only two types of systems -
1. one that exposes some sort of an endpoint to the network - it accepts requests of some kind, does computation and other network requests and sends response of some kind (including long polling, ws etc).
2. reads a message from a "queue" (could be database, could be based on polling another api etc) and does computation/network calls and basically sends it to other queues.
Nothing else. Huge variance in specific requirements, but that's it. For the first type of system, latency matters more. For the second system, throughput matters more.
For the first type of system, I want to be able to spin up threads in response to requests, without worrying that an endpoint is too computationally heavy and might block others. I want to be able to share connections to databases in a shared pool. NoGIL would be useful here.
For the second type of system, I can't remember the last time where I wrote one where I had in-process parallelism/concurrency with shared resources (even in langs where there's no GIL). It would just get too confusing and hard to reason about. Any optimizations were mostly based on intelligent batching. For parallelism, you'd just have multiple _completely_ independent processes, probably across multiple machines.
I would absolutely be disappointed if NoGIL meant compromising on the quality of of the second type of system here. In practice, most of my mental bandwidth today goes towards making the second type of system better.
> I know enough Hindustani music to understand that only melodies are played, and almost never harmonies. Especially when the artiste is performing alap.
I think is broadly true, but anecdotally speaking, myself and people I’ve trained under use harmony and love harmony for hardcore Hindustani classical. It’s a bit of a shame that more don’t use it, but I wouldn’t underestimate it either.
You add it in your addendum, but I must emphasize that you are extremely biased towards Carnatic.
For context, I’m trained in Hindustani music and have given a number of performances and have family and friends who have done the same for Carnatic music. My experience is that Harmonium is very common as an accompanying/supporting instrument - probably precisely for the reasons you specified. Harmony is great, it doesn’t mimic to do the vocal variations - just support the singer doing it as well as possible.
What I’ve actually seen is that use of Harmonium as an accompanying instrument is much more common across the spectrum (both north and south) than Violin for classical and semi-classical - though unlike Violin it’s almost never used solo. OTOH I’ve never seen violin being used in Hindustani.
Sure, but they also (likely) have tons of teams maintaining and improving them. It's somewhat (but not exactly) like saying Youtube and Android are not Google's products.
Developer here. I quite like Jira, I've never seen anything as fleshed out or complete as it is. At a previous startup, I used clubhouse.io, but I seriously missed Jira after a few months.
I generally think Atlassian is a really solid company building good products and I really don't get the hatred. I'm also open to acceptable alternatives to Jira and Trello.
Edit: ooh, just saw that they also own statuspage. And everyone uses/likes statuspage.
Amusingly (to me) the third attitude towards this is: "It just is that way. I'm sorry that the answer does not satisfy you, but the universe does not owe you a satifying answer." :)
Great recession grad - similar numbers. That experience has really scarred me till today, especially because I kept being told how valuable software engineers are, and how good I personally was in this field.
Today, I'm simply grateful to have a fantastic job, and strive to live below my means assuming that things can go back at the snap of someone's finger.
In terms of practical advise for a new grad, there are tons of startups and enterpreneurs doing really interesting work. They need good programmers but can't afford to pay as much. This sort of place can be a great place to kickstart your career, at least for a few years, till the broader picture gets better.
I’ve noticed this but I don’t look at it as maintaining relationships.
If you are going to cover a topic deeply better cover all sides of it rather than just a criticism piece or a puff piece. This is what Keeps me coming back to economist.
for real under-performers, it's usually clear within 3-4 months, esp in small teams / small startups. i have _never_ seen a case where i feel a person lacks fundamentals or is a bad culture fit for a team after 3 months, then turn it around 6 - 9 months.
any number of months waiting after 3-4 IME is months too late. but it feels cruel and it's tough to convince yourself you're right in a specific case. especially when you get to know the person.
To be honest, I was very confused by the the @'ing. Is it possible to always pin the current open file to the context, perhaps in a FIFO fashion? (Other than the manually pinned files). The UX around pinning / @'ing is not super clear to me.
Otherwise still getting the hang of it, and generally pretty neat.