My company failed. Worked on it 6 years and ended in a burnout. Thing is I can say I tried. And now I have another few years (like atleast 40 I hope^^) to do something else. Failing early isn’t the Ende. You did atleast try if you fail.

Comments URL: https://news.ycombinator.com/item?id=39775622

Points: 4

# Comments: 0

For general here is a list: https://pq-crystals.org/kyber/software.shtml

It´s nothing against docker, but keeping a bare web server secure and then introducing databases etc. with self build images is nice.

One thing Im personally missed out (now 27; started at 12 with web stuff) is writing. Not only writing blog articles or documentation, but writing for the sake of documenting small hacks or bigger concepts. So that would be one tip I personally would loved to get.

About projects: - either do things like features for small projects (e.g. dark mode for something like altcha.org) - try to fix some bugs - or try to recreate small projects based on a framework or vanilla for the sake of learning stuff.

As a tip for learning more things etc. in the web dev space -> Look into accessibility. Its a huge and interesting topic.

Also "that is hard and might be too hard for my skill level." -> Do it. Get started with something "easy", read papers, do tutorials, write stuff about what you learned. You wont learn if you wont try :D

In general -> Keep on learning. Don´t waste time on chasing the next framework and ask. Asking questions can be interpreted as being annoying. But if you try to understand different view points, different tech etc. you will end up talking with people that will bring you forward.

Thing is: charging the data center/content provider above global average pricing and also charging the end customer for the same service again.

Comments URL: https://news.ycombinator.com/item?id=38445208

Points: 2

# Comments: 0

On the other hand, if it is not lawful interception, I doubt Hetzner would allow it. Because that’s also against law.

I used a self hosted instance of LanguageTool [1] (they also have a free API plan).

For checking links I used something self build. It checked all links (including in already published articles), archived them via archive.org and if they changed (e.g. offline) link the archive.org link.

After publishing, I also send the published article to archive.org and published links to social media platforms. Back then I also thought of publishing parts of the articles automatically to dev.to, medium etc. but never went through with it.

[1] https://dev.languagetool.org/http-server

What is not allowed though, is saving everything that could be talk under colleagues or other people that is considered private…

Ohhh and we have to archive them in a way, that we can’t change them, delete them and can proof 24/7 that that’s all the emails we have.

A simple way would be a headless browser [1]

But there are also hosted tools that work like a website builder.

The best way is: keep it simple and keep back (check once an hour or day and not every minute).

Many shops use Schema.org markup. So if they support it, you don’t have to write it for every site.

You could also use a library that works with raw html and css. Then you could just use css selectors for extraction.

[1] https://www.atlantbh.com/building-a-dynamic-crawler-with-pup...

Still Bad but less impact than described in their first email. (Asked support)