lugg

Pull your head out your ass.

You're the one sitting here on the internet claiming defeat.

How many people have you told to cut back on consumption and fuel use this month?

Yea. That's what I thought.

Don't act like it's impossible to change behavior it's not.

Smoking, drunk driving, domestic violence, racism, homophobia, and a bunch of other social issues have all been largely tackled the last few decades.

In WW2 we repurposed car factories to make tanks in a matter of weeks.

Please, don't act like we're a bunch of invilids incapable of change.

Speak for yourself.

Have you met our politicians?

It's more like 20% but it shouldn't be affecting your base.

If anything it should be increasing it.

They are, in general, scum of the earth though, so tread lightly and hold no loyalty.

Don't give them your CV in word format unless you feel like finding modified versions of it in the interview.

And please replace referral contact/ name info with "referrals available on request" unless you don't mind your old boss being hit up for new work behind your back.

Looks like you're not working with a recruiter. (Not a bad thing)

Going off my sample size of three, yes, that looks like the average experience.

It's just a numbers game/funnel like anything in sales.

The 50 applications thing is one of the reasons I get really annoyed at people who claim software Devs have it so easy (we do) but when asked how many jobs they applied for last week it's like, oh I applied for 5 jobs over the last 6 months.

Here I am writing and sending 10 unique, researched cover letters every day. No wonder I get hired in under two weeks.

Going to have to raise the bar a bit. This is Australia, we all do things on wifi.

Those are all valid trade offs, but its ignoring the issue raised in the AP.

Like, is an environment like this encouraging bad habbits?

But anyway..

Special hardware: such as? Very few systems can't be downscaled. Situations where you need this special hardware we are talking horizontal multi server setups anyway.

Special workspaces: be less special, improve tooling, improve build operations. Very few setups actually needs centralised configuration.

Large compilations: I'm not sold that a) there is many people with the justifiable need, and b) any real justifiable need is likely going to want on demand autoscaling of the compilation servers, i.e. development won't be local anyway.

I'm not trying to debunk everything you've said. It's a trade off and I've used central dev databases in the past for legacy systems and it worked well for those in the office.

All I can tell you is that iteration speed, testability of code, manual testing and all around team morale was DRASTICALLY improved by stubbing out that bottleneck in newer systems.

Read whole thread so far, haven't seen anyone mention their network conditions. Can people indicate to me if this is just as nice over Pacific ocean sized hops or is this just working nice when you're talking down the road / in the building?

Unrelated? How? It's Facebook. They have shown a repeated assualt and disavowement of social responsibility. I wouldn't expect Exon mobile to do very nice things in non oil contexts. Are you saying you would?

Reference? Where have you been? Cambridge analytica? It's advertising arms? It's all selling user data either directly or indirectly. Don't be so naive.

This is a strawman argument. And I wish people would stop relegating this type of system refactoring to some idiotic attempt to institute order for the sake of order.

Tidying systems up so they are organised "from my perspective" is not done, "for my benefit". It's done to make things easier to change.

Yes, it can make things less performance, no, most of the time that is irrelevant.

Refactoring is not optimisation. They are different things and both need to happen.

They both require you to make trade offs against future difficulties.

Life is incredibly resilient. Intelligent life is incredibly delicate and brittle.

Or just use native data structures.

If you're throwing it all into a docker container as a single artifact you don't need a separate language to patch into a complicated config parser. Just use hardcoded objects/maps in whatever language you use.

Careful you almost sound like a distributed systems engineer following the first rule of distributed systems engineering: don't.

Not AP but given my own government is unable to protect its own citizens travelling there im not about to risk a transfer through there. It's unlikely anything would happen but given my work I'm almost certainly on a list there and I'm simply not willing to risk it.

https://mobile.abc.net.au/news/2019-10-24/china-hostage-dipl...

https://www.sbs.com.au/news/yang-hengjun-australian-writer-d...

Fucking christ. Mules? Seriously?

This comment could be posted on every article about fusion until there is a new fusion power plant opening day announcement.

Do you think it's worthwhile to discourage humanity from attempting new things because there are existing sub optimal alternatives?

Or are you just trying to sound contrarian for internet points?

(Despite what you're saying being the safest, most boring, done to death, remarks on fusion)

1. Over my career almost none of it has been debugging problems due to a lack of foreign keys.

Further to that, instead of having lazy cascading deletes moving the goal posts on you. Data missing its parent for example is an indication something is wrong. It's a useful diagnostic.

2. Most string data is safe to represent as empty. Handling null on the other hand is a different situation and often induces warnings or other side effects depending on the language. Forcing the null checking to your boundaries is much like forcing your state/mutation to the boundaries in FP. Hell eveb though I think it's insane, hexagonal arch works on this idea as well.

Only if you believe popular opinion.

For reference. Adult males recommended daily intake is: 9 teaspoons. Females: 6 teaspoons.

That's from American heart foundation so take it with a grain of salt.

There is a middle ground.

You can err toward honesty but still remove hostility.

I find it incredibly annoying that every single answer seems to just accept that this is how things are and can't be changed.

And that it's fine because everyone knows it's buggy.

That's great, but it would be cool if one day I didn't have to explain all this to some random airline staff 50 times during my travel.

Yes, and what if you don't make a foreign key?

This assumes things depend on the rule being enforced.

Nobody suggests taking an app / db with foreign keys and removing them that is a recipe for disaster.

Will result in corruption. Yes.

Will result in more fault tolerant software, also yes.

It's a trade off and one I make willingly at every scale.

I stopped using foreign keys after university and have never wanted them since.

Non nullable database fields are far more useful than worrying about fks.

Rust is a very terse language. Inexperienced devs tend to write overly compressed code.

That example isn't too bad once you're used to the syntax and idioms but the lack of white space to space out logical blocks is what's making it hard to read.

Well, that and only what I can say equates to writing C++ in rust, much the same way you can write php in JavaScript if you squint hard enough.

Probably doesn't help it's trying to be a comparison which doesn't really work. A lot of that could be refactored out into idiomatic rust and it wouldn't look so bizarre.

The grid needs to maintain supply within certain levels.

If you produce more than your share, someone else needs to shutdown.

Shutting down certain power sources (e.g. coal) comes at a non zero cost. Someone still has to pay the power plant that needs to shutdown or send people home unexpectedly. These plants might be have pre secured contracts to sell at a given price over a given time period further adding to the cost of shutting off their supply.

Some more info here:

https://www.epexspot.com/en/company-info/basics_of_the_power...

It's not a privileged point of view. You can find a new job. You might not like it. It might not be possible for everyone. But the idea that there are only jobs in tech is asinine.

All qualified and experienced people are expensive to replace.

That's not unique to software.

Software engineers aren't special.

Please stop treating them as some enlightened class. They're not.

Software engineers face the same idiocy as everyone else. Every other industry has smart, creative, individuals willing to buck the system and try new things for an edge.

If you truly believe people can't express a simple argument for trialing this sort of thing without losing their jobs maybe they should be looking for a new job because their current one sounds like a train wreck waiting to happen.

> A static layout will never know how to reflow itself when the window size changes; it needs code to define that behavior.

This is no longer true. CSS grid solves this completely.

https://youtu.be/7kVeCqQCxlk

That sounds super interesting I didn't know rust crates were managed like this.

The question in my mind is where does semver come into this?

Why do you need three arbitrary and meaningless numbers when a commit hash, branch, or tag would suffice.