fpereiro

36 ms·

61.
by fpereiro 7y ago
Thanks for your comment! - I don't use lockfiles - instead I use very very few dependencies, and I always target a specific version of each of them. I know this is not the same as a shrinkwrap, but I'm crazy enough to feel that pa
62.
by fpereiro 7y ago
You raise a great point. The web frontends I write always draw views entirely through client-side js, and interact with the server mostly through JSON. The only HTML served is that to bootstrap the page, plus static assets (js & images)
63.
by fpereiro 7y ago
It's perfectly possible and probably won't add much complexity or significant cost. I have no experience, however, in configuring ELB with HTTPS - usually I just go with the known quantity of a local nginx.
64.
by fpereiro 7y ago
Thank you for your suggestion! However, I'm a sucker for text diagrams (ever since I saw them in Jonesforth: https://github.com/nornagon/jonesforth/blob/master/jonesfort... ), so I strongly prefer to
65.
by fpereiro 7y ago
I like dealing with the underlying OS - well, not precisely like, but rather the absence of an intermediate layer between the OS and me. Fortunately, dealing with the OS is very straightforward. However, if Heroku works well for you, by all
66.
by fpereiro 7y ago
It's actually a fine solution and I often do this with infrastructures that I don't intend to maintain myself. In general, however, I try to minimize complexity, and having an external service feels a tad more complex than running
67.
by fpereiro 7y ago
Glad you liked the article! I don't have recommendations for other articles like these; most of what I wrote came from personal experience or things I learned directly from other people working with me. I also have learned a lot from w
68.
by fpereiro 7y ago
Will take a look at Fabric, thank you!
69.
by fpereiro 7y ago
I fully concur with your last statement. I find that the main advantage of having less moving parts is that there's exponentially less things that can go wrong - and that makes reliability possible with very small teams. The setup cost
70.
by fpereiro 7y ago
You raise interesting points! In general, I don't use Vagrant. I simply use my host OS (Ubuntu) and my local node & redis. There's usually no further moving parts than these, so it is easy to achieve development in an environm
71.
by fpereiro 7y ago
The main reason I use nginx is because it is so easy to configure HTTPS with LetsEncrypt & Certbot. Perhaps there's an almost equally easy solution now that only uses node, but last time I checked (2018) it was messy. In this art
72.
by fpereiro 7y ago
Wow, I didn't know that AWS had a managed redis service! I thought Elasticache was only for Elasticsearch. Thank you for pointing this out. In my experience, setting up redis is very easy and not time-consuming; what is not trivial is
73.
by fpereiro 7y ago
Fully agree. 20-50ms for something like S3 is fantastic and proof that we live in the future. S3 is only slow when compared to interacting with redis or a FS layer powered by node (by about an order of magnitude). That's why I feel tha
74.
by fpereiro 7y ago
Thank you for your suggestion about using samesite=strict! I'll look into it a bit more - the only downside I see is support for older browsers, which is a personal vice I can't kick. If I see that there's no elegant CSRF sol
75.
by fpereiro 7y ago
Passionately agree with thinking a lot before adding an element to your infrastructure. That might just be the main point I'm trying to make in the document. I love the idea of infrastructure as code and at some point I will try to wri
76.
by fpereiro 7y ago
Wow. I wasn't expecting this level of interest, not in a million years. I'm very grateful (and a bit overwhelmed!). Thank you for your thoughtful comments. I just added a few more clarifications to the document, mostly inspired by
77.
How I write back ends(github.com)
521 points by fpereiro 7y ago|186 comments
78.
by fpereiro 7y ago
I can highly recommend James Clear's Atomic Habits book. A lot of what has worked for me in terms of habits comes from there.
79.
by fpereiro 7y ago
Completely agree, I don't even try it anymore after many many failures. That's why I meditate and do some journaling first. I intersperse pushups at the beginning of the routine, but the core workout happens at the end, and for go
80.
by fpereiro 7y ago
You make a great point. I actually do all this after waking up earlyish to get my daughter ready for daycare and walk her there and back. I'm also very lucky in that I work from home, so skipping the commute helps a lot. Perhaps a bett
81.
A bulletproof day-starting routine(federicopereiro.com)
14 points by fpereiro 7y ago|19 comments
82.
My Goals for 2020(federicopereiro.com)
1 points by fpereiro 7y ago|0 comments
83.
Some Notes on Habits(federicopereiro.com)
1 points by fpereiro 7y ago|0 comments
84.
On Software Simplicity(federicopereiro.com)
1 points by fpereiro 7y ago|0 comments
85.
A Manifesto for Progress in the Twenty-First Century(federicopereiro.com)
2 points by fpereiro 8y ago|0 comments
86.
My notes on learning React(github.com)
1 points by fpereiro 8y ago|0 comments
87.
Asymptotic software(federicopereiro.com)
1 points by fpereiro 8y ago|0 comments
88.
Hard, simple, rewarding(federicopereiro.com)
1 points by fpereiro 9y ago|0 comments
89.
by fpereiro 9y ago
You're absolutely right; hexnot is way less visual than the standard notation. I am a quite non-visual person and I think that's part of the reason I'm inclined towards this approach. Hexnot seems to draw more on the formal a
90.
by fpereiro 9y ago
Hi Dave, Thanks for checking it out! I definitely agree; traditional notation is quite more suggestive, though I don't know how much this is because of previous exposure to it. The long term question here, I believe, is whether the cog

More ›