luord

9 ms·

31.
by luord 5y ago
Not that the article itself didn't already have some odd takes, to say the least, but I find it a bit ironic that they talk about design with seeming authority when that site has a very strange anti-feature where every few minutes eyeb
32.
Understanding quantum computing through drunken walks(stackoverflow.blog)
1 points by luord 5y ago|1 comments
33.
Let's replace the term “technical debt”(morethancoding.com)
2 points by luord 5y ago|1 comments
34.
The must-ask question for your software engineering interview(morethancoding.com)
3 points by luord 5y ago|1 comments
35.
How to write software that is ready for the world(morethancoding.com)
1 points by luord 5y ago|0 comments
36.
The argument against clearing the database between tests(calpaterson.com)
1 points by luord 5y ago|0 comments
37.
A Natural History of Beauty(meltingasphalt.com)
1 points by luord 5y ago|0 comments
38.
by luord 5y ago
Well, as an avid movie watcher who absolutely loves the theater experience, I truly do hope they never go away, and that my hypothetical children get to experience them too.
39.
by luord 6y ago
> It turns out Kubernetes is actually perfect for small teams As long as at least one of them is an expert on kubernetes. In this case, the one person in the team is that person, and as he points out in the article, he's using it be
40.
by luord 6y ago
Probably, the best answer to the "programming is easy" mindset I've read is this article[1] about whether software engineering is actually engineering. Turns out we are engineers, and we're not even that special as far
41.
by luord 6y ago
> I don't believe this until proven otherwise with actual data. I don't remember the last time that a piece by Uncle Bob or Martin Fowler—and they're just two examples, I've seen quite a few more who are generally met
42.
by luord 6y ago
I can't believe it (I'm kidding; I totally can). I like that some of them mention the excavator (<3).
43.
Anatomy of a Targeted Ransomware Attack(blog.cloudflare.com)
1 points by luord 6y ago|0 comments
44.
Pair with Non-Engineers(engineering.atspotify.com)
1 points by luord 6y ago|0 comments
45.
Open sourcing Protocol fuzzer community edition(about.gitlab.com)
3 points by luord 6y ago|0 comments
46.
Profiling Python code with py-spy(wrighters.io)
2 points by luord 6y ago|0 comments
47.
The bug bounty council at Gitlab(about.gitlab.com)
2 points by luord 6y ago|0 comments
48.
Capturing every change from Shopify's sharded monolith(shopify.engineering)
2 points by luord 6y ago|0 comments
49.
A product's Vue 3 migration: A real life story(suade.org)
2 points by luord 6y ago|0 comments
50.
Spotify's new experimentation coordination strategy(engineering.atspotify.com)
3 points by luord 6y ago|0 comments
51.
PyPy's Blog Has Moved(morepypy.blogspot.com)
2 points by luord 6y ago|0 comments
52.
Serious security: Webshells explained in the aftermath of HAFNIUM attacks(nakedsecurity.sophos.com)
3 points by luord 6y ago|0 comments
53.
An Introduction to JavaScript SDK for CloudEvents(developers.redhat.com)
1 points by luord 6y ago|0 comments
54.
Search crimes – How the Gootkit gang poisons Google searches(nakedsecurity.sophos.com)
1 points by luord 6y ago|0 comments
55.
When Everyone’s a Genius: A Few Thoughts on Speculation(collaborativefund.com)
83 points by luord 6y ago|76 comments
56.
Keeping developers happy with a fast CI(shopify.engineering)
2 points by luord 6y ago|0 comments
57.
by luord 6y ago
Last weekend I decided to remove all third party services/javascript from my website, replacing them with external links (for the share button or the contact form), nothing (for google analytics[1]) or with web mentions (for disqus). N
58.
Making complex topics stick (Part 2: Composition)(architectelevator.com)
4 points by luord 6y ago|0 comments
59.
Solving the data integration variety problem at scale, with Gobblin(engineering.linkedin.com)
2 points by luord 6y ago|0 comments
60.
by luord 6y ago
Damn, I must say that it's rare that I do find something so compelling yet so radically different to how I usually work[1]. Which is not to say that I think I'm an expert; if anything, it's because I don't know how much

More ›