marcos100

11 ms·

61.
by marcos100 5y ago
A lot of times, the obvious _must_ be stated or else companies do whatever they want because "it's not written anywhere that I can't".
62.
by marcos100 5y ago
Played twice. Immediately knew that I should stop. Great game!
63.
by marcos100 5y ago
I feel you. Some people are saying that, if it works, it's not shitty code, but it's not the truth. I made a service that was reliable, but only because there are a lot of ifs inside the code that fixed bugs. It was really shitty
64.
by marcos100 5y ago
I like your analogy, but how do you find the perfect balance? I mean, you can play tetris at level 1 forever, but it is not ideal for productivity (unless you are really at level 1). You have to reach the level that you are comfortable enou
65.
by marcos100 5y ago
Love your comment. doc-comments are good because it explains well what the class/method/whatever are there for, sometimes with examples, that helps understand the code. But I hate that they use so much space inside the source code
66.
by marcos100 5y ago
Knuth's style allows code to be written in any order using named chunks. AFAIK, there are some types of notebooks that allow the use of chunks, but I've never seen people writing in those.
67.
by marcos100 5y ago
It's better to have a business with profits and things to fix up than having no business. It's a tradeoff that has been proved to be valid. As an engineer, it's hard leave some things half baked, but it is what it is.
68.
by marcos100 5y ago
Is it scaling well? Do you have a lot of concurrent users? I'm thinking o using blazor server in a production app, but the latency and higher costs may be a problem. Wasm is not ideal for me because of the high initial payload.
69.
by marcos100 5y ago
The problem is knowing what is "good enough". It comes with experience and, if you're doing something new to you, I think it's hard to assess. You may probably tell what went in hindsight, but even then, it's just o
70.
by marcos100 5y ago
Function comments should explain what it does, and comments inside functions should explain the how. // Receives n >= 0 and returns the n'th fibonacci number int fib(int n) { // We use the memoized ve
71.
by marcos100 5y ago
I agree with you. It will efficiently allocate resources for an inefficient application. But when your system can't handle the load anymore, you'll have to allocate more resources and k8s will handle it for you like magic. It&#x27
72.
by marcos100 5y ago
For those who only read the quote "premature optimization is the root of all evil", here's the context: "Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of the
73.
by marcos100 5y ago
When you program without performance in mind, hw is always your constraint. k8s is a blessing because you can scale out easily and is a curse because you can scale out easily.
74.
by marcos100 5y ago
The charts are ok for the purpose of visualizing the performance of the protocols. At least for me, they are side-by-side with the same min and max values and is easy to compare. The purpose is clear and starting from zero adds nothing of v
75.
by marcos100 5y ago
Totally, it's like admitting that you don't know how to hire. And it's worse if HR is involved.
76.
by marcos100 5y ago
I thinks it's easier to engage new people into your technology with this approach. Once they're hooked on, they'll have to learn the details. I don't know if you're old enough, but Rails got a nice momentum with the
77.
by marcos100 5y ago
It's about touch typing only. If you start changing other variables, the comparison doesn't make sense anymore (to the discussion). Of course your senior engineer that wrote the thing will be more productive than your intern that
78.
by marcos100 5y ago
You touch type not to break a world record. You touch type because you can write without thinking about the keyboard, just like you don't think when using or arms or legs, and it's faster to correct an error that you made. Imagine
79.
by marcos100 5y ago
In brazilian portuguese we have an expression called "engenheiro de obra pronta" (something like "engineer of a completed construction"). It means that's easy to talk about a finished work, it's faults, how it
80.
by marcos100 5y ago
Kind of. The dataset is small and he probably need to create the database at most once per day and have to read a lot more for his analysis/exploration. Columnar databases are a good fit here.
81.
by marcos100 5y ago
Yes, free market is not free-so-I-can-do-anything. It must have some regulations, or else all the corporations will become evil.
82.
by marcos100 5y ago
I think patio11 recommends these tiers for low touch B2B SaaS with 10% discount for annual plans.
83.
by marcos100 5y ago
You're small enough that they don't care. If you grow big, then they buy your or copy your business and when that happens you'll have earned a lot of money, hopefully.
84.
by marcos100 5y ago
I don't know if Chrome has anything similar, but Firefox reader view is awesome for formatting an article and making it easier to read.
85.
by marcos100 5y ago
Yes, you should persist the raw user input. Why would my non-html gui app show some escaped html?
86.
by marcos100 5y ago
The authors of "Design Patterns" didn't create anything new, they just documented common patterns used in the industry and gave them a name. So, when you say "I used X pattern here", I can have a high level architec
87.
by marcos100 5y ago
> I blame schools for teaching kids to reach word limits, instead of how to express themselves concisely. I thought the same in the past. But I think it's a good idea to enforce word limits to make them think more about the subject
88.
by marcos100 5y ago
If you're throwing everything the customer have input then you have a poor written application. Not inserting bad data is much better than trying to make sense of inconsistent data because you don't know what is true or not.
89.
by marcos100 5y ago
Strava famously outlined hidden military bases.
90.
by marcos100 5y ago
People who is interested in rust maybe want to see how it was used. The author could have just kept "Taming Go's Memory Usage". Maybe they never considered rewriting in rust. The pros and cons looks like just some random argu

More ›