HN user

MaknMoreGtnLess

98 karma
Posts4
Comments113
View on HN

Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ or python 3.5+, and you need to be able to connect to the machines over ssh.

I understand what you're saying but do understand that to other people these can be concepts that they arn't familiar with or might actively struggle with

That said - were there any obstacles you faced when you started with Ansible?

What could have been better (tooling/docs/training/etc) to get you upto speed better/faster?

I want to learn from you more.

What if I gave you 2 docker containers:

1. one with ansible loaded and ready to go

2. another one with just SSH running that you can point the above to and experiment with

If you don't know docker - that's ok! It's easy and I will set you up to do that. let me know

This way, you don't have to mess around with either installing ansible or setting up VMsVPS/hosts blah blah

Much of the job that ansible or other config management tools might have done is handled by docker build to bake container images, and k8s to manage custom running services

OK but there has to be something that executes the docker build and then kicks the jobs off - right?

What's that tool at the $dayjob?

why go through all the trouble of setting this up instead of just using AWS

1. Have you ever hosted something on AWS, for public consumption by parties not under your control, where you, personally were footing the bill?

2. Have you ever hosted something on AWS where a misconfiguration on your side and/or upset/impatient customer caused a bill so large that you had to shut the company down?

AWS will scale to fill your bank balance, irregardless of whether you can afford to pay for that scale. AWS is great for elasticity when you can afford to pay.

AWS has no functional bill limits, even after 10 years. For those who post a link to the AWS bill limits havn't actually handled any meaningful scale, at which point a set of dedicated servers is great value.

Would this be possible using SQLite:

- I point it to a bunch of JSON files on disk. They have similar schema but not exact (slight variations)

- I SQLite import them into one virtual table (I would rather not literally import them - think PostgreSQL JSON FDW)

- Then index certain fields so looking up records by certain fields is very fast (faster than having to "FTS" through all the files)

- Allow fuzzy text search on certain fields (say a field was company name and other fields were city, street and human names)

