daltonpinto

5 ms·

1.
by daltonpinto 2y ago
It is not about speed, is about quality. When I met the other 2 blind people, one of them joked that yes, they were very organized, but because they had to be, unlike us, being not organized wasn't an option for them. I don't ques
2.
by daltonpinto 2y ago
Exactly! Not because it is split it means that was well split. If you can reason where something should be, it may be badly organized. Even single file projects can be organized. If is small enough and makes sense, why not? But even in a sm
3.
by daltonpinto 2y ago
Of course that are good things and maybe I wrote in a too much harsh way. Linting features and autocompletes are nice, also autocomplete features are nice to have. The issue that I pointed mostly resonates with the idea that depending on LS
4.
by daltonpinto 2y ago
Not only learned, but it changes with time. When reviewing code, the reviewer responsability is not only to make sure that it works, otherwise tests and its coverage would be enough, but they aren't. If a reviewer sees that something d
5.
by daltonpinto 2y ago
When I mean organized it means having a structure that segrates responsabilities. It could be applying DDD or some other pattern with that makes sense to the team. If you are using a framework like Rails, learn well its conventions, follow
6.
by daltonpinto 2y ago
This question reminds me of the first time I met a blind programmer. I asked him how he managed to code, and he replied with something that stayed with me: a good programmer should organize software in such a way that every piece of code ha
7.
Show HN: Simple mathematic syntactic sugars for Ruby(github.com)
2 points by daltonpinto 3y ago|0 comments