chipdart

5 ms·

1.
by chipdart 2y ago
> You can learn from everyone around you, regardless of their status. There is no "universal developer experience curve", everyone has more or less knowledge on a field or with a specific tool/framework. There's a big
2.
by chipdart 2y ago
> But a warning: you will spend years in the weeds, focusing on things that don't matter. That sums up anyone's college experience. The hard part is telling apart what doesn't matter from what does. More often than not, wh
3.
by chipdart 2y ago
> C# has this: This is only syntactic sugar to allow using object initializers to initialize specific member varabiles of a class instance instead of simply using a constructor and/or setting member variables in follow-up statements
4.
by chipdart 2y ago
> The problem is that programming languages have always focused on the definition side of types, which is absolutely necessary and good, but the problem is that only limiting use by, e.g., "protected, private, friend, internal, ...&
5.
by chipdart 2y ago
> For every project/job/app that needs the AWS levels of resilience (...) I don't think you're framing the issue from an educated standpoint. You're confusing high-availability with not designing a brittle servic
6.
by chipdart 2y ago
> They run a Wireguard network between the nodes so you can have a mix of on-premise and cloud within one cluster. Interesting. A quick search shows that some people already toyed with the idea of rolling out something similar. https:&#
7.
by chipdart 2y ago
> We will charge € 1/TB for overusage. It sounds like a good tradeoff. The monthly cost of a small vCPU is equivalent to a few TB of bandwidth.
8.
by chipdart 2y ago
> yes, like i said, (...) I'm sorry, you said absolutely nothing. You just sounded like you were confused and for a moment thought you were posting on 4chan.
9.
by chipdart 2y ago
I loved the article. Insightful, and packed with real world applications. What a gem. I have a side-question pertaining to cost-cutting with Kubernetes. I've been musing over the idea of setting up Kubernetes clusters similar to these
10.
by chipdart 2y ago
> Demoralized or denormalized? The database is denormalized. The developers are demoralized.
11.
by chipdart 2y ago
> Are you one of the reasons why SEO spam sites are clicked on so often? I don't think your poorly thought-through personal attack has any relevance to the topic. I clicked on the article because there was a submission in HN with th
12.
by chipdart 2y ago
> I'm an independent developer right now, building systems for businesses and there is literally no better way to deliver line-of-business internal applications than via a monolith. This is the same sort of myopic, naive, clueless t
13.
by chipdart 2y ago
What an appallingly bad article. It starts with a premise only backed with an unsubstantiated and outright false appeal to authority ("the likes of Amazon are moving to monoliths!1") and proceeds to list a few traits that are so w
14.
by chipdart 2y ago
> The whole point of CI is to automatically verify the code. Against errors and regressions. Meaning, stuff that breaks your code and affects the service you provide to users. Style issues ain't that. Come on.
15.
by chipdart 2y ago
> (..) you really want those 2x 12 memory channels a Dual EPYC system offers (...) I had to check and I was amazed that there are companies selling workstations with dual EPYC processors, providing a whopping 256 CPU cores and over 2TB o
16.
by chipdart 2y ago
> Intel will have more cores shortly. The article was posted in 2023.
17.
by chipdart 2y ago
> It does but it also seems like AMD is saying just buy one CPU, which is weird because you’d think they would want you to buy two to double the profit. The are saying "buy a single EPYC instead of two of our competition".
18.
by chipdart 2y ago
This article reads like an AMD advertisement for their EPYC processor line.
19.
by chipdart 2y ago
> Aren't the drivers being hired for their recently announced Robo-Taxi fleet (...) The robo-taxi fleet is scheduled to be launched by 2026. This means Tesla, in spite of Elon Musk's wild claims, is not counting on providing an
20.
by chipdart 2y ago
> Well, the share is up 3% since that article was published. :shrug: , I guess ? I don't know where you get your stock quotes. The ones I get tell that last monday TSLA stock prices were at around $350 and right now they stand at $3
21.
by chipdart 2y ago
Requiring manual intervention to handle a blocked pipeline over a non-issue defeats the whole purpose of continuous integration, not to mention that you are suggesting adding twice the complexity as an alternative to not adding any complexi
22.
by chipdart 2y ago
> This is genius. This is a peak Elon Musk stan quote: playing catch-up to what is described in the article as the industry standard, and something that established players were doing over a decade ago, is... "Genius"? Is that
23.
by chipdart 2y ago
> Also, it seems like it's already done in other robotaxi setups. I think you're missing the whole point. The whole point is that Tesla has been promising full self-driving cars for years, and going as far as to talk shit about
24.
by chipdart 2y ago
> “duped” isn’t the right word here. "Duped" is an accurate description of how Elon Musk has been treating customers who bought a Tesla car with a HW3. He's been repeatedly promising those buyers that full self driving is
25.
by chipdart 2y ago
> Big pile of nothing. Not really. In the very least it proves that at best Tesla is way behind established robotaxi operations, and once again demonstrates that Elon Musk's recurrent promise that "full self driving cars is jus
26.
by chipdart 2y ago
> Linting and style guides are not of "critical importance". This is simply false, as attested by the huge volume of comments in this thread by those with actual professional experience working on real-world software projects.
27.
by chipdart 2y ago
> style fixes should always be separate commits. Not really. If you're already changing the code and running linters afterwards introduces changes over your change, this means you are the one introducing the problems. Separate commi
28.
by chipdart 2y ago
You can revert and even force-update the branch to rewrite it's history, but GitHub still tracks the old commits and even lists in the PR the events that rewrote the branch history.
29.
by chipdart 2y ago
> If you start telling people off at work, there is a good chance that you will be perceived as being the problem The whole concept of a PR is to review the changes you ask your team to pull into the repository. What do you think PR comm
30.
by chipdart 2y ago
> CI should reject the feature branch if the linter fails. Your CI pipeline is broken if it refuses to run because of style issues. Linting is either applied as a pre commit hook or manually by the developer. Anything else is a mistake y

More ›