DandyDev

Are you really comparing a socialite from a wealthy family who didn't have to work to a regular Vietnamese guy who built his own business from scratch?

Making enough money to support the lifestyle you want is useful, no?

How do you even get to this take?

The guy clearly explained how he has built MULTIPLE successful products. So there is obviously more going on than sheer luck.

And jumping on the AI hype is exactly what being a good entrepreneur is all about: recognizing an opportunity/gap and capitalizing on it. And the reason he was more successful than those thousands other developers is because he understands that there is more to business than building a cool product. For example marketing, something that he is clearly very good at.

How is this guy "exploiting" people? He sells products mostly for a one-time fee - something HN often reminds us is way better than "subscription for everything". And these products obviously serve people well.

And since when is being successful and in detail explaining how you went about it "bragging"?

I agree that it is a market failure, but it is for sure a marketing success. I cannot help but feel that there must be dozen competitors to his simple products that gather more "honest" profit margins (aka are cheaper or more feature rich) but have a hard time with marketing.

This is obviously something Tony put a lot of time and effort in, and it paid off. Good on him!

Thanks for the clarification. The limit of 30 repos per user is indeed more reasonable. The support for Github Enterprise which would necessitate the Enterprise tier, is that referring to all flavors of GH Enterprise or only the on prem version?

Here's the thing: I think it's a bad idea to try it out, because I can already see in the pricing tiers that if I would like Graphite, I cannot afford it for my team because of the pricing structure.

I work for a startup that is less than 3 years old and has ~90 employees of which ~50 are software engineers and data scientists (people writing code). We're VC funded and not profitable yet. When I see a pricing tier called "Enterprise", I do not expect to fall under that tier as a small, young company. But looking at the limits of the Team tier, we would probably not fit under that tier because we have more than 30 repositories. We also use Github Enterprise (cloud version), which puts us in your Enterprise tier as well.

If the Team tier is already $30/user/month, I'm afraid to even learn what the Enterprise tier is like. I guess we're not your target audience and that is okay.

Here is when I would consider paying for your product: remove the repo limit (or make it much bigger) and half the price. That would make it affordable and more in line with the other tools we're paying for.

Honest question: how did you folks determine your pricing? I totally get that what Graphite offers is valuable and can improve developer productivity. But from where I'm standing, the pricing is disproportionate to the value add.

Github Enterprise - while of course not 1-to-1 comparable - offers so much more functionality for 2/3ds of the cost of Graphite. I'd expect Graphite to cost _less_ than Github Enterprise as it seems it could be positioned more as an add-on to what you get from Github.

Am I missing something?

That is not how a large part of the citizens on the internet works. Hell, a not insignificant number of people will still "search" for Google in their address bar before they get to the actual googling

You're trying to make the point that the only companies using Java are doing so because of legacy. That is demonstrably untrue. Netflix and Google have had ample time and capacity to replace Java, yet they didn't.

As any good engineer, people working at those companies recognize that Java, Golang, Rust etc. are all tools and these tools have their place in different scenarios.

I used to be like you, but my personal "anti-language" was PHP. I would talk down on organizations using PHP and I would take them less seriously as engineers. But I have come to see that they too are using a language (PHP in this case) as a tool to build a business. And it serves those orgs well apparently.

Don't get me wrong, Java would not be my first choice in many cases. At the company I'm working for, we only use Golang and Python in the backend and Typescript in the frontend. That doesn't mean that I cannot recognize the value the Java can bring and the niche it occupies.

I'm actually pretty amazed by how far Java has come as a language. 10 years ago, I thought Java was going to be replaced by the likes of Kotlin or even Scala. But Java has pretty much caught up in terms of features and ergonomics compared to the Kotlin and occupies a comfortable spot now as being an expressive and productive language without bringing the learning curve and footguns of Scala.

Those are pedantic semantics. I assume you know what I mean. But I'll explain it to you: with Rust you are in control of how memory is managed. Indeed through the borrow checker.

Do you feel good about yourself, talking down on people that made a perfectly valid choice by developing software in Java?

Let's look at the alternatives you mentioned: Rust and Golang. Java compared to Golang is a much more expressive language. Java compared to Rust is a much easier language because you have a garbage collector for the majority of the cases you don't need the manual memory controls that Rust offers you. In other words, Java is a perfectly valid alternative to both Golang and Rust with its own tradeoffs.

You try to paint a picture of Java not being cool but at the same time I see "modern" companies that are held in high esteem for their engineering prowess using Java to do incredible thing (e.g. Netflix and Google)

This seems written by AI? And as such it comes across as not genuine

My my, why so angry? You're expecting something that Excel doesn't support for good reason. The string you used as an example might be a date string to YOU, but to Excel and many of its users it's just a large integer. Lots of regular use cases would break if Excel would interpret that string as a datwle

