shearnie

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.

Some microbrands do meteorite dials https://zeloswatches.com/products/copy-of-mako-500m-diver-st...

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

very + very =

spriggy

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?

Yeah MSSQL is the opposite in massive orders of magnitude

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.

Selling to developers is hard slog. Try another non-technical domain.

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.

My angle on building products: Monolith to market.

Break it up and optimise where the sticking points are as customer base and feature set matures.

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.

I remember in primary school in the 80's all the kids were actually using "nigger". I went along with it, I didn't know what a nigger was.

I was in north Brisbane, Australia.

He's deliberately made the java example of file input too busy, it's poorly written. And added multiple exception handling to make it longer than it needs to be (in its context).

I started in BASIC as a kid. The barrier to entry was minimal and fun for a few hundred lines of code.

To manage the complexities of a large code base, you need to have supports and infrastructure and information hiding to structure it neatly. That adds extra code, but contains it in a way to makes sense of it all.

I use both. I even use text indexing, redis, queues and other things.

Sometimes RDB is better. For other things it's easier and more scalable with document store.

They need to know about each other using your application logic (join by GUID for instance), but you're doing that anyway even if you religiously staying in one camp or the other.

I tried for hours to mess around with a simple deploy from github to EB or even a plain EC2 instance.

In an Azure web app it took me five mouse clicks and 10 minutes of research and learning.

We happily update master and don't even waste think cycles on what's wrong with the server or deploy config.

It just works.

Why can't AWS make it that simple.

I prefer keywords in their own line eg:

<code> SELECT foo, bar, blah FROM baz WHERE foo > 3 AND blah = 'dont use baz' </code>

I've been working remotely for the past 6 years. More and more I am having to compete with offshore, and with the boss's expectations that working "in the comfort of your own home" means you deserve a pay cut.

I make it a policy of mine to visit the office once or twice a week for design and planning, so the social aspect keeps me sane. I find it a good balance.

I've recently started looking for a job for the pay increase due to cost of living pressures and because of the culture prevailing of bosses needing to see butts in seats it will most likely be on-premises.

We've been priced out of the market for housing, so we have to live further out. It would involve three hours commuting a day. The pay increase is almost negated by the erosion of your hourly rate when you factor in time and expense of the commute. Not to mention the time being in a car and train rather with my kids.

We've managed to get confidential data stored in Azure for a large financial organisation, all compliances they required passed.

A server is a server right?

Problem could be cultural and generational. Some old school types like the idea of a server without redundancies and fire prevention and fault tolerance and high security clearance in a data center. They want it to be blinking lights at them in a cupboard on premises. They feel it is safe due to physical proximity, even though their firewalls are like cottage cheese.

We're noticing that issue with health data for medical practises. Older people are suspicious of cloud. The younger generation are more savvy.

How much in AUD will you work for?

We're a remote company looking for a front-end developer.

Run a time tracker and log every task you are doing. Cracking the 40 hour mark means you are not prioritizing your time properly or you are meant to be single for a while.

Time tracking is also perfect for accountability in your performance, and also how reasonable your employer is. If you're on a salary for a 40 hour week but end up in the 50 hour territory you are sacrificing precious family time that you'll never get back, for your boss. For free.