deedubaya

> It's perfectly okay to mostly ship HTML with minimal JS

Some might even say it is better to mostly ship HTML with minimal JS.

ducks

I've been avoiding starting a project myself which will require SFTP. Passing text files around via SFTP is how a lot of the world works. It's still painful to implement this, and makes the transfer of data slow (polling for new files to process etc). This introduces a big delay in any data feedback cycles. Managing users with system accounts is painful too.

This project looks to alleviate a lot of these problems.

It'd be great to be able to register webhooks so that it could send events to external systems. Ideally I'd like to know when a file is created/deleted etc without having to walk directories on the sftp server on a regular basis.

Looks neat. Definitely a developer-designed UI.

Of course there is risk in starting your own venture. It’s not a guarantee of success, but the upside is exponentially greater.

Chasing (relative) peanuts is still a better call for most.

Yup, that’s the hardest part for sure.

Developers are highly paid because their knowledge is highly leveraged. Someone else is benefiting from your application of knowledge by an order of magnitude of what they're paying you. Why be the cow when you could be the dairyman?

As someone who hires software developers, opening positions up to remote employees allows us to get the best bang for our buck.

We can hire top talent for our given price range without geographic restriction, save on costs (no desk, office, etc), and retain the employee longer.

There are downsides, but they're 95% managerial issues.

This was really cool to look at. This was really educational having grown up in a rural area where (I thought) no one of consequence came from. Thanks for sharing!

Stripe has written https://sorbet.org/

Take sites like these with a grain of salt. Given the total lack of validation that any of this data is from real employees, there's not telling how (in)accurate this site (and others like it) are.

This particular site seems to be a marketing piece for TripleByte. Perhaps the makers can comment on the accuracy of the data?

Cringe.

Solo entrepreneur full-rewrites are almost always churn inducing, feature stagnation, time sucks.

I'd advocate working on improvements to the current platform, one-by-one. Focus on features that increase your bottom line until you're at a MRR where losing 30% of your customers will be worth the cost of improvements.

How about a Premium feature list on the pricing page?

Your resume URL 404’s

FUD

I'm guessing its the salt water that is the problem.

They're reading into this too much. Top talent likes

- Remote work

- Ability to contribute to "moving the needle"

- Profitable, which probably means decent pay

Most of the time, it isn't what you know, but who you know. It's unfortunate.

I love DO, but man in practice the CPU performance of their machines have been horrible in my experience. Like 2-3x worse than the same $ spend on ec2.

If you like the idea but lack the ability to build your own van, check out https://www.syncvans.com/. They make some really cool rigs.

Reading https://sockpuppet.org/blog/2015/03/06/the-hiring-post/#work..., it looks like your process is better than most!

However, I've walked away from interview processes that require a work sample that'll take more than a few hours or require lots of domain knowledge to get started. It just isn't worth my time, especially as a barrier to entry before talking to anyone.

Things I am happy to do to see if I'm a good fit:

- Pair with a developer on the team. I learn just as much about the team I'd be joining as the hiring company does about me. - Talking through code that I've written, talking through how I came to the implementation and how I might refactor/enhance further. You can't really bullshit this without the interviewer being a nit.

Things I'll do as a 1099: - Fix a real bug - Refactor real code - Do a project that isn't trivial, start to finish

If fraud was committed, the right answer would be to sue the applicant in small claims court for the cost of the ticket. Canceling their flight was just a petty move.

Your HN Post title sucks, extension looks cool tho.

I bet it sucks that the user didn't get a warning or notification...

...but as normal user of email, I appreciate a heavy hand when it comes to email lists which mailchimp deems malicious or bad for its ecosystem. It's no secret that mailchimp maintains a high standard for the quality of lists and email it delivers. The common thread in these stories seems to be malicious actors, poor/spammy content, etc. So I'm not sure it's so bad?

Has anyone with a "typical" (e-commerce shop, saas newsletter, etc) mailchimp list been shutdown without notice?

I’ve stopped using a number of products because the underlying Plaid connection to my banks would routinely break and take weeks (!!) to get fixed. It got to the point that functioning connections was a rarity, and things not working was the norm.

I want Plaid to succeed and I want to use those products, but beware of building something on top of Plaid; you may be driving customers away.

Forest fires (used) to be a natural occurrence which was healthy for forests.

70 years of "put every fire out" has resulted in forests with excess fuel. That coupled with dry spells and warmer temps = a powder keg instead of natural burns.

When they say "let it burn" they don't mean wildly out of control like the Paradise fire. They're talking about letting it burn under optimal conditions, where crowing and running are less likely to happen, to consume fuel that could burn sub-optimal conditions where there is little chance of control.

Less fuel = less intense fire = more likely to control.

What's the use case for this? Maybe being able to bulk-import relational data?

>Outside of the room, the Engineering team laughs at your questions, Operations and the CEO give each other quizzical looks before laughing too, and they go on to the next candidate.

This is such a short sighted perspective that it's laughable.

Good management will see that the candidate is thinking about joining the team as a long-term commitment and isn't just making a job change for a pay increase over their last/current role. It shows that candidate is showing up for the same reason the company exists -- to be fairly compensated for services rendered.

A leadership team that laughs at these questions are going to lose long-term, and should be avoided by potential employees and VC alike.

Edit: grammarz

This is an excellent break down of OP's situation, which seems very common in tech.

> make it known

This was the hardest "part" of working in a company for me to understand and execute on, especially when reporting to a non-technical supervisor. The thing is they simply don't know where to look or what to lookout for to give us accolades. It isn't as hard as we make it out to be, either. It can be as simple as "I made the common components for the WidgetMaker uniform through out the system, increasing reliability and improving maintainability. This will help us avoid an outage during peak WidgetMaking season so we can continue to make Widgets and operate smoothly", which isn't at all horn-tooty, but gives credit where due.

Fun game!