nercury

8 ms·

1.
by nercury 2y ago
I hope the wages of sales people are lower than that of a calculator.
2.
Eliminating Memory Safety Vulnerabilities Once and for All(darpa.mil)
1 points by nercury 2y ago|0 comments
3.
by nercury 2y ago
Extremely small island that stretches from New York to Atlanta..
4.
by nercury 2y ago
If someone spent their time learning their tools, they will make better choices when writing the code without any additional time cost. There are two variants of very similar code. Both do the same thing, both are readable and maintainable.
5.
by nercury 2y ago
Anything you say or do will be used against you by any future government. What's legal now, might not be legal tomorrow, and you will be jugged by your AI "friend". Welcome to dystopia.
6.
by nercury 2y ago
The real threat is AI arguing/competing with itself and wasting 90% of world's power.
7.
by nercury 2y ago
This is more of a preference for bridge to be visible in application. Also the bridge may seem simple at first, but it also may gain associated data, like created_at, order, etc.
8.
by nercury 2y ago
Yes, I would not put it just anywhere. But I have few rules about ORMs: - Proper DB design first. You should be able to remove the ORM and DB should still function as intended. This means application-side cascade operations or application-s
9.
by nercury 2y ago
Yeah, in a web app, one context per request. In desktop app... I have never used EF there.
10.
by nercury 2y ago
Pardon me for the tangent (just a general comment not directed to OP). What I have learned over the years is that the only way to properly use ORM is as a fancy query tool. Build the query, fetch/update data, MOVE THE DATA to separate
11.
by nercury 2y ago
struct Node<'a, 'b, 'c> { data1: &'a Data data2: &'b Data data3: &'c Data } Wow. It's like teaching C++ and starting from SFINAE. Or C# and starting from type parameter constr
12.
by nercury 2y ago
It's like destroying a factory when the chips it produces do not sell.
13.
by nercury 2y ago
Corporate prioritization is the ultimate cookie cutter, doomed to produce the most generic thing possible.
14.
by nercury 2y ago
If AMD did not come up with 64-bit extension, we would be saying goodbye to x86 architecture.
15.
by nercury 2y ago
This sounds like "You aren't having fun properly".
16.
by nercury 2y ago
That disappearing scrollbar is weirdly out of place.
17.
by nercury 3y ago
Yes of course. You have to demonstrate that you are very skilled at building with the particular bricks they use. Don't mention anything else to show your commitment to particular brick usage.
18.
by nercury 3y ago
Right, imagine a company where the team decides to use Macromedia Flash for game UI only because they need to deliver something working on the next sprint. And then everyone gets stuck with that decision for more than a decade.
19.
by nercury 3y ago
Say, you use the same foundation for both the game and tool. Nothing prevents you from building features on top that are optimized either for a tool or for a game! Plus you dogfood the system all the time.
20.
by nercury 3y ago
Bytes aren't bricks. Reshuffling them from scratch after a smallest change is cheap and fast. Taking advantage of that is not stupid. Proper communication and work with client is a skill, and architects have to deal with stupid reques
21.
by nercury 3y ago
Interesting, it acts as if hearing voices in the head.
22.
by nercury 3y ago
It pains to see the need for a microservice to even start thinking about system architecture. As if the additional database and additional set of classes could not be done on the same instance. And then everyone shrieks in pain when they se
23.
by nercury 3y ago
I admit I don't know enough about kernel development, but from general experience one common example is resource cleanup. Say, you have several resources that must be cleaned up in certain order. In C, you would just call the appropria
24.
by nercury 3y ago
I am Rust developer. My advice: favor less abstractions. Especially when interfacing with C, you can always make almost 1:1 rust interface. Start with that. Then, when common patterns start to emerge, do the data abstractions first, i.e. de
25.
by nercury 3y ago
I would argue that the bloat comes when the performance impact is not perceivable compared to the development time. The easiest optimization strategy is just to load it all up into the memory. Compare that to other strategy like catching pa
26.
by nercury 3y ago
If ants can smell where other ants have been, they are kind'a doing Dijkstra's algorithm. Is this the "swarm intelligence" the book is getting to?
27.
by nercury 3y ago
The more you use GPT, the more you will understand that it's not the replacement for your attention to the work. And without the attention to the work, you can't spot bugs, blatant inefficiencies, or better design choices - in oth
28.
by nercury 3y ago
I would not sing praises for Microsoft Flight Simulator 2020. First, the cockpit displays are rendered at lower framerate, because they take considerable chunk of frame time. Second... It may be fine to render display and UI using js, but i
29.
by nercury 3y ago
The biggest wrapper that gives guarantees is the standard library, and usually, when people say that Rust does not do something, they have standard library in mind. For example, standard library made the choice to hide panics in out-of-memo
30.
by nercury 3y ago
I would avoid saying that it's "Rust" that "gives guarantees". It paints Rust as this magical thing that will solve anything. My preferred explanation is that Rust provides better tools to build wrappers that can&#x

More ›