Hacker News new | past | comments | ask | show | jobs | submit | JAlexoid's comments login

I'm pretty sure that he didn't liquidate $50bn in stock to get the money for buying twitter. (That $50bn includes the 20% capital gains tax, that leaves $40bn in cash)


Yeah, that is my point: you don’t need to fire-sell to get fast cash, you can just use your capital as collateral.


That's pretty cool.

- What did you use to prototype your project? What software and what companies offered prototyping services for your project?

- Was it hard to get the whole machine made? How is the market for small scale manufacturing?

I'm asking because I have some designs, that I never materialized - because there were no companies that would mill a one off item.


Thank you!

I used fusion to design and printed ergonomic/partial prototypes on Prusa 3d printers. Then, I fortunately had a ton of manufacturing contacts because I have worked as somewhat of a production engineer before. Some parts were definitely difficult, especially the outer burr of the grinder (there were a couple viable ways to make it, but it is sometimes difficult to find a shop that is price competitive in say wire EDM machining and 5 axis CNC, or CNC and casting, so you have to get shops to coordinate with eachother) or the wood arch (because high volume wood shops are not nearly as technologically sophisticated as metalworking shops)

PCBway is a good option now, especially for 3D printed metal parts. They have CNC as well but they tend to struggle with anything that has complicated geometry or features. But 3D printing doesn't require approval, and for one offs is often cheaper.


> Personally, the low-tech solution of a plunger stuck to my forehead with a klondike bar dangling from the end has always worked for me.

Or you could borrow someone's labrador retriever and have the dog pull you. They like to go real far and real fast... and you get to practice hard turns.

> I HIGHLY recommend favoring trail running over running streets/sidewalks

As a triathlete - I would add something: for me it's more a case of running on soil, over a hard surface. Trail running may take you to a stony path, which is as bad as pavement/concrete.

But in the end it's training your running form to be the best it can be for running, that matters. Running uphill helps to naturally train a good form, even if it's significantly harder.


> Or you could borrow someone's labrador retriever and have the dog pull you. They like to go real far and real fast... and you get to practice hard turns.

You only need to be concerned about hard turns if the dog is untrained, afterwards, they're the best running partners you could ask for. Come visit us at https://www.reddit.com/r/RunningWithDogs/. Lots of suggestions for harnesses for the dog (mandatory, IMO) and waist leashes for the human (highly recommended).

If you own the dog, they can be a great source of encouragement, too. They'll bounce with excitement any time there's a possibility of going for a run, and look at you with big, sad eyes when you instead sit on your phone.

My old girl and I put in 20+ miles a week, 50 weeks a year, for a little over 8 years, or a little over 8,000 miles. That's a lot of M&Ms!


I completely agree. I used to live about 10 minutes from the beach, and I would do sprints up and down on the sand. There's not much that's more humbling than getting completely gassed after a whooping 60 seconds of running.


You're right... Companies should pay mid 6 figures, as well as downtime for training.

Short answer is that most corporations don't have a job in training people.


I can't tell if you're being facetious or not, but the fact is that, when Boomers and Gen Xers entered the workforce, formal training was provided for many entry-level professional positions, and even for higher junior-level ones. This was particularly so when the company was using unusual or uncommon technology. GP was complaining that "no one has any experience in our technologies." That speaks to an underlying entitlement, not just to employees' time, but to prospective employees' time. It's part of a broader shift of the cost of doing business onto everyone but the business (labor, customers, vendors, government).

Companies should pay what it costs to get people to give up a significant portion of their lives working towards their business mission, or else get out of the business.


As someone who went though the legal means when he was in the office last time, he will primarily hurt the legal immigration... because that is the easiest thing for them to do - grind USCIS to a halt.


Well.... DUH!

You're comparing the vast swathes of mediocre talent to the best from the rest of the world. Of course the top talent from elsewhere is going to beat the average talent from the US.


I literally quit my previous job, because people were hired after "a few Coursera courses".

Sorry, if you "learned online" and haven't spent a few years building software - you aren't immediately as qualified as a graduate from IIT.


> H1B visas suck for IT and software workers.

H1b only sucks for short sighted people. Places like India would in any case have more software engineers available, than the US. Moving and hiring best of Indian engineers in the US kept teams operating in the US from being offshored wholesale.

Software isn't a car, doesn't require physical transportation.

An understaffed team in the US would be worth less than an offshore team with offshoring overhead.


I am an individual not a corporation, our interest don't align in this manner.


They are saying that your individual salary would be lower without the additional talent.


>Any offspring also doesn't qualify for citizenship.

Literally anti-constitutional.


"My moral compass is whatever the law says" also it is a amendment to it.


Fist - it is not companies' responsibility to train anyone. It is not their business.

Second - H1b are exploitable, because the system allows it.

H1b has demonstrably not suppressed software engineering wages at all.

Non-competes, have - on the other hand.


> H1b has demonstrably not suppressed software engineering wages at all.

That's simply impossible; it's basic economics.


The lump of labor fallacy is usually covered in “basic economics” classes. There are multiplier effects from clustering of certain types of skilled workers. This increases overall demand and thus overall compensation for everyone in the market.

This is why ending the H1B program like posters propose here would be profoundly stupid - if companies can’t staff their teams here, they will staff them elsewhere, and either stop hiring here or close up shop entirely. This will lower salaries and increase unemployment in the relevant fields.

You already see this in microcosm due to real estate costs serving as a brake on internal migration, many companies have moved all net new hiring out of the Bay Area.

Now admit too many foreign workers at too low wages and you will hit diminishing returns, but we are way short of that point, especially if we can manage to curb abuses of the existing program.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: