mc3

The real lesson is there are multiple lessons. Layered security and risk management. Back up automatically, don't expose database, don't expose configuration files, use tools to try and exploit your own site first, try to avoid passwords in files at all if there ways to do so such as credential stores, encrypt data at rest, no plaintext passwords. When one layer fails the next layer turns this from a catastrophe into a mere headache.

Yes I use that feature too. Seemed like a no brainer. I can even recover the image pretty easy anyway by typing in the 10 or so commands again.

It's about risk assessment. No electricity / no internet means you have bigger problems. 435 npm modules is risky - so that needs to be managed but that's not necessarily meaning ditch NPM.

And for Etsy - well the usual play with these sorts of things is you use them for marketing then get the customer after they make a purchase to start using your real shop running on your own domain.

Sorry to hear that. The obvious lesson is "backup", maybe the less obvious lesson is to pay a bit more for a service that does this for you (or a cloud provider might have that included) and have peace of mind.

For similar reasons I use a cloud backup for home PC files that just syncs it all up. When I was doing it manually it was a once a year affair because: too busy!

Data analyst: "Hmm interesting correlation, 50% of people unsubscribed had moved to California".

They figure it out.

Later.

"Moving to California? We hope you enjoy the change in your life, and hope we can help you celebrate by giving you a 50% discount for a 6 month prepaid subscription, and we hope you stay with us and enjoy this great publication. Thank you for your loyal support."

I think it's a bit confusing to have the full power of VSCode. I think restricting the menu items would be useful. Sorry got distracted by vscode too much!

Thanks jppope. I like the idea to talk about 'results of the work' and you can ask probing questions about why it worked. If they can describe logically what they did and how it linked to those results, describe what they are certain and uncertain about it will probably be hard for a liar to fake all of that (the liar will be confident of everything).

"Results" is a funny thing to define though. For example say I know nothing about coding, and I hire someone to make a website. Based on their "results" they make good looking fast websites without bugs. I hire them. I get my site. I need a change and suddenly they are not available or got expensive. I ask someone else to do it and the say "maaan, wtf they have used Perl and a weird JS library for the front end, and purescript and I don't know how to maintain that. I'll need to rewrite it".

With machine learning, to evaluate the results, I think you'd need to know a bit about machine learning and what P(good work by this person | company made money from the model) is vs. P(null | company made money from the model)

And the opposite end of the spectrum, if you want to get something going more quickly: https://www.indiehackers.com/post/how-to-brainstorm-great-bu...

I think it is a case of treating the job like a job. You do a solid days work then go home. Don't worry if you didn't do it as well as the next guy or girl. There are people that know a lot of stuff, and HN in aggregate knows a hellova lot of stuff, but the main concern in a job is being productive, being able to find solutions to their problems. I think an occasional course to refresh on something is fine, but there is no pressure to code at home. There are plenty of people doing valuable work using the C# or python or php skills they have been using for years. Many systems will use frameworks from the 2000s.

Time for a remote distributed Olympics!

interesting, seems like I get my own docker container to play with!

My non US experience is I have seen no correlation of the boom/bust cycles and "how good it is to be an engineer". I realize that FAANG employees are of course raking it in like never before. But I thought that was because of a lack of a salary cartel and general software eating the world.

Upload to imgur? This is a meme machine!

A bit like free education.

Yes there is a general trend that a new "market place" opens up. It could be adwords, or it could be udemy. There is then a race to the top/bottom where the marketplace becomes popular and crowded out. The "crowd" progressively gets a worse deal (except for the winners of the crowd) and the owner makes more money.

For example adwords:

1. Crowd gets worse deal: average bidder pays more for ads, hard to make a profit, might break even if you are lucky. Might be OK in a new niche if lucky.

2. Winners: people with sharp marketing teams who can bid on the right keywords and have an excellent sales funnel to take advantage. They can outbid the crowd and make a profit.

3. Owner: Google makes a tonne of money from ads of course:

Udemy:

1. Crowd gets worse deal: I saw a 80 hour course for $20 on there. Most are 20-30 hours course for $20. Course maker gets a fraction of that. 100's of similar course means the platform doesn't necessarily give you much traffic.

2. Winners: Some people sells thousands of units of their course on these platforms. Again those with good funnels to get them to buy off the platform probably win (I am guessing).

3. Owner: Udemy does well.

Same applies to the app stores!