If you want Excel to interpret strings as dates, use a more common date representation such as iso8601

This is indeed a red flag. I usually (truthfully) tell applicants the opposite. That despite $company being a startup, founders and senior leadership are all grownups with families and as such we value a healthy work/life balance, don't have any pizza-coding in the evening going on and don't expect overtime.

This is a great explanation. And to me, what sets Datasette apart from a generic SQL UI, is that Datasette excels at publishing _specific_ and curated datasets and allowing interactive exploration in a way that plain CSVs just don't offer.

If you'd read the article, you'd know that the legitimacy of the tweet has been verified by Ubisoft. They apparently really do close accounts due to inactivity

HN is supposed to be a site where participants each other's opinions.

Your response feels disproportionate. As if this person is suggesting giving up your liver is a reasonable price.

I think you're absolutely right! What OP tries to bravely build here, does not need such a complex architecture, even if they want to turn it into a SaaS solution.

I also feel that your comment is slightly ironic, given the poor performance of Notion. I'm almost thinking (without having any clue about Notion's architecture) that Notion could benefit from a more complex architecture that prioritizes performance.

That is a cheap comment. Could you elaborate why you disagree with the comment you respond to?

I think take-home assignments are great, but companies using them should be willing to put in the time to properly review and give feedback. And - spoiler alert - that takes a whole lot more effort than companies like fly.io are putting in, as evidenced from the comments on here.

The reason take-home assignments can work well in my opinion is that it allows the candidate to show off how they perform in _real world_ scenarios - as opposed to live coding computer science toy problems. Interviewers can assess what code looks like that resembles the code candidates would likely write on the job.

What companies like fly.io are doing wrong: if you ask candidates to put in multiple hours writing code for free, the _least_ you can do is give them an interview to give the candidate feedback on their assignment, even if you're going to reject them. In case of rejection, it doesn't have to take more than 15 minutes of time from the interviewers (which is far less than the hours the candidate put in) and the candidate walks away with (1) valuable feedback that can help them improve and (2) a positive view on the company and their hiring processes.

What many companies don't understand is that your goal should be for candidates you reject, to still become "promoters" of your company.

Here is how we do it at Source.ag:

1. If the resume is promising, we always do a first screening interview with the candidate _before_ we even consider them for a take-home assignment

2. The candidate gets the take-home assignment after passing the interview, works on it and sends us back their solution

3. We schedule a technical interview with the candidate. This interview can basically have 3 formats:

a. the assignment was bad: we tell the candidate at the beginning of the interview we don't intend to continue with them and give them some personal feedback on the assignment

b. the assignment was great: we take time to ask the candidate about their solution, to elaborate on their tech choices etc. and generally use the interview to understand if their "talk" is just as good as their "walk"

c. the assignment was ok-ish: we use the interview to figure out what the candidate's engineering knowledge is and to what extend it complements what we got from the assignment. It could be that a candidate didn't perform super well on the assignment, but when talking to them we discover there is enough skill, knowledge and team-fit to work with. This happens mostly for junior-medior candidates, not for seniors.

This is a time investment for us as a company, but has gotten us good hiring results and a positive reputation when it comes to hiring practices.

I like it because it doesn't sugar coat the issue

I think the myth that Apollo was using the API in an inefficient way had been debunked. I'm on mobile now so I cannot easily find the post, but the dev of Apollo explained clearly that how he is using the API is entirely within the limits and conditions that Reddit set.

And as I understood it, they weren't making unnecessary calls or anything.

I assume they did some research, a/b testing etc. and found out that this is a price people are willing to pay. Also, this is 2 beers. 1 if you have to pay US service fees and a tip

I think the point of the article is that you should not want to build a type-B workplace. If you want innovation - and healthy companies should want that - you should hire people asking critical questions

You can use the mkdocstrings plugin with mkdocs which will generate api docs from your functions and classes and their docstrings just like Sphinx does. It even supports inv files just like Sphinx so you can reference third party libraries in your own reference docs

Can you name some examples of these bias issues?

This is so true! I see people in this thread talking about the contempt that "idea people" have for programmers/software engineers, but at the same time I have experienced Product Managers (the quintessential idea people?) who were really good at turning their ideas into super detailed specs.

As an aside, I'm getting a bit tired from the "programmers vs product/business people" trope. The average software engineer would be nothing without a good product manager in my experience. And going by this thread, there seems to be at least as much contempt from programmers/software engineers for product people than allegedly vice versa.

Congrats on the launch of V2!

What are the main differences between Permify and Authzed/SpiceDB?

I understand the reason for using Javascript as the scripting language here, because of its mass appeal, but to me personally it's super disappointing and a missed opportunity.

Python to me has always been the ultimate glue and scripting language and it's sad to see it is not leveraged more often.