kovacs_x

there is no time. only the infinity of now. :)

or it's almost as if they sold to someone, just named it differently. I'm assuming if they flop after those 350M, everything (IP, materials, etc) will go to those investors.

For starters- do you even know whats expected from the role or it's more of a fancy title for Lead / Principal Engineer?

My $0.02 on SW architecture is that it's not as much about SW or architecture as about people and their needs and you being able to be effective channel for everything between end-users and engineering.

If there's one thing- learn as much about your business domain from end-users and "business persons" at your company as much as possible!

ps. basically You're screwed! :D

I like the idea, but typically at home when I start giving out weekly allowance "for free" (to our teenager), the quality of mandatory house chores diminishes very quickly! :D

Have you considered it might not be a love of programming you're lost, but other mental health issue?

I mean- burnout, depression, PTSD, ...?

Are there things you're highly passionate about and would want to do instead of software engineering or it's all grey for everything?

imo 'development discussions' is wrong as it creates apparent power hierarchy in the company and very often does more harm then good.

having a mentor and doing regular self reflection is the way to go.

Haven't you thought that they know this already by your ip address? ;)

why do you think it's a bad idea that all small appliances with power requirements <100w have single type connector? (ie. usb-c)

What is you benefit as a consumer to have each appliance have it's own unique cable, generally providing same functionality?

Hopefully EU will decide on that!

Let's be honest- only reason apple has lightning connector is that they can charge the hardware manufacturers.

Lighning port should die. Same as the previous 30-pin connector.

I don't know the book, but judging by the title the author was apparently 110% correct! :D

Sounds to me that being reject was super valuable to you guys anyway and instead of being "accelerated" you'll be able to go in your own speed the way you want with your product, not as YC, VC's or anyone else wants, which can easily "accelerate" you into the void and add extra level of stress to the one already, because imo investors are more like all-or-nothing types, when for you building "normal" sustainable business, that can later be sold for some X-XX million amount, is viable option as well.

Good luck and keep building! :)

World has changed a lot in last 20-30 years, as cold war and USSR did end in 1991 and lot of things changed in Europe and Asia since then.

Valley will never be what it was in terms of global influence, especially if we look 40-50 years back. It's, no doubt, still a boiling pot for next-big-thing companies, but world around the US has grown significantly, especially in the last 5-10 years and there's a big demand for a skills that was not there 10-20 years ago.

my rule of thumb was if it takes 4 hours to develop, I'll always said 3 days, as then You account for some unknown, testing, building / deploying, maybe some refactor after review, etc esoecially as it was for a product that will run for 10-20 years, with changes allowed like once per year. In 60-70% I'd finish in 1-2 days, but in those 30% it's always good to have extra day available for additional development or debugging or anything else or You can always tell You're finished ahead of scedule and feel really good about Yourself! :D

Why You want it as a list? You're doing some sort of research or just out of personal interest?

My $0.02 on this is the more You understand the problem You're solving and details, and more are using the tools and technologies You have experience with, the more correct Your estimates will be. No book or methodology will help You with that!

The more unknowns, the more Your estimate will be off eventually.

It's simple really! :D

Buy a team for $680M? You serious? :)

From my understanding they bought a functioning truck prototype, corresponding IP's AND the team.

Totally.Misleading.Headline!!! :(

Hacker stole $8.4M worth of Veri coins, not Ethereum!!!

Traditional financial systems have established administrative body and practices, risk monitoring systems, fraud insurance and "slowness" that actually helps in cases as these (eg. You very often can undo transactions, by freezing funds somewhere across the world and then resolve those issues later on).

Imo cases like these will be crucial in adoption of crypto currencies and smart contracts. And if there will be no (administrative) safe guards against cases like these, it might as well be the end for crypto currencies, simply because of lack of general trust in them.

What I'd like to know as a developer- what was the "great" idea with the "call forwarding" in specific contract function?!

What would be the valid use case, why author decided he should put it there beforehand?