agbell

Yes, I got turned on to IronOre and StopLang from Casey in exactly this video. Great tech!

Thanks for reading!

Yeah, the future trick is kind of interesting because it solves the immediate problem and it allows people to feel like you heard their concerns and valued their advice. If that is what they are looking for then its a great solution. If they have spotted legit problems then you need to actually reassess things.

I guess like everything it is very contingent on the environment. It worked in this specific context.

Thanks - I'll fix that. There aren't too many Adam Gordon Bell's out there though.

Yeah, I think that could be true in general. Tetlock found the hedgehogs were more famous and more wrong and I got the idea from him that that was because simple advice is more sticky and works better in sounds bites but it could also work the opposite way -- ie. the more people ask you for advice the more you learn to tell them what they want which might be oversimplified. So you get trained to be more of a hedgehog over time. Interesting idea.

Thanks for reading it. It was one of the those ideas bouncing around in the back of my head for a while but hard to put into words then I read something about Tetlock and the dots sort of connected for me.

Software advice isn't totally a prediction, but it sort of is.

Author here, thanks for sharing this. Let me know what you think. I'm trying to connect the dots on research on expert advice and our fields 'thought-leaders'.

The connection is a bit tenuous but I think contingent advice can be shown to be better than non-contingent advice. I also think people are too confident in their opinions.

Also another submission here: https://news.ycombinator.com/item?id=27462255

Thanks! yeah, I got that. I was just considering in a comment the fact that I wish I had a better word for people with strongly held believes that their solution will solve all things.

Architecture astronaut is one Joel Spolsky used back in the day that I liked. Maybe solution peddlers? Thought-leaders works though and yeah I think for most people it is pretty cringe inducing.

Thanks for reading!

I actually wish I had a better term than thought-leader, because there are people who use that term non-ironically who do have contingent and useful advice. But yeah generally it't not a good sign if that is how you describe yourself.

Author here, thanks for sharing this. Let me know what you think.

I'm trying to connect the dots on research on expert advice and our fields 'thought-leaders'.

The connection is a bit tenuous but I think contingent advice can be shown to be better than non-contingent advice. I also think people are too confident in their opinions.

Thanks for sharing!

A question I had with APL was how do you actually type it in, and it turns out you just use a back-tick as a prefix, like a leader key in vim. Conor walked my through solving something with TryAPL in this video:

https://www.youtube.com/watch?v=lG-CcPb7ggU

The guest of this episode is working on porting J to modern C++. Someone also shared this javascript implementation of APL:

https://github.com/abrudz/ngn-apl#readme

Thanks for listening and thanks for encouragement. I really appreciate it.

That image manipulation example is really cool! Not knowing much of either J or APL, I do like how the non-ascii symbols can visually represent the operation in APL, but using ASCII does seem more practical.

I have heard a similar story or two and they all have involved google.

I'm not sure when these leetcode style interviews became pervasive but it makes sense that recruiters would figure out quickly where to find people that would excel at that interview process.

One reason for learning APL mentioned in the interview is learning to solve problems without branching.

Conor's knowledge of solving problems in a data parallel fashion using masks and such in APL helped him with his day job of building GPU accelerated data-science tools at NVidia.

But it's not just a NVidia thing - CPUs can do data parallel operations and also get slowed down by branching. I don't think this means that you should write everything in an array language, but it means that learning how to solve problems under those constraints will teach you important lessons.

Host here. I came into this knowing more about competitive coding than APL but I found both interesting. The way these ICPC teams compete as a group and train is fascinating to me but this connection between APL and GPU programming was really something cool that I was not aware of.

I love my job, and I love working from home. I have been doing it for years.

Working on a fully remote team is not the same as working on fully co-located team. Some will say it's worse but for me its better. One thing is for certain - it is different. Some things are easier and some things are harder. It's just a different point in the design space of possible ways to work.

So I've had the reverse issue. With hardware encoding on and external monitors plugged into my intel macbook, everything would overheat and I would get kernel throttling of everything.

