legorobot

7 ms·

1.
by legorobot 4mo ago
I thought this was how everyone worked. I wish it were :) This is the right way to do it. Whether using trunk-based development, git-flow, etc -- you're controlling the flow of merges in a particular direction. However, I think the
2.
by legorobot 8mo ago
I agree that there's a lot of complexity today due to the process in which we write code (people, lack of understanding the problem space, etc.) vs the problem itself. Would we say us as humans also have captured the "best" w
3.
by legorobot 1y ago
I think that's reasonable :) More stuff is more stuff, no matter how simple/complex the aspects of the code and reasoning for why it is that way.
4.
by legorobot 1y ago
I think my issue with this generalization is assuming the code itself is where complexity is measured and applied. For example, the Quake Fast Inverse Square Root[1] takes into account nuances in how floating point numbers can be manipulate
5.
by legorobot 1y ago
> Just taking the notion of "complexity". Reducing that to _just_ cognitive load seems to be a very poor analysis, when simple/complex ought to deal with the "size" of a structure, not how easy it is to understan
6.
by legorobot 1y ago
Definitely agree with this, I think ClickHouse can do a lot with joins if you don't implement them naively. Keeping the server up-to-date is a part of it too. They've made strides in the last year or two to implement more join alg
7.
by legorobot 2y ago
100% this. I have a set of commonly-used code in a repository we use at work. AuthN/AuthZ, code specific to our infrastructure/architecture, common http middlewares, error types, DB wrapper, API clients, OpenAPI Server generation,
8.
by legorobot 4y ago
We've used the s3fs-fuse library for a while at work for SFTP/FTP server alternatives (AWS wants you to pay $150+/server/month last I checked!) and it's worked like a dream. We scripted the setup of new users via a
9.
by legorobot 4y ago
Same experience for me too. I learned a lot, and integrating OAuth into a platform was pretty painless, including importing and managing users. It was the first time I felt like I can wrangle the OAuth spec and implementation, and really un
10.
by legorobot 4y ago
I haven't thought about it that way! I've not hit the GC as a performance wall when it comes to accessing nullable DB values yet. Thanks for the insight.
11.
by legorobot 4y ago
I think the idea is `sql.NullString` can be used to have a SQL NULL still be an empty string in Go (just avoid checking the `Valid` field, or cast to string -- no check necessary). It seems like the intent of a string pointer vs. `sql.NullS
12.
by legorobot 4y ago
I totally agree with this too! Sometimes its nice to have a project that's meant to go nowhere, but it teaches you a ton and you get a lot of that yak shaving out of the way. By the end you might have so little to show, but I found wri
13.
by legorobot 4y ago
Comfort in the unknown helps a lot with this -- creativity is also a skill that can be trained and tested like muscles. I usually get stuck in "cycles" where I know I'm not making progress, but I'm exploring my interests
14.
by legorobot 4y ago
My one tweak would be that in projects in development, the hard rules are less applicable. Sometimes I've found hard-coding some things (e.g. FIXME items) are to make it into production when developing a prototype and testing (< 1.0
15.
by legorobot 4y ago
There is -- anchors[1] :) [1]: https://marketplace.visualstudio.com/items?itemName=ExodiusS...
16.
by legorobot 4y ago
Totally agree. I've found that adding a timeline to _remove_ TODOs/DREAMS (whatever the team choice is) from code as a CI check is very applicable -- what you thought might be good at some point in the past may (and likely is) not
17.
by legorobot 4y ago
> This is a lovely way to look at it! I wish I had thought of that example too when I wrote about idempotency! I wrote a post about idempotence as well a couple months back ( https://chrisprijic.com/idempotency-is-key&#x2F