hbrn

25 ms·

241.
by hbrn 4y ago
You're confusing correlation with causation. The evidence suggests that buying expensive cars makes you rich.
242.
by hbrn 4y ago
All of your dependencies are individual repositories. The whole world runs on polyrepo. If that's not a success story, I don't know what is.
243.
by hbrn 4y ago
> Not updating dependencies is the equivalent of never brushing your teeth That's a strawman: the choice is not between updating and not updating. The choice is between updating on my terms or not. I recently updated stripe from 2.x
244.
by hbrn 4y ago
Polyrepo scales to thousands coders without anyone even noticing, and that's the beauty of it. Just look at the size of node_modules in an average project. You stand on the shoulders of thousands of other engineers and you don't e
245.
by hbrn 4y ago
For anyone who complains about dictatorships, remember some of the most resource-abundant countries are dictatorships. Those companies should be one of last places to look for good software development practices. They have absolutely no inc
246.
by hbrn 4y ago
One thing I often tell people is that if a particular technology makes it easier to work with code that's 10 layers deep, it will also make it more likely that people will write code 10 layers deep where they would previously do 5 laye
247.
by hbrn 4y ago
You're comparing database to a service. NOTAM is real-time, google.com is not. By that standard google.com is always down.
248.
by hbrn 4y ago
The risk of focusing on code and architecture too much is that it will never break. Not because it's very reliable: because you have no users. Part of being a professional engineer is recognizing that your knowledge is always limited.
249.
by hbrn 4y ago
Latter has a risk of attracting fanboys and detracting product engineers.
250.
by hbrn 4y ago
Not writing complex systems is a skill (that most engineers lack).
251.
by hbrn 4y ago
> Not everyone is as diligent and not everyone will have thought through/remembered all those edge cases when they happen to end up maintaining/adding to your code. Edge cases could be due to accidental complexity. In this case
252.
by hbrn 4y ago
> Then you make a change, that change impacts 10 of those. You now need to go back and re-test, manually, those 10 thing and check they haven't broke. Unit tests provide no guarantee that those 10 things haven't broke. They c
253.
by hbrn 4y ago
The problem is that writing good tests is harder than writing original code. And what happens in most companies? We hired a junior engineer and don't have work for them... let them write tests!
254.
by hbrn 4y ago
> when a request comes into job/views.py or load/views.py then we immediately start working with JobLoadMediator to handle business logic between the two? In my world, mediator.views and job.views would likely have different au
255.
by hbrn 4y ago
> I really do not understand the debate on monoliths and microservice anymore. > Don't go extreme in any direction. Context context context That is exactly why debate occurs. All religions, be it microservices or TDD, are taking
256.
by hbrn 4y ago
> The tragedy of the design of computer programs is that we have no theory of efficiency, no theory of what is most optimal Yeah, that's just fundamental law we have to accept. I believe the reason we don't have a theory of eff
257.
by hbrn 4y ago
This is good enough to break circular dependencies between individual modules, but keep in mind that circular dependencies between the apps remain (e.g. job depends on mediator, mediator depends on job). I usually prefer to resolve those to
258.
by hbrn 4y ago
> Would that mediator be another app? Yes! It is an app that might not even have any model classes. But it will contain business logic. And it will probably speak domain language, which is great. If you're lucky, those two other app
259.
by hbrn 4y ago
> Because it’s mature, well integrated with Django and is a path so well-trodden > Cron is awful for this use-case. You end up just inventing Celery Isn't it the other way around? Crons are way more mature, well integrated (mgmt
260.
by hbrn 4y ago
The short answer is yes. The long answer is if two entities are updating each other you might benefit from shifting all update responsibilities to one of them. Or even to a third entity that knows about both and keeps those two isolated fro
261.
by hbrn 4y ago
Are you just trolling? Or your cronjobs are really making http requests?
262.
by hbrn 4y ago
Oh sweet summer child. Please read this carefully: https://folk.universitetetioslo.no/trygver/1979/mvc-2/1979-1... Business logic is supposed to be reused. Controllers in web frameworks (views in Django) expo
263.
by hbrn 4y ago
I think the idea is that instead of thinking "here's the object I'm serializing" you should think "here's the view (endpoint) I'm serializing for". Contrary to what people usually think, the shape of
264.
by hbrn 4y ago
Typically it goes like this: 1. You found one case where complexity is essential. 2. That one case is not consistent with the rest of your app, and you were taught that inconsistency is bad. 3. Since you can't remove complexity from th
265.
by hbrn 4y ago
Ah, the typical "where to put business logic in Django". M in ActiveRecord MVC web frameworks is deeply misunderstood. M is not "data model" (it would be called DVC if that was the case). M is your domain model. It&#x2
266.
by hbrn 4y ago
> I don't know if this task is just an especially bad fit for me, or if my mental abilities are declining? > The code I'm porting is average code, not terrible, but plenty of little things to complain about. There might be a
267.
by hbrn 4y ago
Do you see any problems with that? Like, the fact that it is trivial to exploit?
268.
by hbrn 4y ago
> 4.7% yearly they pocket on more than $50 billions. Without giving the returns back to the USDC holders (as far as I know people keeping USDCs in their own private wallets do not get any yeld). They do if your USDC is in Coinbase accoun
269.
by hbrn 4y ago
Quantum physics is still physics. The fact that it's not computable (non-deterministic) is not even disputable at this point, it's the nature of reality. The only questionable thing is whether quantum effects are essential in brai
270.
by hbrn 4y ago
> The goal is that the sheer recurrence is enough to convince people of the negative impact on innovation and societal growth big companies have. I don't think anyone disagrees that monopolies are cancer. The hard part is coming up

More ›