The external monitors cause the GPU to draw more power, but I'm not sure why that combined with hardware encoding in OBS caused issues. When I switched to software encoding the cpu was a bit higher but everything was fine.

Apparently this is related to VRM overheating and people have workarounds posted on reddit, but it seem like switching to software encoding made it go away for me.

https://www.reddit.com/r/macbookpro/comments/gs6bal/2019_mbp...

https://support.apple.com/en-ca/HT207359

That seems unfair. Even after warm-up time Jruby and truffleruby are still slower and the truffleRuby folks are investigating it.

I thought looking into why something was slow was worth writing down as a blog post.

https://github.com/agbell/jekyll-perf

Author here, thanks for sharing. I was confused about why JRuby was slow in the Jekyll CI and also in my own Jekyll blog when compared to just standard Ruby. This post is my investigation and I've gotten a couple pointers since on reddit as well.

It seems like this is somewhat in that direction. It looks like it is using merkle trees to store the history.

If I can plug my own podcast then CoRecursive. I try to find people with interesting experiences building software and turn them into an episode.

Signal Vs Noise is also great and Arraycast is brand new but great so far.

http://corecursive.com/

http://arraycast.com/

https://signalsandthreads.com/

Yeah, refined types are a great solution to this problem, but can lead to slow compile times. Just having private constructor for a case class and a public apply method that is an Option or Either or something can go a long way in my experience.

In some areas it is explicitly the opposite that happened, and in a way that is for the best — see implicits.

Scala 2 is a very flexible language and a lot of outsider complaints seem grounded in this flexibility.

Scala 3 is more opinionated in some ways:

"Opinionated: Contextual Abstractions

One underlying core concept of Scala was (and still is to some degree) to provide users with a small set of powerful features that can be combined to great (and sometimes even unforeseen) expressivity. For example, the feature of implicits has been used to model contextual abstraction, to express type-level computation, model type-classes, perform implicit coercions, encode extension methods, and many more. Learning from these use cases, Scala 3 takes a slightly different approach and focuses on intent rather than mechanism. Instead of offering one very powerful feature, Scala 3 offers multiple tailored language features, allowing programmers to directly express their intent

"

I think it is a very practical and grounded focus change.

https://docs.scala-lang.org/scala3/new-in-scala3.html

That is my understanding of what they did.

"Scala 3 takes a slightly different approach [from Scala 2] and focuses on intent rather than mechanism. Instead of offering one very powerful feature, Scala 3 offers multiple tailored language features, allowing programmers to directly express their intent"

So rather than something like implicits, that can be used N different ways, only 2 of which are practical, Scala 3 adds those 2 features explicitly.

Rumor has it Kotlin was inspired by frustrations getting Scala edge cases to work in IntelliJ.

I totally agree. I love the direction of Scala 3. This quote says it all I think:

"Scala 3 takes a slightly different approach [from Scala 2] and focuses on intent rather than mechanism. Instead of offering one very powerful feature, Scala 3 offers multiple tailored language features, allowing programmers to directly express their intent"

So rather than something like implicits, that can be used N different ways, only 2 of which are practical, Scala 3 adds those 2 features explicitly.

https://docs.scala-lang.org/scala3/new-in-scala3.html

Arrival: The short story its based on it amazing and explains things not just using linguistics but also physics. I love the movie, but it's sadly not as good, especially how it ends.

My coworker wrote this tutorial for using JSDos and docker and old dos shareware games together.

I had never heard of JSDos before but it seems to work very well. Its crazy what you can run in javascript today.

He is planning to do a VNC version at some point as well since the mouse doesn't always line up with JSDos.

Maybe this isn't super practical but for me it was cool to have a one-liner around I can use to play Commander Keen or Scorched Earth.

Reply All is great, though I think it is embroiled in some controversy right now.

Corecursive is my podcast about the stories behind software development. I think hn readers would like it.