Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hzia
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
hzia
9mo ago
Congrats team! Graphite was basically what GitHub should have been but never was Huge fans of their work @ GitStart!
2.
▲
by
hzia
11mo ago
Most heavy users of python notebooks (including us) have a hate love relationship with it, especially when you add it into git. Honestly this is worth alone for the fact that there isn't random JSON blobs coming in PR diffs. I wish mor
3.
▲
by
hzia
1y ago
This is very exciting! Existing data will become a lot more valuable and it brings it one step closer to how we learn as humans! The downside is that this is going to be extremely expensive, so the data set to conduct RL will need to be cur
4.
▲
by
hzia
2y ago
I agree on the Bell Labs analogy Most browsers have consolidated over time because we are constantly updating web standards and bar for security is so high. On top of that everything has to be insanely backward compatible WebGPU is a good e
5.
▲
by
hzia
2y ago
Majority of revenue base lives on iOS globally (due to being a monopoly in the US) That's why Apple has higher profits than all other mobile operators combined!
6.
▲
by
hzia
2y ago
I think you are drastically overestimating the revenue gain from ad blockers But I agree that default search with being Google must have heavily blocked competition. Comparing how much they pay Mozilla and Apple to maintain search, it would
7.
▲
by
hzia
2y ago
That’s revenue not profits. Majority goes to app devs. Profits are all that matter
8.
▲
by
hzia
2y ago
I think most people do not understand that Google funnels a lot of their profits to make Chrome and Android into OSS. Youtube may be the only viable company that can come out of Google. Rest will either have to charge a lot of money or die.
9.
▲
by
hzia
3y ago
That sounds really low. Do you mind sharing where you rent your racks from?
10.
▲
by
hzia
3y ago
Thank you so much for that!! I wondered about this as well. Love how above and beyond you guys are going to support other OSS implementations <3
11.
▲
by
hzia
3y ago
How do you sign multiple devs on a commit though? Would it be a joint PGP key signed by all keys of all devs that helped with the PR?
12.
▲
by
hzia
3y ago
GitStart only takes care of well scoped tickets in backlog and finishes them at the PR stage. There is so much more to do including: technical architecture, API design, breaking down large projects, infrastructure and so on. All of the abov
13.
▲
by
hzia
3y ago
Your advice is spot on, and why we wanted to build a better than the current status quo! a) we already have a sizeable alumni who have gone through GitStart over time, with many still in touch. We are in works to bring them all together in
14.
▲
by
hzia
3y ago
I appreciate the candid honestly! Even though we are aiming to become a career accelerator for junior devs, not everyone is going to graduate right away. For some, just a few months of experience is enough but for others it can take years.
15.
▲
by
hzia
3y ago
We already have email+password+verification_link combo for client dashboard, and we are soon bringing it to our developer dashboard soon! (along with a brand new dev focused website) Unfortunately the developer waiting list is quite long so
16.
▲
by
hzia
3y ago
How was your experience recruiting and working with dev teams based out of China? And how do you enforce foreign contracts from aboard (or draft local ones with a sub within China?) We already have customers and a subsidiary based out of Ho
17.
▲
by
hzia
3y ago
Internally we are expanding ways in which we draft multiple PRs initially when new devs onboard and send the one with the best peer review approval We could infant send all the draft PRs upstream. And as a senior dev upstream, you review a
18.
▲
by
hzia
3y ago
We enable EOR + BR + MDM setup on the enterprise plan. Plus, MDM is usually gimmicky given most devs for these clients work in a virtual environment anyways (so the code never leaves their infrastructure). IMO if we fail as a company, it wi
19.
▲
by
hzia
3y ago
Quite a few are due to priority changes over time. We are thinking to automatically close PRs when there is no activity for > 14 days.
20.
▲
by
hzia
3y ago
Do you think outsourcing (“gets outsourced anyways”) still happens for most tech teams? IMO, just like you mentioned, teams are so scared of outsourcing that this happens less and less. I agree that this works for well scoped tickets that o
21.
▲
by
hzia
3y ago
Currently most of dev bounty platforms do start with OSS, but we only started doing that last year. Because of that, 90% of users of our commercial usage today is still close-source, and biggest customer base are from heavily regulated indu
22.
▲
by
hzia
3y ago
Unless there is a strong regulation like HIPAA, I have seen setting up a US based company (through Stripe Atlas) take care of most legal woes. But ultimately it depends on the motivation of the company itself, and they use all sorts of excu
23.
▲
by
hzia
3y ago
Agreed ... the service itself has to hold ground on its own. Thats why on our landing page, the focus is on the service itself with some mission interleaved. Would you reckon it's the right balance?
24.
▲
by
hzia
3y ago
GitHub PR detail view is a hot mess. The entire page is endlessly long, with very poor signal to noise ratio We are very tempted to re-build that experience on the dashboard(at-least for our PRs), but I hope someone can launch a simple dash
25.
▲
by
hzia
3y ago
I love this! We can make it even easier to ask for emoji reaction to the PR description instead of a comment to make it 2 click to take action And build an experience that guides them through the PR instead of getting distracted by nit pick
26.
▲
by
hzia
3y ago
And to keep memory usage under control, we restart the non-deterministic service every 2 days because we were too scrapy to clean up memory after using it. Jim said we will add more bugs fixing it so we believe him.
27.
▲
by
hzia
3y ago
My personal take is that the highest level of trust lies with the in-house team. If thats broken, you need to restructure the team until trust is established again. I am really skeptical about a service (like pullrequest.com) where external
28.
▲
by
hzia
3y ago
We currently attribute commits back to every single dev involved in a PR (including reviewers) as co-authors. We also actively work with our customers to allow devs to mention their contributions in their CV publicly. And you can always rea
29.
▲
by
hzia
3y ago
I see more interest on this than I expected! In the last month, we have rejected quite a few tickets that may have been easily tackled by a senior dev. Including technical documentation for infra, K8S, CLI agents to collect runtime traces,
30.
▲
by
hzia
3y ago
Good point! Also some cultures also show far less care than others (despite feeling the same way) A lot of my Asian friends do not pro-actively jump into slack to not look stupid, but the moment you get on a pairing call with them the perce
More ›