ainzzorl

8 ms·

1.
by ainzzorl 3y ago
When did it become acceptable to write things about other people as he writes about Jeanine Banks? Even if everything he says about her is true, it still feels incredibly rude to say it in public.
2.
by ainzzorl 5y ago
Software engineer from Moscow. This is an absolute disaster for us. I can't imagine how and when we recover from this. The damage already made to our country is going to be devastating, and it's not even over yet. I even envy Ukra
3.
by ainzzorl 5y ago
The best universities in the world make their courses available online for free - what a time to be alive! I wonder if it's still possible to make money selling online courses in CS.
4.
by ainzzorl 5y ago
Not exactly this, but "Dragon's Egg" by Robert Forward takes place on a neutron star with a surface gravity billions times that on Earth.
5.
by ainzzorl 5y ago
> Amazon basically didn't touch it since the acquisition almost a decade ago. This is what I love about it. When something works for me (and Goodreads does), I don't want it to change.
6.
by ainzzorl 5y ago
This is a great comment: instead of making generic arguments, you actually tried to show how to do it better. Thank you. I don't find the comments in the original code distracting, but I do like your version better. > I'm also
7.
by ainzzorl 5y ago
While I agree with the general sentiment, the first example in the article IMO demonstrates how "what" comments make understanding code easier. When I first read that code, I was pleasantly surprised how easy it was to understand
8.
by ainzzorl 5y ago
A lot of code files starts with lengthy copyright notices, and no one seems to mind. I find comments at the top very easy to ignore if I work on that code regularly. Also, I don't think I've ever seen comments at the bottom of a f
9.
by ainzzorl 5y ago
Thanks! If you know some good examples, please consider proposing them: https://github.com/ainzzorl/goodcode/issues/new?assignees=&l...
10.
by ainzzorl 5y ago
I agree that some comments in the first example are unnecessary, e.g. the one pointed out in [0], but I find comments like that at worst useless, but not harmful. They have a potential to become harmful if someone updates the code but doesn
11.
Writing Well-Documented Code – Learn from Examples(codecatalog.org)
333 points by ainzzorl 5y ago|142 comments
12.
by ainzzorl 5y ago
Lambda indeed is not the right tool for this. It sounds like you need some infra that can auto scale - there are many ways to do it on AWS (EC2 auto scaling, ECS, EKS), any other cloud provider, with Kubernetes...
13.
by ainzzorl 5y ago
Please consider adding an FAQ about how it compares to "native" AWS offerings, because it resembles a few of them. E.g. Lambda ("run your code" without "start a cloud server" and "turn it off"), ECS (
14.
by ainzzorl 5y ago
Sounds cool! Will it support only "basic" DynamoDB features (reading/writing records) or some "advanced" things too, like GSIs/LSIs, streams, fine-grained access control, TTLs, backups?
15.
by ainzzorl 5y ago
I've been assembling and annotating a collection of instructive and self-contained code examples from open-source projects, to make it easier to learn by reading good code. Code Catalog: https://codecatalog.org
16.
Code Catalog – a collection of code examples from prominent open-source projects(codecatalog.org)
7 points by ainzzorl 5y ago|1 comments
17.
by ainzzorl 5y ago
Yes. I was thinking to start with smaller examples showing how they write code at <big project> without necessarily understanding the big picture, but bigger examples would be great too eventually. Something like http://aos
18.
by ainzzorl 5y ago
You blog about interesting things, subscribed :-D
19.
by ainzzorl 5y ago
Replied in another branch: https://news.ycombinator.com/item?id=27687724
20.
by ainzzorl 5y ago
I started a repository for it: https://github.com/ainzzorl/goodcode . Please follow! It's empty for now, but I included a few examples [1] of what I'm going to annotate and add there. [1] https://gi
21.
by ainzzorl 5y ago
> "There are so many projects on GitHub – pick one you like and see how they did it." But most successful projects are quite large; where do you start from? I'm working on a slightly similar project motivated by this probl