gureddio

The author has some points but if I was one of his colleagues reading this (he works at github according to his resume) I'd hate to approach him with anything, at all.

I feel like he's missing the team element in this post. Yes your individual contributions matter, but the team's delivery matters more.

It really does feel like this is the current worry in the tech sphere, and somewhat unnecessarily

Well I live in a fairly small city with not a lot nearby, and it's showing me unremarkable nearby high schools

VAS Aviation has put the audio up https://www.youtube.com/watch?v=fItu5qM7QfE

I'm just a hobbyist, but my understanding is that there are supporting systems in-place, such as RIMCAS (Runway Incursion Monitoring and Conflict Alert System) https://test1.skybrary.aero/articles/runway-incursion-monito...

Yeah and this is why Jira consultants exist

Care to expand?

That sounds like fairly specific usage. My color laser has served me well for document printing, both color and black and white

Definitely consider the outlay for a colour laser printer. I've had one for around 5 years and it has been no trouble and is always ready to print, scan and copy.

That and it's been around so long that the language and it's standards have been through so many iterations

I really take issue with the idea that your travel insurance will save you in a case like this. It's almost a naive position to take. Travel insurance is notoriously exclusionary when it comes to individual items, especially high value items.

Travel insurance is probably one of the most least likely types of insurance where there will be a positive outcome for the consumer.

All of these ecosystems have problems. I'm a long term Google Pixel user and I could list all of the irritating problems I've had over the years

I agree with you about the build quality, but also from a software perspective.

I've been a long time Pixel user, and have had the Pixel, Pixel 4 XL, and currently have the Pixel 6 Pro.

On every device, there has been one or several glaring software bugs that haven't been fixed for months, or have required a really, really nasty workaround.

A good example was the bluetooth stack on the Pixel 4 XL. We got a security software update one day, applied it, and then found that the bluetooth connection to loads of devices was suddenly broken. Google took months to get the issue fixed, despite a few hundred pages of complaints on their forums. Instead someone (not from Google) worked out that if you went into developer mode, you could swap out the bluetooth stack for a previous version, and it might work again.

Is this sort of blasé approach to quality assurance and lack of urgency around fixing user reported bugs that really, really irritates me about Google's hardware devices.

The 6 Pro is an ok phone but also has it's problems (painfully slow and somewhat unreliable fingerprint unlock). I think I've had enough and I'll probably give a Samsung device a try.

I feel like in the UK, some of us got WFH in lieu of a pay rise

Both look like something I currently do in a Google Sheet. I might take a look

Surely this is about who or what you are following though.

Personally there is very little crossover between what I follow on instagram and twitter. So the quality of the discussions vary greatly.

On Twitter I follow developers and product people. The quality is better on Twitter, but it's definitely declined because of engagement seeking over the last few years.

That and Snapchat's entire UX is utterly unintuitive

Someone re-writes this article every few years. It's not the first time that somebody has pointed out that customising the scrollbar isn't a great idea

Yes but you do fight the framework in some cases. Take for example persisting a database connection, or a pool of connections. A totally normal use case for a server side framework

Next.js does indeed have those positives, but it steers you towards paid services (prisma and vercel)

It really doesn't look like that big of a change as well. Looking at the PR, they didn't go too heavy on their typescipt usage. I can see they when using typescript, they added types for function parameters, but not for return types, for example.

The "contrived textbook example from 20 years ago" still has a very real impact today. In my experience there are still lots of development teams that are instructed to develop in a "Clean code" style in the flavour of Uncle Bob. It's especially true in the .net development space, and is almost a cultural problem within .net.

As a former .net developer that was often pushed into "clean code", my big takeaway from the video was that actually, not using "clean code" techniques, such as polymorphism made the code so much more readable and easier to grok that the optimisation that followed was completely natural.

Linting, git commit hooks that enforce the linting. I'm guessing some static analysis tooling on the build server as well

I don't agree with your points about complexity. Some developers will go off task and introduce complexity when it doesn't need to be introduced. You must have seen this in your career.

As a manager, you should be putting up gates against this (code reviews, and politely rejecting proposals to introduce unnecessary complexity)

When I started out as a junior developer, I was put onto a team of 4 other developers that was building a booking system for a leisure company.

I got the impression that one of the developers on the team was particularly smart because he would lock himself away for a few hours at a time and build something amazingly complex that nobody else really understood.

Ultimately, he only worked well when the application was still in development. When it came to shipping it, a lot of the areas of the application that he had worked on had shortcomings or just didn't work. Fixing them was also difficult because of the complexity, which was always made worse by the frustrating thought of "why the heck didn't he just implement this the simple way?".

The work got hard, and the team crunched to fix the problems. He just resigned and left and found another "greenfield" project to work on somewhere else.

In a way, him leaving ultimately helped the remaining developers - we didn't have to keep his unintelligible, not fit for purpose code.

Now, all of these years later and I'm the lead developer elsewhere. I now often have to politely brush off efforts to introduce needless complexity that developers propose infecting our codebase with.

Writing code is fun, and building a caching system might be fun, but in a working environment you need to deliver what the customer wants and is happy to pay for. If the work being done isn't on that path, it shouldn't be done.

I guess I'm sharing this to say, perhaps those brilliant developers aren't that brilliant.

Thanks for sharing this list! I wasn't aware of nginxproxymanager. This is something I've been doing semi manually for years. It looks like it'll slot right in and save me some work

I run two main devices:

- QNAP TS-253A-4G NAS. What has been a real game changer on this has been container station, which allows you to run any dockerised app. It is however a little underspecced for any real heavy lifting. It's basically the workhorse for file storage, media hosting and downloading.

- MeLE PCG35 Fanless Mini PC. This is a fairly new addition. Is a home web server (nginx) and runs my gitlab instance. Saves me about $20 a month in hosting costs by self hosting instead (nothing important). It also runs Pi Hole. The OS is Debian

Sounds neat. Are you doing anything to mitigate the possibility of SD card corruption with the Raspberry Pis?

I used to use a single RP to run as a media server, and it was great, but stopped using it after suffering from SD card corruption.

but you just don't know what kind of rats nest I'd be walking into, at least here I know what I'm dealing with

Very well put. With work, it's often better the devil you know

I fully agree with this. I've worked at the same company for the last 7 years. It's essentially because I have a great boss, and we have a great working relationship. If that boss were to be replaced, it would change the job massively