li4ick

I blocked most of Reddit (also, deleted my account) when I say this: https://www.youtube.com/watch?v=uSVqoW1rz6w&t=850

because reddit programmers are so bad they couldn't just add an _if_ statement, or a limit?

Then you haven't heard of Stalin Sort

Add that to your aaS bullshit filter.

I mean, it's time to accept that JS is everywhere. Or, you can do something like Stallman, and have a remote machine send screenshots to you, so you don't have to run non-free JS.

We occasionally spend 20 min on Tuesday and Thursday, at around 14:00. That's enough for us. But then again, we're in a very unusual position as a team.

There's a reason people have their ideas in the shower. That's the last place on earth that is still not invaded by the smartphone. And that's why showers > baths.

Oh, he's improved over the years. You should watch his very first presentations, during the Quake era. I think he's taken some speaking lessons to diminish his "uhms". But yeah, he's fearless of the public, which removes his mental blocks. I used to stutter in front of the public, but the one thing that solved it for me was a course, where we had to improvise in front of a camera. At the end, the coach replayed every video back to us. Every participant felt so much cringe that it ironically solved the issue.

I mean, I believe that there should be a Hippocratic Oath in software, but I'm not sure where your particular cutoff bar stands. My view of software is against the mainstream: most programmers should dedicate their time to build tools for scientists, to solve actual problems and advance our species. Current tech is mostly trash, useless and nobody needs it.

Thought the same. He probably saw those JOIN vs Queue vs Hybrid designs and thought that he understood the entire system. Probably never even touched a system of that scale.

>xenophobia

I know at least 3 genius-level people from Europe that refuse to go to the US, because they are white, and every single moment they see these "whitey are racist by just being white" they simply descend even more into their beliefs. Also, their humour would get them fired within a minute in the USA.

Now imagine if the people working on the lower level stuff had the same attitude. Imagine if the codec implementations were slow because we need more features. Imagine if the graphics people never gave a damn about perf, just like the "programmers" you're talking about. Imagine if your database was the main perf hog in your system etc. etc. I'm sorry, but here's an unpopular opinion: those people are just not good engineers. The increments of software development should be abstractions, not features.

Which should tell you something. The vast majority of tech advancements are because of hardware, not software. I think that software people should feel a bit of shame at this point in time.

I use Haskell because it actually delivers on the promise of software reusability. In his book, John Ousterhout wrote a wonderful phrase: "increments of software development should be abstractions, not features.". I completely agree.

Even though the JVM ecosystem is great, I dislike the languages that run on it, Clojure being an exception. To filter out OOP, it fundamentally abstracts the wrong thing. Modules should abstract functionality, not data. And that's why I don't want anything to do with Java.

I'm starting to think that every thread about FP is pretty much identical on HN, especially when Haskell is involved. If you still need a ton of push to try it out, you'll never get it. If decades upon decades of provably superior concepts haven't convinced you, just give up. Just go and get hyped when the next minor FP feature gets integrated into your favourite language, something that's been used in Haskell/Erlang/etc. for 20+ years.

Makes sense. If they're really serious about Siri they need a high-quality search engine.

I mean...why not just go full OCaml at this point?

I wonder about the future of Stackexchange, now that every community has it's own subreddit/discort/etc.

There's one thing I want to scream at every front-end developer out there: STOP OPENING POPUPS WHEN I'M SELECTING TEXT!

Again: STOP OPENING POPUPS WHEN I'M SELECTING TEXT!

Care to elaborate?

Whoever at Google is responsible for this, I suggest they read this: http://worrydream.com/MagicInk

I guess they forgot what "information software" means. I use Firefox, but this is just bad design.

Greg Kroah-Hartman told me it's 40 times slower than Linux, at least that's what he told me 1 year ago. Wonder how that's changed...

If you like this kind of behind the scenes, i highly recommend Ken Kocienda's book "Creative Selection" about the development of some parts of the first iPhone.

Cont:

4. I'm not stagnating whatsoever, but it's getting harder and harder to ignore these issues. It's getting harder and harder to just think about my wellbeing and my project, and simply ignore the bigger picture. That is, the company tries to keep their employees at a certain average level. Don't get too good though, as they won't be able to pay you for that. So really good people just leave.

So, what would you do in my situation. I can tell you that i'm going to stay for a little longer to make sure that the project is rock solid and stable. But I feel like the really good engineers are somewhere else and the temptation of a higher pay is getting stronger. I really want to continue to work on this project, but how do I convince the manager(whose only real management was to give me a hard deadline) that I've done the equivalent work of a few people, and the current benefits are not enough.

Thank you.

Dataset assembled in China

Probably iPhone 7/8 by the looks of it.

The biggest lie about Haskell is that it's easy to learn. No it's not, and I do use it at work. Sure, it's not THAT difficult to get a basic understanding until you get to the usual Functor, Applicative, Monad stuff, which you can understand if you imagine them as context bubbles. Once you put something into a side-effect bubble (IO), you cannot take it out, so you're obligated to work inside of that bubble. This analogy should get you far enough. You're now ready to build toy projects.

But, even if you finish the Haskell Book(http://haskellbook.com), which is like 1300 pages, you're still going to be unable to contribute to a serious code base. Anyone who says otherwise is lying. Now, you have to understand at least 20 language extensions which you find randomly at the top of files {-# LANGUAGE ExtensionHere #-}. Now you have to understand how to really structure a program as either a stack of monad transformers, or free monads or anything else. Then you get into concurrency and to do that you have to understand how Haskell actually works, what non-strict computation does etc. etc. Otherwise you're going to get some nasty behaviour.

You think I'm done? Let's get to Lens. You can use Lens after a relatively short time of reading the docs. But to understand Lens? Very few people actually understand Lens.

Don't get me wrong, Haskell has spoiled me, and I don't really want to touch any other language (I still like Clojure, Rust, Python, Erlang). Once you get past that the language is a joy to use.

Ok. What's going on here? There's just no way this is real.

This [1] is one of the best in current research. It tries to actually follow the road. So it naturally builds the road map.

[1] https://www.csail.mit.edu/news/mitqcri-system-uses-machine-l...

Visualization is a small part, yes. I'd like to control the building. An employee can enter a room and the system would do stuff. I can say that "it's kinda dark here" and the system would either open the blinds or switch on the light. Depending on a lot of parameters. The thing is, the BIM doesn't have the interior elements such as desks and printers, just the layout of the floors. That's why my current hack is to have a color coded floor plan which generates everything. The graph is always changing throughout the day, and there are a lot of ML algorithms running in the background, including graph classification. That's why I'm trying to represent everything as a graph.