Put all the compute and battery into a celtic torque around your neck and light weight raybans with full immersion on your face for a $1000 package and they'll capture the market.
Whoever releases a pair of non-clunky glasses with eight hour battery that can do sufficient AR for under a thousand bucks will have the iphone moment and own the world. Looks like a race between Meta and Apple. Unless Microsoft has something sneaky in the works.
I used a nosql database (Cosmosdb) when I should have used a relational database. The Azure cost plus the lost time in transitioning to SQL plus the cost involved in the implementation ran into embarrasingly debilitating six figures.
I was on a savings goal to get a deposit to buy a house to be able to raise my family. I worked hard for the past few years. Then the house prices went out of reach, I got hit with a massive tax bill, school and daycare fees skyrocketing, power prices going higher, rent increasing 10%-15% until now there's barely anything left. I've given up. I don't work with any motivation now I just do the bare minimum. What's the point in working hard when government and landlords take all your money?
If your partner has adult ADHD separating finances save a ton of stress.
Maybe happy couples with aligned spending and lifestyle expectations end up joining their accounts as an outcome. Rather than joining accounts make you happy
This is what we do also. Monster PR's get glancing reviews and are risky and diruptive to everyone else's feature branches when they merge latest. So the smaller the better. Quicker integrations. Less mess. Less risk.
I wonder if it’s actually the screens themselves, or the disengagement of the parent where screens fill the void?
Did TV do the same thing two decades ago?
Cosmosdb still doesn’t support skip and take.
And aggregate queries are incredibly inefficient.
We’ve had to move a heap of data from cosdb to sql server, our reports ran from 3 hours, to now 5 minutes after moving to SQL.
It would be more interesting to find what they did with their time before and after. And also the impact of UBI to the already employed. How their vocational prospects have changed.
Money given to the unemployed is not UBI, it's the dole.
They seem to coincide closely with the release cycles of Visual Studio proper. I wonder if both teams (or the same team) are within similar disciplines.
Totally agree it's not simple. But monolith in early stages enables a must faster change cycle from early adopter feedback since there's less wiring up to consider as features change.
If I were the unfireable billion dollar CEO I'd be able to take time out of my job to drop off my daughter to school also. I'd also be able to afford the million dollar house close to work so my 30 minute trip to school would be a dream compared to the 90 minute commute to work.
I'm currently working remote and took the job over an on-premises gig in the big smoke.
It's a 200 pay cut per day.
However factoring in expenses in fuel and parking and car wear, and the 10 hours of time lost commuting per week. I'm counter-intuitively better off by the equivalent 200 per day.
Reason being my time spent NOT commuting is invested in my bootstrapped startup. If I had to commute, I was essentially earning money by sitting in traffic rather than coding, which had to be spent to an offshore developer while I'm in a car instead of at my machine. So that including expenses in commuting will erode my net income. Not to mention the stress and health and mental performance impact commuting does to you. Sitting in traffic, cognitively processing the driving, finding a car park, walking ten minutes from a car park to premises.
My motivation and energy is sapped by the time I'm in the office. And more so by the time I get home.
Prior to this I was doing the commute to make sure the boss sees me gig for a year and compared to now, the difference in performance I notice is remarkable.