You do that anyway as per Conway's law.
451 karma · joined February 5, 2021
Google might have very smart and knowledgeable people in it but this language is like a bad overhyped C. See next code that all it is doing is parsing a CSV line:
func NewPoint(line string) *Point {
tokens := strings.Split(line, ",")
if len(tokens) != 4 {
return nil
}
var err error
p := new(Point)
p.id_ride, err = strconv.Atoi(tokens[0])
if err != nil {
return nil
}
p.lat, err = strconv.ParseFloat(tokens[1], 32)
if err != nil {
return nil
}
p.ts, err = strconv.ParseInt(tokens[2], 10, 64)
if err != nil {
return nil
}
return p
most of the code has nothing to do with its functionality - it's just error handling that is plain hideous to write and read. Not to mention all the clutter to just convert an integer and a float.
And let's just not go into deeper aspects such as the structs that double as classes and has everyone creating his own style of SOLID and DPs. Or the inconsistent syntax which sometimes looks like traditional OO and othertimes like plain C further confusing users.
I find it very hard to believe that this language would have caught on if it weren't for Google pushing for it so aggressively. And I find it so disheartening to realise that after all these years developer productivity and happiness is merely an afterthought for language designers and that marketing and hype are the main drivers.
And yes I know the saying "there are languages people complain about and languages that people do not use". I find it worthy of high school gotcha sayings to which I reply that language designers of the majority of programming languages have no clue about how to make a language nice to its users. It's as they know how to design a internal combustion engine and then they put a chair and 4 wheels on it and they dismiss complaints about how unreasonably difficult and miserable the driver experience is.
Pragmatic as in these are not generic solutions/patterns but actual working architectures.
Thanks.
2 pages in FoundationDB paper (https://www.foundationdb.org/files/fdb-paper.pdf) I knew I was looking at one month's reading material if I really was to grasp everything. It'd be much easier if I worked with DBs and Distributed daily but I don't.
But, yes, I see your point.
It is becoming a regular thing, almost part of the news cycle. "In other news, yesterday was the biannual data leak from Linkedin".
It is outrageous.
That is impressive. Like a framework for implementing noSQL DBs.
Identity is even a dominant political trend in itself. "Identity politics".
I agree with the premise of the post. I just cannot see how it can be done. I think it's better to learn to accept differences gracefully rather than minimizing the identity surface. It's also my way to test people and communities. Try to disagree on something they consider basic. They way they'll treat you shows who they really are.
Which leads to a number of weird situations like maintainers begging for compensation from simple users while behemoths make tons of money out of their SW or pretty basic SW being undermaintained (I vaguely remember a case pertaining to a security related library a few years ago where everyone was waiting on an overwhelmed and unpaid maintainer to provide a security fix).
Dunno. Some things just don't make sense to me. FWIW as far as my projects go I license under GPL. If it's free for you let it be free for all. I'd hate to be in the shoes of Redis contributors. To me, if your work is being used you must be compensated. Anything else is just plain wrong.
That sounds ominous.
Why do they execute the generated tests though? I mean I'd expect this to go only as far as generating the tests. Also that means that at least someone needs to review the tests.
"Sometimes" is the key word here. And the one that I wouldn't know how to quantify.
I really don't think so. And I'm afraid that this is a classic race to the bottom for the most of us.
1. I compete for positions with people all over the world. Who can complete with a fraction of the salary I need.
2. As a remote worker -most often working as a contractor- I'm even easier to be replaced in a heartbeat. No severance or anything alike.
3. Did I mention that I compete with all the planet? That makes competition for good roles really crazy.
4. Work blends into life and it is very hard to keep it from. This gets worse depending on the company/role but in general these things tend to go the employers way not yours.
5. You need to find new ways to socialize (and the motivation to do so is minimal) or you risk mental health issues.
All I'm trying to say is be careful what you wish for because you might get it.
https://www.reddit.com/r/ExperiencedDevs/comments/nnw7yd/sob...
https://www.reddit.com/r/ExperiencedDevs/comments/noa841/sup...
I guess there will be more on their way.
I'd say we all subsidize bitcoin and the likes indirectly and unwillingly through the price hikes in HW directly or indirectly attributed to something of dubious (to put it mildly) tangible value.
Lost my brother-in-law few months back after a long battle with cancer. My sister is still mourning. It takes time and it never really goes away fully. You just get used to it I guess.
One of the things I thought and shared with her, and which had some effect was this: we all die and we all spend our time here in various ways. Being sad for a loss means that we were lucky enough to have someone of high value in our lives. That is not a given. So, sad as we might be it's also a reason to be happy that we were that lucky. The alternative would be to never have met them and thus lead a much poorer life.
Dunno if that helps.
I won't be surprised if all flies in/out to Belarus are suspended.
PS: Which also brings to mind the downed Malaysian flight when flying over Russian-friendly Ukraine. I hope that airlines also have these areas in their no-fly lists.