@retoor this is not monolith vs microservice. A module != service.
The Linux kernel for example is a famous modular monolith.

Also a microservice architecture is an organisational (people and teams) solution not a code organisation solution. It's a Conway's law thing.

You can install Rundeck locally.

I'm all seriousness, that sucks mate and good luck finding the next one!

George Orwell depicted my birth year so well...

@hjk101 years=tests & same=sane

Swipe without proof reading fail😅

It's a major version upgrade. Your auto updater should have created a separate branch for it and your end to end years should have failed.

This is the only way I've found a somewhat same way to maintain dependency heavy frontends.

@Lensflare thanks! Familiar with that expression indeed, my mind didn't make the connection.

@D-4got10-01 of course, it's even in the name. You are a resource that care about you to the extent of protecting their resources. Money etc. are also resources so if that is getting to much in danger choices have to be made. Also they are there to milk the resources as much as possible too.

@Lensflare what do you mean? Lead is a metal

I could probably join in if I'm not in holiday yet. Has been years since last DR meet-up

The kicker of your first point is that the whole process is so time consuming it's (up to 10 times) more expensive than providing food & shelter. So you're not saving anything.

@JsonBoa yeah alphabetical would be worse, qwerty is at least designed for typing. Lovely rant by the way.

Dvorak is one of the high potential ones, Colemak and friends are already a lot better.

Something I did not consider was mobile swiping. That might be more accurate on qwerty.

@D-4got10-01 not breaking but basically every key would move a hammer with the keyed letter that hits the center (striking the ink lint and paper behind it) and then travelling back. Now with certain letters the hammer of the next letter could/would collide with the hammer traveling back.
The qwerty layout was designed to eliminate those mishaps while typing extremely fast.

It is however possible to optimise for finger travel without consequences these days so it's kinda ridiculous that we still use QWERTY. Especially considering the vat majority of people using the keyboard have not ever touched a mechanical typewriter.

@Liebranca that's the key feature that makes it work for me.
Don't you have the same issue now with setting how many actual spaces get inserted when hitting the tab?

@rootshell that is horrible. I've find using the language defacto standard is the best way to have the least issues by far.

Even though I think it's stupid to indent with spaces. It's even sillier to fight the thing that everyone expects. It's horrible to have the framework and your style clash or anyone new having to go WTF.

Very good. I don't know how the fuck spaces replaced the literal specific task it was invented for indentation. For pretty alignment it's stuff sure. Spaces are great. For levels of indentation tabs vastly superior. Always have been.

"Where it can run some apps not all apps"

Yeah that goes for every single operating system. Apps need to be designed to run in an environment (this can be automatic). This is how ecosystems emerge and why Windows failed on mobile for example.

There is no OS that can run every application. Linux with Wine is probably the largest possible ecosystem support. Other solutions like WSL do not count as that is using virtualization and the actual other OS.

YAGNI is very important here.

The guiding force behind abstractions should always be variability analysis. You only abstract things that vary.

Even though you may not build abstractions sometimes you do use abstract concepts because they make more sense in communicating. For example if you have a single chair object and you are not getting a couch you might still call it the more abstract "seating", because that is the function you care about.

You can read up on clean architecture and ddd. There are some useful teaching in there however keep the YAGNI in mind. If you follow all that crap to have the layer system in ddd you will end up with at least 4 times the amount of concepts/abstractions than you actually need. Still they do provide some ways to do it correctly when you do actually need to implement an abstraction.

@atheist no way I'm paying them. Not after all the nagging they started doing years ago on Android. They asked me so many times to go premium that I started to use newpipe. This was before the ads issue.

I don't mind paying for stuff that I use/want to use. I do mind putting whiney little bitches.

Presenting as NIC sure I can see that however remain active when unplugged? How would it do that?

During the meeting when they are almost done interrupt. Show the earlier solution in the PR and say "I knew this sounded familiar" too bad MR comments about style only get valued here.
Then leave said meeting.

As you didn't do this. Take it up with your manager. If they care you should be able to point out and night actually resolve this. There might also be a reason for this culture, like previous Devs that made an absolute mess of things.

In our team we had a rule of PR's needing to be reviewed within 24 hours unless it was non-trivial. Than it can even have a meeting to understand the implementation and address any shortcomings. This should be resolved the same week. No cycles of multiple days.

Just look up the phrase "are you like a crazy person?" and you will see a very British and polite example from a splendid movie.

Does Mr big ideas have API access? If he is that dumb and has access; abuse the hell out of it.

Also bureaucratic fuckups like this should be handled by your direct manager.
If your manager doesn't care about you being able to do your work you should not do any work. Just write a script to automate opening the same ticket to change management until it gets approved and don't do anything else.

You then went through the proper procedure and it didn't work. They block you from completing the task and you put everything in motion to remove that block your job is done.

I've done shit like this with processes that were this stupid. Making it their problem or amplifying it enough so it becomes management's problem always worked for me.

Bloody hate the massive z index kids.
Only where you must indeed be 100% sure it must be highest on every page included there is a reason for going higher than 10.

That or some game/dynamic stuff that uses a lot of layers.

@iiii for one the per file overhead is ridiculous on NTFS. This was my greatest annoyance. And because windows UI tools are super inefficient it goes over them multiple times. The "calculating" step is wasting about 6 minutes in a large source directory when copying. And then another 8+ min for the actual copy duration.
Even in WSL (so with virtualization overhead) on ext4 the action was done in around 18 seconds...

Ext4 in general is more optimised, this includes journalling and fragmentation. Those are not major constant impact issues though.

Microsoft should have switched to ext3/4 with extra attributes years ago. It's so vastly superior to NTFS it's ridiculous. Would give a huge performance boost and less fragmentation on HD.

Ideally you want a b tree FS these days but that's a lot harder license and stability/requirements wise. Ext has been proven and is relatively simple.

Why is the delete before submission folder not automatically removed on submission (or in whatever step that makes sense before that)? Sure people should be able to follow simple steps, however if it's simple enough to automate and impact is big enough. Automate it!

Less hassle for new people to the project, can't be forgotten in haste or infrequent submitters.

@D-4got10-01 don't worry about the tags mate we find it just fine

@tosensei yes my thought exactly. And yet hard enough to blow people up for bowing him off.

Only vape reason (although one can usually avoid it) is even an object implements two interfaces. The API requires a param for each interface. Ah the same object is presented twice.

Most of the time I've seen doc like that it's premature optimization (interfaces should not have been split) or huge class syndrome.

@lorentz problem is with new breakthrough authors. They get lost in the sea of trash.