They're both forms (perfect passive particle in particular) of the latin verb "video". So they both mean "having been seen". The difference is in gender. visa = feminine; visum = neuter; visus = masculine.
Check out OneSignal (https://onesignal.com/)! We offer SMS both as a standalone service as well as part of our omni-channel offering.
We offer both a seamless experience for both developers and marketers with a clean, robust API and a fully featured dashboard.
Indeed we have templates for SMS that your team can share and edit without you getting involved. We have quite a lot more than that as well, e.g. see our Journeys product.
Feel free to reach out to me directly for questions or feedback!
They came in at #13 on that list. While traffic's bad in Boston, commuting via public transit is actually a viable alternative. It's very dense and has a solid commuter rail system in addition to an expansive (if aging) subway system. It's also very bike / pedestrian friendly.
Heh, as someone who came very close to doing this (i.e. using k8s for a LAMP-stack type app at a startup), it's not just "shiny object syndrome" driving people to do this. Here's what our progression looked like:
1. Start with basic LAMP app in git that's manually deployed to an EC2 instance
2. Add in CI / CD + CodeDeploy
3. Create a staging environment
4. Dockerize local environment to keep dev environments in sync and onboard easier (really, this part's a gamechanger for a small company)
5. Ok so now we have Docker for local dev environments but stage and prod are managed separately. Can we just run our Docker containers in stage / production?
When I researched step 5, the options were basically k8s or Docker swarm but Docker swarm didn't seem battle tested (for prod). k8s was clearly a nightmare for a small team to maintain so we started looking into GKE / EKS -- but EKS was still in beta. Thus we punted. We've actually started using ECS for a newer project and I'd likely go that route for step 5 instead.
Yes, retargeting and tracking is extremely effective.
You've fallen into what I'm gonna call the "HN fallacy".
- I would never click on an ad, therefore no one clicks on ads.
- I don't have a need for a better file syncing UX, therefore no one would ever use Dropbox.
- I don't see the point in crypto, therefore no one would ever use Coinbase.
Specifically, let's say you've seen 100,000 ads in your lifetime and literally zero have had any impact on you, much less driven you to click through and purchase immediately. It's reasonable for you to question the utility of these ads.
There are, however, entire populations of users whose behavior is vastly different from yours. They may be very willing to click through an ad to purchase.
A good marketer will only target their ads at the people most likely to purchase (i.e. not you). This puts you on a negative feedback cycle where you only get ads from companies that are spray-and-praying or too unsophisticated to target their ads more specifically.
Chicago's a very nice city. There are basically three main factors keeping the cost low currently:
1. Population decline.
2. A very large amount of good housing stock. Chicago's completely flat with solid public transit reaching out to the suburbs.
3. Lower proportion of tech and startups. Similar to how tech has driven up the CoL in many cities, the relative lack of tech in Chicago has kept CoL down.
Winter is rough in Chicago, but the CoL in Boston has skyrocketed which invalidates that as being the _only_ reason.
A large portion of jobs in the bay area are in Silicon Valley which is south of SF and comprised of cities like San Jose, Palo Alto, and Sunnyvale. For someone seeking the amenities of a global city like SF, none of the other cities in the bay area come remotely close. They're all generally quiet, clean, suburban locales except San Jose which is a sprawling mid-sized city but still nothing like SF for someone wanting a world class city.
Some places have a contract-to-hire approach which is effectively a trial period.
I believe companies fall into two basic structures:
1. agency / consultant model - implement short-term projects, specific tasks, etc. It's easier in this approach to swap employees in and out as new projects start.
2. software product model - the company's entire business model is built around or highly dependent on internal software projects. Institutional knowledge is very important. It's really important to protect the product process and plan for the long-term implementation of strategic vision.
Contract-to-hire works well for #1. But for #2, the overhead and cost of disruption to the core process is too high. Top-tier software products require a relatively smaller number of highly engaged and skilled people to drive projects to an optimal point. These people need to also be directly involved in hiring and onboarding to maintain the culture and high standards. Bad hires can destroy such a team. Thus you end up with the current interview processes as they're efficient and err on the side of rejecting qualified candidates accidentally. If they spent 10x as long on hiring, they could improve the accuracy, but then they wont have as much time to build product which is the key tradeoff involved.
Bright Cellars is the data-driven wine subscription that matches users to wines. On
the engineering side, we have two core teams: eCommerce and Data Platform. In addition
to being an eCommerce website, we're building an internal data platform to drive indsustry
insights and optimize our operations, marketing, and wine branding initiatives.
It's an exciting time where we're growing quickly and have a number of interesting
technical problems to work on.
The legislation being enacted's main goal is to keep people employed. The PPP (payment protection plan) is directed at small businesses (< 500 employees) and can be forgiven if it's used toward payroll, rent, etc. In order for the loan to be forgiven, in the 8 weeks following taking the loan out, your employee headcount "cannot decline from average monthly levels during 2019 or during the past 12 months" [1]
Now, the larger company / industry bailouts -- those seem less well-defined. I haven't seen the latest on those but I'm sure the government would _like_ to tie them to employment as much as possible but we'll have to wait to see.
"dying" is hyperbole. The manufacturing sector has been on decline for 40 years but other sectors are starting to build up. The downtown core has seen a boom in revitalization, particularly these past 5 years. There's a push for tech and startups.
It's basically in the same metro area as Chicago. Would you say Chicago's dying? It may have declined (or not grown as fast as other US cities) lately but "dying" seems like hyperbole, no?
Oh, I agree with your post and appreciate you adding real substance to this thread. I'd say the area's in "decline" as opposed to "dying" but that may be splitting hairs. I do think "dying" implies that there's no hope for revival. Like it's some remote coal town that lives or dies by that single industry. Sure yeah, the manufacturing industry is not doing well here and Racine has fared particularly poorly. That made Mount Pleasant vulnerable to Foxconn but is only one part of the story. There's a lot of political nuance when it comes to Wisconsin and Milwaukee. This deal wasn't getting done without the state government backing it no matter how naive or desperate one municipality was. My point is that it's far more likely corruption or even just normal political incentives drove this deal as opposed to stupidity.
Just to jump in here to add some additional comments:
* Mount Pleasant WI is not rural (city-data.com says 95% urban). It lies on I94 just 1hr 15min from Chicago and 30min from Milwaukee.
* I doubt Mount Pleasant WI is dying.
If I remember, the deal was pretty opaque and many details were murky. I find it more likely the local officials were incentivized somehow as opposed to sheer incompetence.
Additionally, it should be noted that the WI governor (Scott Walker) who orchestrated this deal lost his re-election bid shortly after this. While there was always uncertainty about Foxconn actually following through, the lack of Walker (and thus probably Trump) basically sealed the deal.
In my experience, a great founder should be good all three of these: 1) thinking fast, 2) thinking slow, and 3) knowing when to think fast or slow. It's easier to determine if someone isn't great at thinking fast (or doesn't know when they should think fast), for example if they don't respond quickly to an important email.
I don't think this is a binary thing. Moreover, I think the ability to meld the two and manage the balance of decisions across a growing number of stakeholders is one of the biggest challenges for founders.
You can negotiate with Stripe if you're at high enough volumes. It's likely that the "best" choice of payment processor is heavily dependent on the specific business in question. If you need agility and developer friendliness, Stripe is hard to beat. If you're trying to grind out every last percent of margin, you'll have to shop around and see what you can negotiate (and the offers you get will likely depend on the nature of your business, chargebacks/fraud, etc).
I was frustrated with this exact issue for years until I bought a TV antenna a few years ago. Super Bowl, NBA Finals, etc are all on there, for free, in HD. No lag or interruptions either. It's also nice to just flip through the channels every now and then.
Probably both, I'd imagine. Regarding cost, Stripe was pretty outspokenly against Prop C in SF last year (which passed, to their dismay). The result is an added tax on revenue which hits Stripe hard since they have a high volume, low margin business. Not to mention CA is already a very expensive place to run a company.
With rising costs in SF, they likely had to explore viable long-term solutions. They can start moving more jobs to their other offices, open new secondary offices, or expand their remote presence. With remote, they're able to keep SF as the HQ while lowering costs. It's also popular among devs, so it'll keep their brand image good amongst their target demo and among their current employee base.
Basically, there's a ton of completely unqualified (or even under-qualified) applicants who apply to just about every job opening out there. If you've ever been on the other end of the table, posting a job opening and sifting through applicants, the situation becomes clear very quickly.
I'm actually surprised 250 make it past their initial screen. The rest of the numbers seem reasonable to me though.
It's pretty interesting -- as a startup founder leading a dev team of ~10 people now, I've hired almost all junior level candidates. We never had a posting for "Junior Software Engineer" though. We just had one posting and considered everyone who applied separately and within the context of their experience.
At the risk of coming off as pedantic, Olympic marathoners DO run 5 min mile marathons very regularly (the world record is at around 4:41 pace currently). That said, I fully agree with the comparison of startups/businesses to marathon running. As someone who does both, the parallels are really interesting.
The hardest part of running a marathon is training -- hitting mileage goals, pushing yourself during workouts, prioritizing running above social outings, staying injury-free, and staying healthy. Not to mention the occasional psychological hurdle and hormonal changes. It really lines up quite well with the startup experience...