Hacker Newsnew | past | comments | ask | show | jobs | submit | jgr447's commentslogin

Any data supporting the appreciation of 4% a year?

This seems socially much more acceptable to taking a loan and then invest the money in stocks for example, but to me is not that different.

True the volatility is much lower, but so is the liquidity if you have to dispose of the propery in a short time due to life circumstances.

If this is a single property and plan is to be the bulk of one's net worth it seems risky to me.

Then there's the "dealing with tenants" variable which can be none to a ton of work/hassle.

REITs are imho an interesting way to get rental income with less hassle and much more diversification if you can stomach the stock price moving up and down.

Look at Vanguard VNQ for example.


> Contractors still do a bit better than employees

Curious if that is actually true when comparing to tier 1 banks/hedge funds full time employee salaries+bonus+retirement+healthcare.

Assume 600 GBP/day * 22 day/month * 10 months (realistically) full time work, that's 132k/yr.

From that take out accounting, illness, insurance, healthcare, retirement, travel, possibly more.

All things considered, once you get above 100k base as employee contracting becomes less attractive. Strictly as a money move that is, there's other dimensions for sure.


600 seems low - I earned a lot more than that back in the day, and that was a long time ago. A quick search of jobserve.com for just "java" found roles quoting up to 750 on the first page, and if you're any good that'll be negotiable. And if you get into even slightly niche things (Oracle Coherence, in my case) the rates are much higher.


I don't think it's very far from the reality of your full stack app developer though.

Ie. 900+GBP/day is listed rarely and for very specific/niche things.

Then, the more niche it is the more likely it is that the downtime between contracts becomes longer I imagine.

Curious what your anecdotal experience has been, to the extent that it can be shared.


Before rdbms became a commodity, companies would build them in house and required very specialized skills.

Then it became a commodity and now you can just use postgresql for a basic web app without knowing much about dbs.

Start adding scale and availability requirements in the mix, and you're back in need of specialized knowledge on indices, query planning, disk access patterns and db admin in general.

Same for cloud providers imho: you can throw an app online quicker than ever before, but as things get more complex you will still need an understanding of infrastructure, network, availability, security etc.


Not having used it in any meaningful way, after a lot of reading I am sometimes still unclear with the value proposition.

The value imho could be in being able to package distributed applications and deploy across cloud providers or on prem, seamlessly.

I don't think this is true though short of doing a lot of effort to abstract access to a gcp/aws/azure managed service (say, a db), which is probably a bad idea.

If you take that away, then a lot of the replication, autoscaling, load balancing, failover etc. can be implemented using cloud providers without having to manage the complexity of k8s.

Hope to be proven wrong here.


Looking distractly it seems one of those "hot new javascript frameworks of the month" infographics.


> Kubernetes isn't supposed to be simple

Disagree, it's a tool designed to abstract away the complexity of deployment and operations, simplicity of use/management sound like should be a design goal.

It will probably get there but for now it's hard to disagree with the "complex" label.


+1 on challenges in enterprise environments for local container-based development, this seems an unsolved problem for now

iterating on docker-compose might be easier/faster locally, then pushing to a dev k8s cluster for testing in ci/cd

curious if people are using k8s locally and why


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

Search: