ElatedOwl

6 ms·

1.
by ElatedOwl 26d ago
> They either focus on the wrong things when developing software, they have a very shallow knowledge and lack of regard of how difficult good engineering is, or they’re utterly clueless and rely on good soft skills and politics. I’ve wor
2.
by ElatedOwl 3mo ago
the point of that section is that attackers and security researchers will use / are using loops, and you as the maintainer are not able to opt out of others doing this. an unwilling participant.
3.
by ElatedOwl 4mo ago
My favorite part of Ruby is the testability. You can test anything, easily, without having to make interfaces and other design decisions specifically around tests. Testing anything in Ruby is dead simple, and agents are very good at writin
4.
by ElatedOwl 4mo ago
no, these meetings are still hot garbage. half the time you’re going to discover the right decision / path while you’re coding. focus time went from hammering code to figuring out how to solve the problem. PRs are now how we exchange i
5.
by ElatedOwl 7mo ago
The author effectively argues deep thinking is dead, that people are no longer going to take the time to understand the problem and solution space before they solve it. I think that’s untrue, I think it’s /more/ important than bef
6.
by ElatedOwl 7mo ago
I think good code is even more important now. People talk about writing the code itself and being intimate with it and knowing how every nook and cranny works. This is gone. It’s more akin to on call where you’re trudging over code and unde
7.
by ElatedOwl 8mo ago
> This post brings up a lot of (imo true) points that I honestly can't share with the ai-lovers at work because they will just get in a huff. But the OP is right - we automate stuff we don't value doing, and the people automati
8.
by ElatedOwl 8mo ago
I keep seeing “Claude image understanding is poor” being repeated, but I’ve experienced the opposite. I was running some sentiment analysis experiments; describe the subject and the subjects emotional state kind of thing. It picked up on a
9.
by ElatedOwl 1y ago
This will get written off as victim blaming, but there’s some truth here. I don’t use Claude code for everything. I’ve fallen off the bike enough times to know when I’ll be better off writing the changes myself. Even in these cases, though,
10.
by ElatedOwl 1y ago
I agree with that being fastest, but not cheapest. In my experience these one off reports are very brittle. The app ends up making schema changes that are breaking to these one off reports, and you usually don’t find out until it goes to pr
11.
by ElatedOwl 2y ago
> As the recent US election has shown, it's not what you say - but how you say it, that counts. Are you implying that Biden spoke with more confidence than Trump, but Harris did not?
12.
by ElatedOwl 2y ago
load_async is still concurrency, but not parallelism. The queries themselves can run parallel, but when materializing AR objects e.g., only one thread can run at a time. A greedy thread in process will still subject you to GVL waits
13.
by ElatedOwl 2y ago
I spent 10 years doing C#, and the last 3 doing Ruby. I never thought of N+1 as that big of an issue. These queries are typically fast (1ms * 100 is still only 100ms…) and multithreaded web servers are non blocking on IO like database calls
14.
by ElatedOwl 2y ago
Writing is really beneficial for exploring the problem space. Many times I’ve confidently thought I understood a problem, started writing about it, and come away with new critical questions. These things are typically more visible from the
15.
by ElatedOwl 2y ago
I agree that LLMs capabilities with a language are going to be extremely relevant. Community, API consistency, and whatever other factors that are going to increase LLM usefulness will decide the popularity of languages in the coming years.
16.
by ElatedOwl 2y ago
> both our BMI's hover just over 30. > We're active, we eat well Respectfully, you are both obese. If you’re ok with that that’s ok; but to say your diets are appropriate is telling yourself a lie.
17.
by ElatedOwl 2y ago
Agree the DB side is overstated. These particularly suck though in ruby on multithreaded servers (eg puma), where N+1s are constantly giving control of the GVL to another potentially greedy thread. I’m sure python multithreaded servers will
18.
by ElatedOwl 3y ago
imo a properly configured Postgres server should have enough RAM to keep any hot data in cache. The cached path is the accurate measurement.
19.
by ElatedOwl 6y ago
I manage at a lower level, a team of developers. I’m a big fan of stating a clear goal and letting the developer/team decide how to tackle. I may have suggestions, I may veto proposed solutions if I have legitimate problems with it, bu
20.
by ElatedOwl 7y ago
Spot on with cost, as with everything you have to be pragmatic. Tests are great for: * High risk items (large consequence when it goes wrong) * Documentation * Weird unintuitive things We had a C# project recently that needs to detect chang
21.
by ElatedOwl 7y ago
For portable non-concentrate, Mighty by Storz and Bickel is hands down the best device I've used. The engineering is flawless: amazing battery life, extremely durable, easily replaceable wear/tear parts, use while charging, fast h
22.
by ElatedOwl 7y ago
Chargebacks are a costly process. The processor will charge a fee ($15-$25 is a fair guess) and you lose the money from the transaction.
23.
by ElatedOwl 7y ago
>I often have this weird fear that I wont accomplish anything in my life like it is some sort of personal failure. Completing a big project, setting a new weight lifting or running PR only leaves me feeling empty. I've come to reali
24.
by ElatedOwl 7y ago
I wonder if this will have Visual Studio's Go To Implementation feature. If so, I really hope this gets fully integrated in Azure DevOps repos. It's a great experience right now, but I pretty often end up pulling the repository do
25.
by ElatedOwl 7y ago
Cash comes with a fee; armored trucks, safes, money-handling mistakes, etc.
26.
by ElatedOwl 8y ago
It isn't just the card brand taking a slice. At best it's a 3 party system between the Gateway (Auth), Acquirer (person actually paying the merchant), and the card brand. I don't think it's uncommon for their to be middl
27.
by ElatedOwl 8y ago
Stripe as an acquirer does have bank relationships. Visa isn't paying the merchant directly.
28.
by ElatedOwl 8y ago
Our team inherited a tangled spaghetti mess of a client facing API. There were some additional requirements that needed to be added and we quickly discovered some serious security issues. We considered a full rewrite, but this was too time
29.
by ElatedOwl 8y ago
If you're not happy with where you're at in your career, don't worry, it's totally because you're too smart .
30.
by ElatedOwl 8y ago
Netflix, Walmart, etc. solve a much different set of problems than most shops. I'm proud to work for a small company with simple (but rapidly changing) requirements. :)

More ›