Live data from Hacker News

Signaling in tech is some fucked up shit (2016)

daiyi.co

181–190 of 205 posts

Re: Signaling in tech is some fucked up shit (2016)

#181
post #21

Earlier quoted context omitted.

“Look at how many plates I can juggle at once!” “Aren’t you just trying to walk to the store?” “Look! I added a fifth! Everyone do this now!”

Isn’t using Java, PyTorch, Elasticsearch, and neural networks for a TODO iOS app the same?

This made me burst in laughter. I am indeed using Java and Elasticsearch, and no PyTorch, but Spark for an app I am working on. Way more complex than it should be.

Re: Signaling in tech is some fucked up shit (2016)

#183

Coming from embedded, the web is such an awful platform. No versioning. Polyfills everywhere! XML (satan's markup). Javascript... Every line of code is a rabbit trail into "can I use" BS. Web devs didn't make it that way. They're just the ones who have to live with it. We should be buying them lunch and thanking them for their service, not crapping on them.

Embedded has plenty of its own ugliness, though. It just doesn't change at such a rapid clip. In fact, once you ship a thing, it's unlikely to change at all. I appreciate this "do once and forget about it" approach, but at the same time the tooling for embedded can be ugly AF as well.

Depends on your chipset. Last project I worked on was for the Z80 (only a few months ago, strangely). Like buttah.

Re: Signaling in tech is some fucked up shit (2016)

#185
post #3

> when I told other software people I’m a web developer, I got treated like shit. I was a lower class of coder because I wasn’t “solving cool problems” because making web sites is easy. Of all the stupid arrogant awfulness in tech that has crossed my path this one is definitely high on the list of the most baffling. Web dev is the hardest and most intimidating dev work I've ever done, by a country mile. (Whether that…

What other work have you done though? From my experience, it seems like a lot of web dev people struggle with OS/Compilers/Embedded/Robotics work, but people who don't struggle with OS/Compilers/Embedded/Robotics work tend to handle web dev just fine. Why is that? The only explanation I can think of is because the work is easier ( easier, not trivial ). (Note: I don't think a web developer (or anyone) should be consi…

i think the real reason for this is related to the availability of easy-to-use and up to date learning materials, more than anything else

Those people who are good at OS/Compilers etc would still need to use a tutorial to pick up HTML/CSS/JS...and due to the popularity and inclusiveness of the web dev community, they will find it relatively easy to find high quality interactive tutorials that can get them up and running quite quickly. Additionally a lot of the web is designed to be easy to use...its the reason why we're all using HTML5 and not XHTML right now. I think of the current competition between Vue, React, Angular and others to basically be an ease-of-use competition. Its genuinely quite cool that web developers are making fairly tricky concepts easy to use with these libraries.

On the other hand, a lot of material about OSes, compilers, embedded systems is relatively obscure, frequently out of date, possibly difficult to find outside textbooks and research papers, and open source libraries in these domains might even require looking through source code just to figure out how to use a library. A lot of these communities are also indirectly elitist, leading to various sorts of bootstrapping problems for newcomers (I've heard "if you can't build the Linux kernel, why are you even trying to learn about it" several times on different mailing lists :/)

As a personal anecdote, I work on compiler and OS things as part of my job, and most people on my team have a high degree of respect towards web dev work. There are only 2 people on my team who think that we could easily do some light web dev: me and another colleague, both of us who've done actual web dev jobs for several years before transferring to our current team. So I don't think web dev is easier, but just far more accessible than a lot of other fields.

Re: Signaling in tech is some fucked up shit (2016)

#186
post #180

Earlier quoted context omitted.

The inflated sense of ego associated with “saving the world” and “solving tough problems” has almost completely turned me off from tech, in the Bay Area in particular. My problem isn’t with the sentiment—it’s that 99 out of 100 times it’s pure bullshit. There are a few people out their doing really amazing things, but the vast majority of people who have big egos aren’t the people working on that stuff. Tech is the n…

One doesn't need to save the world. But not making it worse through ads and ubiquitous tracking would be nice. So is not pushing negative externalities inherent to web apps to customers just because it makes web devs more productive. Today's web is a monster.

> So is not pushing negative externalities [...] to customers

Same could be said of bailouts, recycling, MLM, and other sucker games...

Re: Signaling in tech is some fucked up shit (2016)

#187

Earlier quoted context omitted.

When I see an interviewee list out a bunch of things they have "experience" with like that, I assume they actually mean "I used this once".

It's hard to avoid touching the DOM, HTTP, NPM, React, NGINX, Docker, etc. on a daily basis if you're doing any kind of serious work; it's not just some disjoint list of obscure buzzwords.

Yes, compare and contrast the above to my own partial list of technologies from 1977 to 1997...

“Nova 1220 BASIC, Acius 4th Dimension, Hypercard, MetroWerks CodeWarrior, Lightspeed C, Turbo Pascal, MP/M, DigiTalk Smalltalk/V, J2EE, ...”

What does any of that have to do with each other.

Re: Signaling in tech is some fucked up shit (2016)

#188

Earlier quoted context omitted.

In english, "statistically speaking" can mean you are making a claim about the odds of something rather than a 1:1 correspondence. It is extremely common and absolutely correct. For example I have not run a study but I am very confident that, statistically speaking, tall people are better at basketball than short people. I am saying that I have an opinion that if you were to try and choose good basketball players, bi…

If you believe this is about pedantry and the literal meaning of words, you’ve missed my point. However, you’re speaking to it: the commenter used the phrase “statistically speaking” to indicate their confidence in their assertion. I’m taking issue with the fact that they used the phrase - which, as you say, is strong enough to describe the way taller people are better at basketball - to generalize that Clojure devel…

It doesn't imply great confidence, it is literally saying a different thing. You seem to think it means the same thing as "scientifically speaking" or "I have evidence that". It very often means only "related to statistics". That's it. No epistemological claims needed.

"I'm so going to win the lottery"

"On average ... no you aren't" / "Statistically speaking ... no you aren't" / "If you work out the odds ... no you aren't" / etc.

If I ask you a question about some gambling game, you are going to think about it in a statistical way. I mean you will think in terms of populations and samples and odds, not that you will go perform experiments and then do a statistical analysis of that evidence in order to come to a scientific conclusion.

Re: Signaling in tech is some fucked up shit (2016)

#189

Earlier quoted context omitted.

It's hard to avoid touching the DOM, HTTP, NPM, React, NGINX, Docker, etc. on a daily basis if you're doing any kind of serious work; it's not just some disjoint list of obscure buzzwords.

Yes, compare and contrast the above to my own partial list of technologies from 1977 to 1997... “Nova 1220 BASIC, Acius 4th Dimension, Hypercard, MetroWerks CodeWarrior, Lightspeed C, Turbo Pascal, MP/M, DigiTalk Smalltalk/V, J2EE, ...” What does any of that have to do with each other.

There's one thing: Hypercard and DigiTalk represent directions personal computing should have gone, but didn't (although that's not relevant to the thread topic)

Re: Signaling in tech is some fucked up shit (2016)

#190
I dunno, to me the whole 'abc coders are xyz' is a heuristic. I value curiosity and I find that devs that are solid at a wide variety of paradigms often get there through curiosity. So if someone tells me they are learning Clojure/Haskell/Scheme/Racket/OCaml/Brnfuck/Scala/Smalltalk/etc I'll think that's interesting and wonder what made them decide to learn the language. Without further information it's a safe guess that they are curious and enjoy learning new things/challenging themselves, things that I think are cool to do. And people who do cool things are often times cool people.

But Daiyi's main point isn't that abc coders aren't xyz, but rather that other people are also xyz, and that if an efg coder becomes an abc coder and are found to be xyz then they were probably xyz back when they were efg before becoming abc coders.

And this point should be well taken. There is a common trend that analytic subjects contribute more value than artistic subjects. This, in part, is due to the phenomenon that analytic subjects have values that are easier to calculate (...analytically, whence this is somewhat circular) while artistic subjects have effects that must be evaluated more subjectively. A coder works for a week and adds a new feature which increases marketability. A painter works for a week and produces a painting that may eventually sell for $500 in a couple years. But this undervalues the painter---the effect of arts on a society is more than their retail value.

I think this in part describes why web devs/front end engineers are socially valued less than coders in the development community. Their contributions are harder to quantify and the problems that they solve are more diffuse and subjective. This leads to "it's hard to quantify an efg coder's contribution" being conflated with "efg coders contribute less".

But this is BS---I have yet to come across anything that isn't both an art and a science if done correctly. In fact, this thought lead me to my own answer to one of the great philosophical questions of the ages: "what is art?": I contend that art is anything done well.

And as a computer scientist with a prior life as a musician I can assure you that there is plenty of 'calculation' that goes into the arts. Sometimes this is explicit. For instance, say that I have a closed voicing CFA (closed voicing means everything is close together) and they are moving to B?G that will then move to CEG. What do I want to replace `?` with? Well we don't want F to move down (we try to avoid parallel motion, this can be thought of as a sort of axiom) so F must either remain fixed (oblique motion) or go up (contrary motion). We also don't want voices to cross (while voice crossing is less taboo than parallel motion it is still often avoided, and our adherence to this restriction makes our problem much easier). Since we are working with a closed voice we have two (diatonic) choices: we can double the G or stay fixed on F. Doubling the G is boring but staying on F creates dissonance (B to F is a b5 and F to G is a M2). Luckily this dissonance is nicely resolved by the subsequent voicing and we win music! Yay!

Notice something? This is just a constraint system! But rather than solving a SAT formula we are adding in some subjective data to consider as well. I like to phrase this as "In math, `1 + 2 + 3 = 6` while in music, `C + E + G = happy`".

These calculations can also be done implicitly: say I'm taking a break over some jazz tune and I'm hitting a turn around, a ii-V7-i. I have a vague notion that I want to hit the "Billie Holiday special" (https://youtu.be/KUCyjDOlnPU?t=2m59s) at the end of my break (a melodic 5-2-1 with a slight scoop up to the 2 which falls back to the 1). I'm in the key of Bb and I want to play this around the tonic at the 8th fret of my D string. Right now I'm in the upper area of the neck and about to change to the ii chord which holds for two beats. I want to leave a pause over the V chord to make the tag more interesting, so I have exactly two beats to get from where I am to where I want to go, and I have to quickly 'calculate' this transition in real time. This is, of course, very natural since I've been playing for most of my life, and the 'calculation' is more of a feeling than an explicit mental exercise. But underneath the hood there is a shitload of precomputation that I did, practicing similar harmonic and melodic situations, honing my instincts, expanding my ear, studying theory, etc. I have just, in real time, solved a complicated constraint problem in front of a room full of people. And they are all cheering for me! See? People love math!

I'm sure I don't have to argue the reverse direction on this site (namely that coding/engineering/mathematics/etc are all forms of art) so I'll omit this.

All this is to say that the distinction between the artists and scientists is very blurry. I won't go so far as to argue that it doesn't exist since it clearly does. But when I try to figure out what that distinction is I find a number of qualitative differences but nothing quantitative.

Post reply on HN