Live data from Hacker News

One year as a solo dev building open-source data tools without funding

datastation.multiprocess.io

61–70 of 120 posts

Re: One year as a solo dev building open-source data tools without funding

#61

Is it bad that the first metric the author shares is a borderline vanity metric (Github stars)?

I reacted to this as well. I hope he/she gets real value for the work they put in. Having worked as a developer and consumer of open source work (for huge finance institutions), it pains me to see how devs pour their souls into open source projects, and consumers (our bosses) don’t even know or care who wrote the code everyone is using.

Re: One year as a solo dev building open-source data tools without funding

#62

If you can, it is always better to go full time. If you hourly rate is 150$ (in the market), and you can work 300H a month (including weekend) (It should be 400 hours - 13 hours a day). Than you are basically making around 70-100K a month (in value), but paying only 4K (in cash, your living expenses). Of course, if you are 2X, 3X , 4X engineer , you are basically making 300K a month for 4K cost.

I'm not sure this makes much sense. If you work for a large corporation you can easily make 100K+ a year and work a very reasonable 40 hours or less a week and live off of 4K a month.

Unless you're actually realizing those gains and earning 300K a month, you are not "basically making 300K a month for 4K cost". You are making 0 dollars a month for 4K cost.

Further, if you think that it will pay you back in full in the future (instead of making the money right away), you will have to invent a wildly successful product and/or customer base to backfill the pay for all the previous hours worked. Realistically, you'll probably make nothing for your first year unless you start with a plan to secure funding. You'll also bust your ass for a year while losing money in the hopes of a reward in the future. I know they say time is money, but it's not money the way you seem to be equating it here haha.

Re: One year as a solo dev building open-source data tools without funding

#63

Advice regarding VCs: Don't ever talk to them if they randomly approach you saying they "really like what you're doing". They will gladly sent an associate to talk with you about your business in the greatest detail and ask you to share presentations, demos and metrics. Anything you give them will then get passed along to their own portfolio companies in your space. So don't feel flattered when they feign interest in…

Had this happen (random outreach). Led to a series A. Respectfully disagree - I don't think competitors copying is a significant risk early on, compared to running out of money whilst trying to hit product market fit.

based on your anecdote against hundreds of thousands of founders getting spied on. I've seen it happen.

Basically if somebody wants to invest ask them: $ and t+

If they try to dodge or make up excuses, MOVE ON. IF they say if you give me A,B,C and then we can invest, ask them to put them in writing and put an exit fee. If they do not invest, they give you 1% of the proposed amount.

Somebody who is serious and has the balls won't waste time. Unfortunately rare.

I've wasted a two years of my youth because a VC on HN reached out to me, who ultimately just used my product/coding services.

Any dumb fuck can be a VC if they can raise cheap capital. Remember, there is very small group of VCs that know what they are doing. The rest are just in the game to spray and see what sticks on the wall (most of them do not make it during a downturn)

Re: One year as a solo dev building open-source data tools without funding

#64

Advice regarding VCs: Don't ever talk to them if they randomly approach you saying they "really like what you're doing". They will gladly sent an associate to talk with you about your business in the greatest detail and ask you to share presentations, demos and metrics. Anything you give them will then get passed along to their own portfolio companies in your space. So don't feel flattered when they feign interest in…

Had this happen (random outreach). Led to a series A. Respectfully disagree - I don't think competitors copying is a significant risk early on, compared to running out of money whilst trying to hit product market fit.

While both are anecdotes, I think the original warning is the more important one as it's not the one new founders will expect to encounter. Nothing wrong with taking the call, but be aware of the risks and do a bit of homework before you share anything mission critical.

Re: One year as a solo dev building open-source data tools without funding

#65

Advice regarding VCs: Don't ever talk to them if they randomly approach you saying they "really like what you're doing". They will gladly sent an associate to talk with you about your business in the greatest detail and ask you to share presentations, demos and metrics. Anything you give them will then get passed along to their own portfolio companies in your space. So don't feel flattered when they feign interest in…

If intel in your company will kill your business you don’t have a defensible business.

This may be true after a certain point, but is certainly NOT the case when you're just getting started.

Re: One year as a solo dev building open-source data tools without funding

#66

Advice regarding VCs: Don't ever talk to them if they randomly approach you saying they "really like what you're doing". They will gladly sent an associate to talk with you about your business in the greatest detail and ask you to share presentations, demos and metrics. Anything you give them will then get passed along to their own portfolio companies in your space. So don't feel flattered when they feign interest in…

What's stopping you from asking them to sign an NDA before disclosing any details of what you are doing?

Re: One year as a solo dev building open-source data tools without funding

#68
post #67

Is it possible to do more SQL over CSV in the browser? I'd love a simple browser app that I could drop a CSV file into and write SQL against. Right now I use `j`, but its a bit clunky.

Yeah! app.datastation.multiprocess.io supports this!

Here's a demo video: https://www.youtube.com/watch?v=_7LEV3ZeQWU&feature=youtu.be

Re: One year as a solo dev building open-source data tools without funding

#69
post #66

Advice regarding VCs: Don't ever talk to them if they randomly approach you saying they "really like what you're doing". They will gladly sent an associate to talk with you about your business in the greatest detail and ask you to share presentations, demos and metrics. Anything you give them will then get passed along to their own portfolio companies in your space. So don't feel flattered when they feign interest in…

What's stopping you from asking them to sign an NDA before disclosing any details of what you are doing?

How are you going to know they betrayed you?

If you know, how are you going to prove it?

If you can prove it, how are you going to litigate it?

NDAs only real usefulness is for big players to legally bribe and contain small fry.

Re: One year as a solo dev building open-source data tools without funding

#70

If you can, it is always better to go full time. If you hourly rate is 150$ (in the market), and you can work 300H a month (including weekend) (It should be 400 hours - 13 hours a day). Than you are basically making around 70-100K a month (in value), but paying only 4K (in cash, your living expenses). Of course, if you are 2X, 3X , 4X engineer , you are basically making 300K a month for 4K cost.

You are saying never start a startup? If you don’t want to take a risk on a startup, you’re much better off taking a salary job than trying to get a high hourly contracting rate.

Strange analysis, these numbers mostly don’t add up. People contracting at an hourly rate almost never get constant consistent work, otherwise you’d get hired on a salary. You have to spend half your time looking for work, and you’re not accounting for that at all. At 400 hours/month, you are suggesting working 90 hours per week for 365 days per year. Having worked this many hours before for stretches, I know first hand this is a recipe for complete and total burnout and depression within a few months. And even 90 hours per week at $150 per hour doesn’t add up to 70k/month, it’s 60k/month. 2x/3x engineer is usually referring to productivity, but not pay. You generally can’t increase your pay by being more productive. Pay scales that you’re talking about ($300/hr, $450/hr, $600/hr) are extremely rare in engineering and come only with niche software markets. Almost nobody is making hourly rates like that, there’s nothing basic about it, this is an unrealistic goal.

Post reply on HN