andmarios

The behavior described in the article can be seen in all dementia patients.

The article is written like it is a rare and unfortunate story which we watch from the sidelines, but only the age of Lee makes it unique. Many of us will experience exactly the same with a beloved one ( probably a parent, maybe a significant other).

Every single part of the story except the age, all the changes in the behavior —small and large—, how hard it is to live and/or manage someone with dementia, how difficult it is to come to terms with it, etc, happens to an awful lot of people. It's just that it's not a subject people talk easily about.

Last but not least, doctors are often the worst offenders in the progress of this disease. Most doctors only care about the "now", solve the problem at hand, send the patient home and be done with it. Surgery, psychotropic drugs and other forms of treatment can speed-up dementia progress. Alas, there is no incentive to research, document and act on this.

I can. Rent does not count towards spending but it counts towards... earning.

So, if you own a house and rent it to others, the rent is part of your income. If you rent a house to leave in, the rent is not part of your spent amount.

There is a special clause, that if you spent more than 60% towards tax, rent and loan payments, then you only have to spent 20% of your income on services, goods, etc.

This is exactly what it wants. 30% before any tax, without counting rent, etc must be spent or you face 22% tax on the unspent amount. :)

Allow me to explain better.

The 30% comes before any tax. Also it does not include payments for taxes, rent and other things.

So, let's say I make €40K/year. My tax will be about €11K. Further taxes, such as owning some property, owning a car, can add €1-3K more. My rent may be €7K.

So now, I have already spent ~€20K but this does not count towards this limit. I still have to spent €12K on various things (food, services, goods, which come with 24% VAT in Greece) or I get an additional 22% tax.

It's madness!

But business people know all about debt because it's common for a business to operate on debt. They can relate. And, as the advice usually goes, it's better to first address your debt before going into saving and investing.

Syncthing. No cloud part though.

Oh cool, so as an engineer I'm expected to know instantly if what I'm working on is legal or not, although most of these cases take years of legal battles or involve huge working bodies from EU, etc.

Maybe since engineers are expected to have such good judgement, companies should strip their legal and HR departments and just put related matters for vote in Jira.

That's good advice; if you are building a command-line tool for Unix. :)

The thing is I can chain command-line tools using a pipe, embed them into scripts and more. I probably can't do that with your app.

My guess is that great products are based around workflows rather than features. Have a vision, work towards it.

Ah, I missed it!

Another exercise could be to have a page where the Access Control Allow Origin is set to a specific domain, then make a request by setting a different origin.

E.g:

  curl -H "Origin: https://wrong.origin.com" https://httpbin.org/anything

Many people think CORS is enforced by the server.

I would suggest one more exercise; make a GET request to an address where the server replies with a redirect.

I would assume that the consensus is clear these days that swap is good and should be enabled for most cases for Linux > 4.0.

Of course, real-life often is different than theory. Does your machine have a spinning disk or an SSD? I am much faster to enable swap on an SSD, since it won't be painfully slow, should we ever get into a situation where our RAM is saturated.

What happens in cloud VMs? These things use a network disk storage (transparent to us), and often writes need to be sent over the network more than once (for redundancy). How extensive swapping would behave in such an environment?

As for saying no, it's important to set some rules to avoid chaos, but it's also important to trust our senior people to take decisions. If they need to go against a rule, I would expect a good explanation in their commit —because, infrastructure as code— and documentation. If a junior wants to go against a rule, they can consult a senior. Issuing a no and expecting everyone to follow it blindly, is the worst form of micromanagement. :)

Engineering is not about building robust structures. It can be applied towards that goal but that's it; an engineer takes specifications and constraints and solves the problem within these bounds.

An important part of an engineer that the article fails to mention is the use of the tools of applied mathematics. If you use an RDBMS and you normalize your database, you are closer to an engineer than someone who can only handle NoSQL.

We do pay, for us, it doesn't make any difference in the quality.

Slack is browser based, even the "native" client option. This means your colleague cannot choose which screen to share in Linux, so if he has two screens he has to go at great lengths to make it work properly (either share both or share a specific app instead of a screen).

Also Slack's screen sharing quality is terrible and ofter you cannot read letters in the remote end's screen. Zoom's codec is much more crisp with text and graphics, almost like a native app running in your computer instead of video.