Ugh! I may have interpreted the comment I responded to wrong, and replied to my own strawman. I think you need the power for the user to delete records (obviously) but this could mean a bug in the system could cause the records to be deleted. But it sounds from what you are saying that they sort of "intentionally" deleted the records (not sure if a human had the intent or an algorithm?) but if intentionally deleted yes that sucks, there is no reason for that I can think of, given what they do is about handling DDOS.

Unless the mechanism exists for legal reasons, i.e. they are forced to take some sites down by the government or law suits.

Ironically this can be used to create search engine spam!

First time i've seen a https://txti.es posted on here. nice.

Why can you delete DNS records? Well it's pretty common to want to do so (usually followed by adding some new ones).

Your doctor has a syringe as a medical instrument. They can kill if not used correctly.

And also there are docos on netflix about the fake products problem, and they do scare you away from using certain large online marketplaces.

So if I were the big retailers and cosmetic manufacturers (etc.). I'd be banding together to help fund more docos like that on netflix and elsewhere.

That'll scare people over to physical retail without mucking the image of any specific brands.

Another advantage of physical is the great advice you get and being able to act straight away (tale the thing home.). For example for a DIY project you often realise you don't have something mid job, just go and get it, get some advice on how to install it, and finish the job off on the same day.

Does this mean I can treat it a bit like PHP hosting of yore, where I upload a single file and stuff just works? No NPM etc? That would be compelling!

Maybe this is what will save bricks and mortar? Guess where I buy any product I am going to ingest, put on my skin or plug into a wall?

A real store with some special online exceptions, but those exceptions are never going to be Amazon or Ebay.

There are some shady real stores selling shit too of course, so I have to be choosy, but I'm feeling pretty safe at a national supermarket chain, or Kmart.

Correct AFAIK you can't get end to end type safety in Handlebars, in that if you treat a string as an array it will silently not render something, whereas in Typescript / React you would notice.

But... let's forget Handlebars because Typescript/ES6 allows you to write code like this:

    mythings.map(thing = `<li>${thing.name}</li>`).join();

And this is React-free and arguably a lot simpler for the needs of a static site, and actually more flexible as your are controlling the character by character output.

And the question is do I want to pull in not just React but Next.js and learn all of it's ways to do this? I think for a static site no.

I like the idea. I'm not sure how a spreadsheet interface would help with "high volume transaction" (thousands?) situation. I thought API integration would be the way to go with dealing with a high number of transactions?

Which I would take to be "is there any place that experienced tropical weather for a year that would normally be subtropical or temperate?"

Yeah the idea of building a 100% static site in react seems a bit ironic to me. Handlebars is so much simpler to work with for a static site (like a blog) that isn't going to "spring to life" and become a SPA.

But I can see it being useful in the niche area of someone who needs to do server side rendering for performance (every millisecond to first render counts), while keeping the code simple by not having a second technology to do that rendering, and they need the same thing to be a SPA. Maybe a GMAIL type application? And again the user has to care - I don't care if I wait 10 seconds for my mail app to load as I'll be spending minutes in there once it does, and you've locked me in for other reasons anyway.

This might matter for SEO but to be honest you could just have a non-JS version of the same page which looks different for SEO purposes.

Next.js seems pretty hot, so I am probably missing something :-).

I'd rather not use JS on the server myself, so for my projects I'd either make a SPA with API backend and no server side rendering. Or just a classic "rails style" crud app with a sprinkle of JQuery.

I hope someone chimes in and tell me what I am missing and why to use Next.js other than "I only want to do JS and React for all the things."

I think the Vim way is to spend very little time in insert mode, so most of the time you don't have to think because you will be in the other mode. That said give me VSCode anytime!

One way this can be achieved is using specflow or cucumber and then make that drive selenium or puppeteer.

Probably a 10 minute job to set up some basic commands (like demoed here). Not saying you can replace this project in 10 minutes of course.

Advantage is you can use the same language as used here pretty much, but you can use some of gherkin's nice features like the tables for different test cases (or scraping cases!).

Kasaya would have the role in this case of defining the common language.

It's not 1999 anymore. There will be increasing demand for cloud services going forward. It's more of a bread and butter rush than a gold rush.

The advantage is when a new person starts. "How does this work?", oh here is a link to a well explained document on this thing called "Rails". Oh you know "Rails" already, of course you do, that's why we hired you.

Where as with a customized "elegant" meta-programming DRY NIH solution unique to ThisCorp. "How does this work?". "Try to figure it out yourself. Jack has left and Ryan is too busy fixing production issues to help you".

Obviously if you have a team of Haskell compiler writing geniuses YMMV.