All the while (best case) not actually having to import the files into the DB (it's ok if the indices need to be rebuilt everytime)

I meant that now we never hang out, we don’t trust each other any more, and code review has suffered as a result. It’s especially hard for new people joining a team where baseline trust is basically equal to that of Internet stranger.

Huh. How's your hiring process like? Do you hire very young people?

The only time I've seen this happen is when the team used to work in a colocated manner, and then some members started to WFH. Eventually some of those people WFH got too tied into the "home" part of WFH and work suffered. Simultaneously other people in the office just started to treat those WFH as second class citizens as well. This really caused a mess.

If this is what you're seeing, the easiest solution is to just move to a remote only team.

If you want to stay, you need to have a good manager in place who understands these dynamics and can mitigate issues.

Ha ha haha - EXACTLY to the last dot!

I am terrified of where we are headed as a society. I get that writing blogs are more time consuming than tweeting but for the consumer - is this content really valuable in the long term?

I don't have a Twitter account, but I view posts and threads simply by opening Twitter links in a private browser window. Does that not work for you all?

No. After a while there's a huge modal layer asking me to log in

It’s more common than you think

I didn't say septics are uncommon. To ask you differently:

- How large was that plot (on which the septic system was installed)

- Was the septic system dedicated to your house or shared

- How large was that septic system

Well the question is not just for this idea but for any idea, how do you know if a problem is big enough to be solved.

This is premature optimization. How many datapoints do you have so far?

Did you interview 50-60 of one persona yet?

There is no one answer because the detail completely lies in the specifics, which is why I asked you those questions. You seemed to have missed those questions.

And how do to proceed when there are mixed signals when talking to customers.

There's no mixed signals. You're uncovering personas.

Each persona outputs a different but unique signal.

Segment them. Then try and resonate with 1 to max 3 personas depending on your mental bandwidth and resource ability.

By the way, how did you learn to do market research first before building a product? You're already ahead of the curve and very likely to be successful than most first time founders I've seen

Every day there are posts here with some Twitter thread as the source

These threads are extremely and overwhelmingly popular and that surprises me.

These threads always start off like "Here's how to make $100MM in 10 hours" and then multiple sub posts of most generic nonsense I've ever seen.

What's even interesting is people think they get tremendous value out of there and share/re-tweet and go crazy about them.

Am I really stupid or are most people on Twitter who engage with these threads on some kind of hallucinogen(s)?

While I am happy to go into TAM and related metrics, I am assuming this is your first successful startup.

In that case, don't worry about the market - infact, having just a few dozen paying customers who can be fit in 1 to max 3 personas but those that you understand very well, can reach well and get immediate feedback from is very important.

I've conducted a small survey to identify a probable market for a problem before started building anything, and it turned out to have mixed results.

- How exactly did you conduct the small survey?

- What kind of questions did you ask?

- Did you use a form or conducted 1:1 interviews?

- How did you source the participants?

- What was the motivation of the participants?

Like 55%-45% split

split of what?

Is your solution a whisper idea? Or can you share it?

Rude

Money doesn't just disappear if you don't spend it, you need funds to live, not income.

It does. It's called inflation.

Don't be an asshole on the internet. There are bigger assholes on the internet and they can outwit your smart ass replies trying to belittle someone who hasn't been an asshole to you and was asking a genuine question.

The hardest thing about remote work is code review.

code review was done async. and in all practical sense "remote" at all the dozen places I ever worked in an office.

How else do you scale code review on a team of more than 2 people. Get all 5+ people in a room to do code review for a 5 liner?

We don’t have to be best friends, but yes, showing up is part of the “teammate” package. You don’t get to withdraw that part and still demand all the same things from me.

… but they arn't.

The person who has meaningful and deep relationships outside work isn't demanding all the same things from you.

Most work are in dense cities and cities are inherently expensive. For the commute to be meaningful, everyone in your team has to be within a short distance of these dense cities.

The “teammate” package you propose is pretty expensive all things considered. You might not realize nor care about the expense but the teammates might.

In the end, the company cares about productive output. Mercenary or not, companies that have the most productive output that makes the customers happy are going to win.

My money are on companies that go remote, keep costs down and pass on those savings internally (employees) and externally (customers).

My money is not on companies that are forced to hire people within driving distance of some arbitrary office.

Setting up a platform/cloud agnostic PaaS that a scrappy preproduct/early stage/pre-revenue startup can use without incurring large, spiky, unpredictable costs.

Because at this stage the startup has too much going on, this PaaS is very low overhead - so no Kubernetes complexity.

Think EC2/EBS/ELB at flat predictable rates.

understood.

What's the design pattern you recommend Temporal users use to implement multiple consumers?

Usecase: Handle a large, spiky backlog by dynamically sharding the consumer input, starting and putting multiple consumers to work until the backlog is within nominal specs.

Eg: Shipping orders during a sales event. Each S&H order takes the same response time but multiple S&H orders can be parallelized and there are a few hundred thousand orders pending. Of course, S&H order can fail, in which case they are restored to the pending state after a timeout or loss of a lock

That's fair but I have a question:

If I DID want to get access to the event sourcing mechanisms under the hood - can I?

My hypothesis is that I can use Temporal to implement high quality DDD pipelines that follow CQRS - having explicit access to the event sourcing mechanisms would be fantastic!

Otherwise, it's an issue as most DBs can be argued to use some form of event sourcing mechanisms under the hood but they arn't built to be exposed outside the DB - hence an event sourcing mechanism has to be reimplemented (hence pitfall of homegrown ES systems).

What are your thoughts?

OP, Will you consider allowing download of the actual dataset? (WikiPedia style)

If not, what would hold you back from doing so?

I would be OK hosting a mirror of this service including the infrastructure (and handling the associated costs) if it helps.