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

Points: 2

# Comments: 1

What prevents that we, just move the goal post? Moving the bug from code to spec? The spec must always be simpler and more easily to understand and debug than the code. But in praxis that means it can’t be fully specific in most of the use cases?

It seems to favor the compact and efficient kind of code that is brittle in the hand of a mildly competent junior dev, or a heavy multitasking senior.

I like smart code, in fun projects, but on the job I prefer fast to read and to reason code. Don’t try to be fancy.

So I guess that’s a book to challenge my assumptions. I like that. Thx.

I still would prefer a true Icon.

But it is down right evil to impose extraterritorial sanctions against a company and preventing other to do business with them.

Then i realized that i was offtopic in a kinda funny way

I like to request your comment on a similar topic. While coding in go - I often find me asking: is this package go-routine save? Many times I find the answer in the doc's or can ask on the internet, sometimes I need to look at the code.

"go routine safety" is just like the color in the rant of munificent.

On a current project I would like to assert that a user provided callback is a pure function - there we got another color!

those two colors are alike - they represent meta informations about an entity (function, package, struct) and they are about the behavior of the entity.

They also have something to do with boundarys - tho my English skills deny me to elaborate :(

I wounder...

Do you know other kinds of colors?

Is that coloring bothering you? And if not how do you approach it?

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

Points: 2

# Comments: 0

I could need a pointer, I have the feeling I am one inch away from understanding - but still something is missing. could you provide a hint or a resource or an sample implementation?

it's about creating a dynamic user model for my CMS. I observe the user and record it's interactions with the web page. I also managed to lift those interactions in a business domain - ie. interpret interactions with certain HTML Elements as interaction with a product / article / topic.

I got the data - as stream of filtered interactions - but still the math needed to create an actionable model eludes me. :(

I am looking for ways to aggregate the data into some expressions like "user got strong interest in blue lamps" the CMS could use to make decisions about content placement.

how can I organize the interaction in a way to draw sutch conclusion? what kinds of algorithm should I look into?

thx in advance, Merkur

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

Points: 1

# Comments: 0

mysqldump got a CLI argument to provide the password! As far as I know - visible to anyone with some access on the system. the documentation warns about that and suggest to create a config file to store the password.

security is a spectrum - but if it's about password storage in modern web applications live on the lower end.

I am increasingly frustrated by that - and if I raise concerns many admins stick to binary security "storing stuff unencrypted on disk is okay, cause the attacker is inside already" followed by "you must store the key somewhere" it's wrong and it's true at the same time. it's also sad - because not only the users, but also the ppl paying us trust us to keep them save. and we don't. :( we can say "it's a spectrum" and we are truthful - but we just can't keep em safe. I think it's important to recognize that simple fact.

...or is it me who is just meticulous?

but still..some rhetorical questions: Is KMS based on this concept? Is it's implementation open sourced? Is it verified to run unchanged in the instance I pay? Who is verifying it? Who is paying the one verifying it? Can I meet him / her to drink a coffee and build trust between us?

pls, do not misunderstand me. I got more trust in the amazon techs than in my own ability to admin a complex linux system on bare metal. But while all that is great progress toward security we still need to make a leap to find a solution. don't we?