In addition to everything already mentioned, Zoom has great screen sharing quality and very, very importantly, is the only solution that supports Linux with a native client, which means proper screen sharing and much more.

Linux desktop adoption may not be great, but many good software engineers use it for work. In our team it's hard to find a windows laptop. Zoom is the only software that works for us.

It says that the sprint planning takes about 45 minutes. What I take that this means, is that there is a backlog with stories and tasks which was created and refined by the dev team. These stories include specifications, estimates and more.

So what the project leads actually do, is to decide which of these backlog items will get into the sprint. That's all.

I have a Sony Z4 tablet, released in 2015. This is the best Android tablet ever made and after 4 years nothing can beat it when it comes to a use-centric approach. Alas, it was the last tablet Sony made.

Sony had a very rare insight when designing it. It's 10.1" with a gorgeous display and no burn-in after 4 years.

It is made of quality plastic, with rounded metal edges so it won't break when falling and a textured back. The thing is light, 395g. Nobody, even today can best this. Because it is light, thin (6mm) and with a textured back, you are never afraid you are gonna drop it. There is grip —remember, usually we don't use cases for tablets. Also due to the weight and how evenly distributed it is, you never get tired holding it. When I hand it to people, they are always surprised by the weight and how comfortable and nice it feels.

When most companies and reviewers optimized for aluminum, Sony had the mettle to go with what they thought better and they were right. Unfortunately, you can only value this, after you use the tablet.

They also made it waterproof. Submersible into water waterproof in 2015 which is very handy for a tablet, using it in a kitchen, etc.

It's a pity seeing them cutting more and more every year their efforts in the mobile division. Of course, they made mistakes, mistakes that I guess come from the company culture, but also the market is increasingly dominated by marketing practices. Let's not forget Samsung mocking openly apple users in their adverts.

I have a Huawei Matebook X Pro and I like it. There are many things to like about it but the one that stands out for me is the 3:2 ratio screen.

No matter how much Dell and Lenovo call their offerings professional, I just can't see a professional working on a 13" 16:9 screen.

Things I don't like about the Matebook is that the warranty and repair services are basically unknowns, there is no next business day, on-site warranty and of course, they aren't battle tested —though quality issues seem to be all the more common for Lenovo, Dell an Apple nowadays. Had a friend joke the other day _your Huawei is the only one sure to keep working, its main purpose is surveillance and if it brokes down, it can't perform its duty_. :)

Indeed, but ops people have to learn new technologies all the time, so it's not that big of a leap. When you talk about a cloud and see a sysadmin rolling their eyes, it's not that they have something specifically against the cloud, it's that they've seen so many diverse bugs and issues in their life, that they know you just exchange one set of problems for another.

Also, a challenge to using clouds more effectively is you need to bring onboard your developers. Ops people often have to act as coaches and basic systems' knowledge is very important in this role.

Every year cloud providers announce tens of new services, poorly tested and far from production ready. Non-ops eng teams and management are always happy to use the latest buzzword out of AWS, then ask their ops team to make it somehow work.

Certifications are moot. I don't care if you are certified, or if you have used a cloud (or kubernetes) following a tutorial. I do care if you have seen enough issues throughout your career, so you can debug every time (not when, nor if) mud hits the fan. I don't care if you can type a port in a yaml file or in your browser. I do care if you know how many ports are there, what's the ephemeral port range and so on. Systems are 75% experience, 25% basic knowledge, you can't get away just with certifications which matter only after you get experience and knowledge.

If you are experienced in ops, I know you can learn and work out any cloud. If you claim you are experienced with a specific cloud though, then better have to share a ton of war stories or it will just be a huge red flag on your CV.

Let's call it for what it is, clouds, like data-science are hot fields right now. It's only natural that many people will go after a good-paying job claiming expertise in the field.

So, I'm an average person hosting my email on my domain. I use it for both personal and professional reasons. I'm by no means wealthy, so even though my email address has huge value to me (from clients, to friends, to banks and digital services) I can't pay a huge price for it.

With your suggestion, someone with enough money would be able to force me to sell it. Identity thieves would have a field day with this!

