srer

6 ms·

1.
by srer 4y ago
> But fundamentally no one should ever be trying to merge code that hasn’t been unit tested. If they are, that is a huge problem because it shows arrogance, ignorance, willingness to kick-the-can-down-the-road, etc. Here you are assertin
2.
by srer 4y ago
Consider it is not an unheard of experience to join the workforce, use a preconfigured macbook with precisely 1 SSD, and spend one's career building on SaaS platforms like AWS Lambda. In such a world, perhaps those who remember there&#
3.
by srer 4y ago
> The language has memory-safe concurrency (except for maps, which is weird)... My understanding is you should operate the other way around. Things aren't safe for concurrent mutation unless it's explicitly documented as safe.
4.
by srer 4y ago
I work somewhere going through a similar process for much the same reason. And to be frank, I'm wondering if how it ends is in me looking for a new job. I know there's good reasons for the business to go through this process, and
5.
by srer 4y ago
10 hours isn't too bad when dealing with a giant organization. Often problems cut across teams and services, and troubleshooting then liaising and ultimately getting a remediation action through (which might involve producing, testing
6.
by srer 4y ago
I do the opposite. Across C, Python and Go, I was prepared and had a good understanding of the languages and stdlibs before joining through reading books and working through the exercises. It worked very well for me, on joining my knowledge
7.
by srer 4y ago
A single server is much faster than most people think, too! In the microservice or serverless arrangements I've seen, data is scattered across the cloud. It's common for the dominant factor in performance to be data locality, most
8.
by srer 4y ago
Leetcode is programming. It's not sprint planning, 1 on 1s, backlog grooming, jira tickets, slack support, gathering requirements, making estimates, negotiating features with management, responding to alerts, or the million other th
9.
by srer 4y ago
As a general rule for dev work, trying to make evidence based decisions is fairly difficult. There's just not that much evidence around yet that can make it obvious as to if in your particular situation what the best choice might be. A
10.
by srer 4y ago
I largely agree with you, that rather than introducing Rust into your workplace it's easier to change workplaces. I currently work in a Go shop. Why Go? Did it win some business value delivering contest? I don't think so, it'
11.
by srer 4y ago
Lets see what the Go doc example looks like: sort.Slice(people, func(i, j int) bool { return people[i].Name < people[j].Name }) In Python one might write: people.sort(key=lambda person: person.name) Or in Rust: people.s
12.
by srer 4y ago
Pretty simple for me: I like working with Free and Open software much more than proprietary software. I think it's important for society, and I have more fun that way too! Also the payoff for me has been very good, I can learn emacs on
13.
by srer 4y ago
Reminds me of discussions I had in the early 00's! People would say "Linux is cool and I'd like to try it, but Windows is where all the jobs are" . It's a fine point, and quite reasonable. It is however I think imp
14.
by srer 4y ago
There are significant pockets of non-git users in the developer community ;) I find hg much more pleasant to use than git, and can generally still work in git based teams while using hg. I find pijul's approach much more interesting th
15.
by srer 4y ago
Largely complaints of Rust seem to boil down to the programmer needing to describe object lifetime information in code. We can, as the original post did, show approaches that are overwhelmingly difficult in Rust because of this but trivial
16.
by srer 4y ago
Increasing we automate processes, have programs do the work humans once did. It's extremely helpful and productive, but it has a darker side. The processes are rigid because machines are rigid, and the designers cater to the 99% cases.
17.
by srer 4y ago
I work in a company that's all in with serverless on AWS, but unlike you I can't give a glowing recommendation. The answer should always be "it depends". IMHO the more distributed a system the more difficult it is to cor
18.
by srer 4y ago
I find interviewing skills are more important than job skills in terms of income. Trying to get a 20% raise by doing a good job I've found to be a protracted difficult task, but a 50% raise by interviewing? Much easier. You do need som
19.
by srer 4y ago
I do that, create the ticket. I want to believe it means one day we will do that TODO, it'll beat the priority of all the other tickets in the queue. But it never does, there's always some critical new feature sales wants, or some
20.
by srer 4y ago
https://research.swtch.com/gorace describes a loss of memory safety through data races, but I note it says "In the current Go implementations" and was written in 2010. I never heard of news that the situation had
21.
by srer 4y ago
Wanting SQLite in Go touches on something that I think is quite a waste in modern Go circles, but happens everywhere to varying degrees. There's often (for instance, in Go projects wanting to avoid cgo) a desire for everything to be in
22.
by srer 4y ago
Is it memory safe? As I understood it you lose that as soon as you start using the namesake keyword, "go".
23.
by srer 4y ago
I'm going to mention my own tiny experience report as a frequent SQL user, of Go's simplicity pushing a lot of burden onto the user in the relatively simple task of querying a list of things from a SQL table: http://go-
24.
by srer 4y ago
> your greater system model has to assume it can die at any instant for any reason Correct. This is something I have to design for in the system anyway, because in practice anything can (and does!) die at unpredictable times. It's t
25.
by srer 4y ago
IRC's influx of new users has been dropping off for a long time. Personally I started using IRC 20 years ago, there were a lot of new users then. The big IRCnets were massive[a] compared to today[b]. Today libera.chat is the biggest, b
26.
by srer 4y ago
Much like you I look forward to (mostly CPU) increases to get better arma3 performance! We need all the performance we can get, because even if it was the worlds most optimized engine, we'd just create bigger scenarios. Who wouldn&#x27
27.
by srer 4y ago
I'm not sure what you mean by manually manage. I don't manually manage my memory anymore in Rust than I do in garbage collected languages (say Python or Go). (I do have to think about object lifetimes and whats pointing where in a
28.
by srer 4y ago
Software updates is one reason For simpler userspace updates a restart of the relevant processes is easy enough, but it can be a bit more difficult when it comes to kernel updates. (Updating a running kernel has been a thing in Linux for a
29.
by srer 4y ago
Programming is a vast field, "essentially never" is quite a strong statement. For many errors, in many situations, terminating the process is quite reasonable. In my particular situation, the greater system will restart failed pro
30.
by srer 4y ago
IMHO: Rust integrates a bit better with existing software. Inclusion of Rust in Linux being an example. Go culture tends to value pure Go projects a bit more than Rust's, where Rust wrappers around C libs are more accepted and common.

More ›