HN user

jinglebells

144 karma
Posts0
Comments99
View on HN
No posts found.

"The general rule – IP ownership

The general position under English law is that IP rights created by an employee within the course of employment automatically belong to the employer; where there is any doubt as to whether an employee or their employer owns IP rights, the relevant legislation largely favours employers."

It's been that way for decades, while the UK was in EU.

I had to get it written into an employment contract that Open Source activity outside of work was my own.

By using a machine you switch from having one well understood, pretty standardized ui paradigm: put stuff on track, tracks goes to checker, checker checks them through, you pay and bag your stuff

Even this is not universal. In Sweden the checkouts have that divider so the checkout clerk can start scanning the next customer's products while you're packing.

In the UK, you can't move on until the other person has bagged and removed which you're expected to do before paying, which makes self-checkout considerably faster because you're already bagged.

Nodejs is faster than Python as a general rule, anyway. As I understand, Nodejs compiles Javascript, Python interprets Python code.

I do a lot of Django and Nodejs and Django is great to sketch an app out, but I've noticed rewriting endpoints in Nodejs directly accessing postgres gets much better performance.

Just my 2c

If you're "Pro-office" you're dictatorial. This is a problem.

The cat is out of the bag. I haven't worked in an office in nearly a decade, anyone saying "you have to be in the office" will be drawing from a dwindling pool of supplies.

Same. I've got a purpose built office in the garden I built for my wife and I five years ago.

We've got wired internet, power, whiteboards, sofas, variable desks, multiple monitors, it's great.

But we built our business fully remote back in 2014, we've been doing this forever now. While our work colleagues are in their kitchens or on their sofas. It's not sustainable.

I like Go and Elixir from the minimalist approach but I've delivered so many projects recently by using Django and Django Rest Framework with a React front-end simply because you get ORM, Admin, form validation etc out of the box.

In a couple of days you can have a production-ready site and I've never seen anything quite like it for productivity.

Here's one: Get some shelled shrimp/prawns. Mix mayo + ketchup, lemon juice, paprika + tabasco to make a sauce and pour over the shellfish

Shred lettuce, slice avocado and serve with some chunky bread rolls. Shouldn't take more than 5 minutes, 1 bowl and a plate.

In the UK, they literally are.

The law says you need to be covered by a TV Licence to:

watch or record programmes as they’re being shown on TV, on any channel

watch or stream programmes live on an online TV service (such as ITV Hub, All 4, YouTube, Amazon Prime Video, Now TV, Sky Go, etc.)

download or watch any BBC programmes on iPlayer.

I don't know why you're arguing this, it's all verifiable.

From https://www.tvlicensing.co.uk/check-if-you-need-one

The law says you need to be covered by a TV Licence to:

watch or record programmes as they’re being shown on TV, on any channel

watch or stream programmes live on an online TV service (such as ITV Hub, All 4, YouTube, Amazon Prime Video, Now TV, Sky Go, etc.)

download or watch any BBC programmes on iPlayer.

This applies to any device you use, including a TV, desktop computer, laptop, mobile phone, tablet, games console, digital box or DVD/VHS recorder.

I'm not sure it answers your question but in software, the requirements are almost never codified up front because extracting the rules is part of the project.

In terms of the dog-house, there's that rule "Build one to throw away". Since no two software projects are similar, the only way to truly know what you're building is to build it, see what works, throw it away, then build it properly.

Part of what makes software so good is that you _can_ upgrade the skyscraper while people are in it, metaphorically hardening floors or adding new levels.

I think the pattern is

    Public Web -> Reverse Proxy -> Application Server
Rather than
    Public Web -> Nginx -> Node (In his example)
You could reasonably do
    Public Web -> Node reverse proxy -> Node Application Server
It doesn't really matter if the reverse proxy is Nginx or Node or something else, it's a good pattern to insert a lightweight service at the front which can redirect the requests upstream. If you need to scale by adding new boxes or services, this can now be your load balancer.

Your reverse proxy can also handle blocking dodgy requests (Fail2Ban) or act as a lightweight static file handler, leaving your application server to do the grunt work.

And what happens when I don't have any signal? Writing an offline-first mobile website is INCREDIBLY hard. Where are you going to store the data? How are you going to detect the network connectivity without polling and hosing the battery because the radio doesn't timeout? Geo-fencing events?