svisser

The word "translated" isn't correct here, as the articles may not be translations of other articles.

It's not exactly tolerated by Wikipedia community, see this discusssion:

https://en.m.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost...

Ironically, her husband's name is Robin.

Wikipedia itself is also working on a new UI:

https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improveme...

The English Wikipedia isn't one of the "early adopter wikis" but if you visit, say, the French-language Wikipedia you can see the changes (e.g., different width to improve readability).

You should look into BDI agents and BDI programming languages.

Being good at hacking doesn't mean they can write clean maintainable code (in a team).

It may be because it's the vault codebase, a tool for secrets management, encryption as a service, and privileged access management.

One would hope that such a codebase is well understood and implemented.

For context, Alibaba uses their own fork of MySQL which is AliSQL:

https://github.com/alibaba/AliSQL

Do you specifically want it to be about Python scripts or also other languages?

The opening sentence of a linked article sums it up quite well: "If nobody understands a mathematical proof, does it count?"

The abc conjecture may be solved today but only when a sufficient number of people understand and accept the proof as a proof.

Unfortunate name if you happen to know Dutch.

Earlier thread: https://news.ycombinator.com/item?id=9896369

For those looking to validate dictionaries / JSON responses in Python, the voluptuous library works quite well: http://github.com/alecthomas/voluptuous. It also works for lists and other data types.

Coincidentally a book was written a few decades ago called "Ringmakers of Saturn" which discusses the presence of alien life around Saturn as well.

In Python you can do this:

1_000_000

https://www.python.org/dev/peps/pep-0515/

I guess the real question is:

"Why have foosball (table football) become so popular among management of software development companies?"

"Divided by a common syntax" also describes the relationship between Python 2 and Python 3.

Not necessarily.

There is even an argument that you want to be "the last" on the market.

For example, Google is the last "search engine" - it wasn't the first search engine on the market but it did grow to dominate the market when it arrived.

> In the long run, for readability and maintainability, ORMs win most of the time.

It depends. Anyone working on that code now needs to learn the ORM, the SQL and how to let the ORM generate that SQL for anything beyond the basics.

This can detect when a CVE vulnerability is fixed but how would you know the version number at which it was introduced?

Would adding structure help in managing the work better?

It can become difficult to convince management of hiring (paying) more people when there are improvements that should be made first.

- Determine who you need to convince on this matter

- Find out what metrics they care about (time lost, money lost, potentially employees lost, clients lost).

- Formulate your proposal in a way that emphasises how those metrics will improve by hiring more developers.

Even if you get paid more, you still spend time learning knowledge and skills which aren't easily transferable to your next employer.

You can't get that time back so long-term it's probably better to develop software in a more modern ecosystem.

Having said that, I don't know your local market or industry.

You've already identified that it may not get much traffic and it isn't monetizable with two big ad networks.

It's worth experimenting with a few things but you may just need to move on to another project that has better chances.

Dropbox

https://news.ycombinator.com/item?id=8863

It is essential to balance work with play. So you should not feel bad to play video games from time to time.

But if you're always doing things that involve a lot of thinking (work, study) it may be good to balance that with exercise or creating things with your hands.

If your work is not very exciting and it's unlikely to change then you may need to consider changing jobs.

The changelog should be a document written by humans for humans.

So you manually maintain the changelog while working on fixes / features and you add any remaining notes just prior to each release.

You can automatically remove six from your codebase after you're Python 3.x only. So six can be a possible solution (provided you have automated tests).