I think it's a good number for a sustained load within a large cluster.

50MB/sec multiplies due to replication and consumers. Also in large clusters, the bottleneck comes often from the network switches rather than the rest of the stack.

Also when it comes to sustained load, many people don't realize that 50MB/sec × 10 brokers × 24 hours × 7 days × 3600 seconds leads to 300TB per week (without counting the replication). :)

Once you do this, squatters will just find an easy way to make a domain seem active: email traffic, basic websites, etc.

Also sometimes there are legit uses, like squatting names in order to protect your brand. For example I could see google squatting google-search.com

I would take a different approach to reach a similar conclusion.

Assign a task to a junior dev.

- Efficient: copies blindly a solution from stackoverflow in 30 minutes

- Inefficient: copies the same solution but tries to understand it before committing it, taking 90 minutes.

The inefficient lad is on his path to become a senior engineer. :)

Sometimes, devops, admins, DBAs, etc are there for QA. It's not that they don't know how to automate everything, it's that they know if you permit someone to do a dumb thing, they'll probably do.

It's one thing to talk about good practices and another to build a large development team that can understand and follow them. By moving the responsibility to devs, you tax your senior devs, who have to monitor middle and junior devs more closely and sometimes micromanage them as a consequence.

A few schema changes a year are more easy to test, justify and —most importantly— track than many small ones going on at the same time. How do you even manage the schema version when there are multiple branches that require changes and you don't know the order they will be merged in? Instead of a version number, you start to use flags. How about deprecated features? How and when do you clean up? Something else that might be important, are performance optimizations.

I agree on the suggestions of the article and it's the way I try to write code that uses a SQL store, just saying that sometimes in real life you have to make things harder in order to stay safe.

Marios from Lenses.io ( landoop ) here. On a brief look, although IANAL, the new license doesn't affect us directly. Our core product has native Kafka and Kubernetes SQL capabilities which aren't based on Confluent's KSQL. Lenses does integrate with open source schema registries —Confluent's and HortonWork's— and this integration is also not affected by the licensing change.

On a personal opinion (I don't represent my employer), the new license affects both behemoths like AWS and smaller providers like Aiven alike. It may be a bargaining chip for the business, a trojan horse or it may backfire; only time will tell. I think many HNers know first-hand how hard it is to balance business and open source. It is a sign of health that the community is concerned and the best way to ensure an open platform going forward imo.

I think that such a product, even if developed internally, it would be stopped by the business team. The reason being it would be better than Windows in many aspects.

I'm a long time Linux user, but got an ultraportable lately and kept windows on a small partition (mostly for BIOS updates). Linux was installed without any issues, everything except the fingerprint reader works. The interesting thing is that it does not just work, it works better. The most pronounced difference is the touchpad. On windows it is frequently stuck —and it's not palm rejection because I never had an issue in Linux. The 3 finger click that is paste or _open in new tab_ in Linux, in Windows opens Cortana. With Linux battery lasts longer. With Windows, the fan starts turning without any reason while the process manager says _no process is running_. Very annoying. Windows constantly nug me because I used my skype account which, according to them, does not have an associated email. Applications go into full screen without any indication on how to close them. I have to search for software on the internet, via my browser. The other day I wanted to start Windows for a Lync meeting and it decided it has to install updates and restarted a couple times before allowing me to continue with my life. Perhaps the most infuriating thing was the candy crash tiles that greeted me when I first booted the computer.

I'm not saying you should use Linux, but you should ask for better Windows.

If a small town in the US could become a tech hub, then every capital in the world would already be one. Significant amounts of money are spent around the globe, yet it seems tech hubs are the one thing you cannot disrupt. :)

Same issue here. I'm a Linux user but recently got a new laptop and thought I should at least log in once to Windows before installing Linux.

I was welcomed by candy crush tiles and other questionable stuff. It is totally incomprehensible to me how a machine that costs almost $2k has candy crush as the first tile the user ever sees. I don't think Microsoft cares anymore.

If there is a link, I'd say it's devops —except cockroach and caddy of course.

Go is a very useful language for this space, as it's easy (we aren't developers after all), it's safe, fast, compiles to a single binary, easy cross-compile support, software written in it tends to be robust, great basic library, etc.