chrisgoman

Vagrant

Thanks, will take a look at that curl thing. We are still using this and been working for us for ~15 years (python 2, ported to python 3) and this is just an example of how to take https://fabfile.org to the extreme but still is not the best way to do it. We only ~50 servers so it is not a massive fleet. The convenience of typing `fab <env> <role> <task>` to do things under control is still better than nothing :)

Strongly do NOT recommend what we are doing

- https://github.com/chrisgo/fabric-example

- https://github.com/chrisgo/fabric2-example

Fundamental no but mechanically yes. GCP is more abstracted IMHO so you are in some areas "higher" level, AWS has lots of super deep stuff like all those policy configurations for IAM, etc. are VERY different. You are already ahead of the game because you are using Terraform and not vendor locked in to something like Cloudformation

https://forum.leasehackr.com *was* good, now a lot more "deals"

You mean how do you report google's customers (they pay google to show ads) to google so google can cut off their own revenue stream?

How about the reverse of this? Had to let go of 2 people because I do not know how to hire (apparently) as the people I hired looked good on resume, did ok in interview (but I may also be bad at that) but could not really perform the work ("simple" LEMP stack)

Digitalocean Spaces uses Ceph as their backend and it is NOT stable (at least with s3fs), had to migrate away from it and could not do a full-stack on DO (aka "no AWS") and had to swap in Wasabi.

I think this is mostly true but depends on the industry and "critical mass". If you have enough people, then letting people go and then filling in with OT hours (remaining people) is still more cost effective all things being equal (some people may actually welcome the OT hours here and there) and not chronic understaffing

This is most likely what is happening is the shopping website and AWS are now trying to make you create at least 2 accounts and the captchas will start showing after that

You are your first client?

Specially for regulated industries and if the company you work for has clients in regulated industries and up the chain of clients. What if somebody steals your laptop with NPI/PII data. As with a lot of things, a lot of stuff only matters when things go bad (like somebody stealing your laptop)

They are most likely going to leak the list of people that requested the breach settlement checks :)

A COO only has 3 high level things to do (sounds easy but is really hard because it is a blank slate)

1) Figure out what needs to be measured (KPIs, metrics, etc) in specifics

2) Be able to measure items listed in step 1 accurately and timely

3) Make changes to improve what you are measuring (efficiency, volume/counts, speed/rate, etc)

Keep repeating steps 1 to 3

We use ACH Pushes to pay our contractors

Save 50% of all the revenue for taxes

too many crappy websites, probably needs a "committee" to whitelist domains (only good quality ones) but probably too much work for not enough money or needs some monetization strategy

homebrew is the BEST!

using fabric for deployments (fabric2 kind of a pain but almost got most things ported over) even if our main app is in PHP

The point is that your ENTIRE team will be in Europe or Singapore so there will be no time delay between them ... the US team/person will be the odd man out

If you want a "safer" financial outcome, quitting your job and starting your own thing is NOT the answer.

If you can do your product without raising money by actually making sales (bootstrapping) and making a profit every month, then this is more "safer" than raising money as you will lose control over your financial outcome. The successful ones (there are not a lot) get a lot of press but there are a lot more failures with raising money and then figuring out profit

Do other "fun" things, learn to sail, learn to fly a plane, learn to cook

It is better to be a developer that ships! That would mean you have some generalization so you can start-to-finish and then you can specialize in one of the steps between.

Based on what you wrote here, you do not need to learn any more things by reading -- you need to start DOING. *EVERYBODY* will be happy with "starting a self-sufficient small cash business" but that is easier said then done and you will never get there until you do it. BTW, you may lose money also, that is entrepreneurship/startups so you are overthinking it. If you are risk-averse (aka you have to "learn more" before doing something) ... then entrepreneurship/startups may not be for you -- and that is OK

You are on the right path with the steps you outlined above but there is NO holy grail or "the path" (I'm sure you've read enough and all the paths are different) so everybody has 24 hours per day to do something so you just need to do "enough right things". The lean startup model is good because you do not have to wait for "funding" (may never come) and you can just start doing something.

You may have to fail a couple of times to get it right -- again, that is OK -- this is how entrepreneurship/startups. So the first thing you really need to get right is "Do I want to do this?" Entrepreneurship/startups is NOT a job where you get PAID to do X (and whether it works or not, you still get paid). This is a lot of ups-and-downs but mostly fun journey if you are ok with taking risks.

Good luck!

Mercury is not approving all applicants for some unknown reason and they can NOT tell me why

Here's a business model

https://techcrunch.com/2020/10/06/nivelo-nabs-2-5m-seed-to-r...

This is why a lot of places don't accept personal checks. This has been around for decades "bounced checks" - NSF (not sufficient funds), REFER TO MAKER, STOP PAYMENT, etc. Not only do you not receive the funds, you are fined by your own bank.

It is a crime in most states (keep the returned check handy) https://oag.ca.gov/consumers/general/bad-checks but kind of hard to enforce

If your goal is to create your own startup, the technology doesn't really matter. Unless your startup is a "mobile app", then that is also not important today. As with most suggestions here, your best bet is to start with web dev (like you have mentioned) but don't get sucked into the hype. You could do a lot with Rails or PHP (this gives you a solid understanding of some foundational stuff)

- Internet: Domain names + DNS + Hosting (VPS is enough)

- Web Dev + Backend: Nginx (web server) + PHP-FPM (PHP) OR Unicorn (Rails)

- Database: You will need SQL no matter what other people tell you

- Front end: HTML, CSS (Bootstrap), Javascript (jQuery)

These are the most "boring" things you can learn but you won't spend weeks just getting your environment going and you are already frustrated. All the cool stuff deals with async, PWA, SPA, NoSQL, (... insert more buzzwords here ...) that will just confuse you before you even get a login page up and running.

Your goal is to be able to create a functioning "web application" that may already exist so you can just "borrower" the features and not have to think too hard if learning coding and technology is where you are at right now.