Pretty good stuff overall. Enums have a lot of caveats but they feel like a much needed addition.
KIROKAZE

titsay

Origami Around
Peter Solarz
Game of Thrones Daily
d e v o n

oozey mess
PUT YOUR BEARD IN MY MOUTH
art blog(derogatory)
trying on a metaphor
TVSTRANGERTHINGS
Claire Keane

ellievsbear
Lint Roller? I Barely Know Her
AnasAbdin
NASA

Discoholic 🪩
h
No title available
i don't do bad sauce passes

seen from United States

seen from United States
seen from Sweden
seen from United States

seen from Canada
seen from United States
seen from United States
seen from United States
seen from New Zealand

seen from United States
seen from Italy
seen from United States

seen from United States

seen from United Kingdom
seen from Netherlands
seen from Germany
seen from United States

seen from Finland
seen from Netherlands
seen from T1
@mheroin-dev
Pretty good stuff overall. Enums have a lot of caveats but they feel like a much needed addition.
There’s a bunch of different ways you can implement the process of finding and reclaiming all of the unused objects, but the simplest and first algorithm ever invented for it is called “mark-sweep”. It was invented by John McCarthy, the man who invented Lisp and beards, so you implementing it now is like communing with one of the Elder Gods, but hopefully not in some Lovecraftian way that ends with you having your mind and retinas blasted clean.
Heresy. Heresy that works.
Carmack, like Abrash, is a legend in programming circles, and for good reason. The stories in this book about him are, frankly, a little scary. His devotion to the machine borders on fanatical; he regularly worked 80 hour weeks and he'd take "vacations" where it was just him and a computer alone in a hotel room for a whole week – just for fun, to relax.
You Don't Need Millions of Dollars
Practicing Ruby is a great source of information for Ruby developers. This specific article's one of the best dev posts I've seen in months.
Notes and more details on the talk here.
Rich Hickey (the creator of Clojure) is consistent in delivering fantastic, thought-provoking talks. Personally, I consider the following required viewing for most, if not all programmers. If you’re not particularly interested in Clojure, I’d suggest watching these videos in reverse order.
I’m probably the dumbest guy in the lineup of amazing speakers. Say “hi” if you’re around.
I will be talking about how usually mainstream languages are terrible. I think we can change that with Javascript and I'll be exploring some of the flaws I see in the system, possible improvements and maybe a couple of bad jokes in between.
This is how you do a personal website.
gcc -O4 emails your code to Jeff Dean for a rewrite.
When Jeff Dean fires up the profiler, loops unroll themselves in fear.
When he heard that Jeff Dean's autobiography would be exclusive to the platform, Richard Stallman bought a Kindle.
Dash is an amazing tool for developers and it's currently on sale on the Mac App Store for $7.99. You can download it for free and try it first, but trust me, you need this.
Learning New Programming Languages
These are some of the things that help me when I'm learning a new programming language. I hope they're helpful for you too:
High level overview
Mostly Wikipedia. The questions I'm usually asking are: what's the type system like? Do I need to compile stuff? What's the paradigm? What are the key language features?
I want to get a rough understanding of what I'm getting into and what's it good for.
Start with a book
I've tried reading blogs, watching screencasts and trying to "wing it", but the best way I've found to get started is to get a book and read the first 5-6 chapters. I don't spend too much time reading each page unless I'm dealing with new concepts. Instead, what I'm doing is finding the basic tool set that allows me to write minimal programs. I look for stuff that I already understand (how do conditionals work? How do I create a string? Do we have a regex library?) and then I try to re-create something easy like a permalink function. The idea is to get me doing "productive" work as soon as possible.
Go for the juice
If there are interesting, language-specific features (e.g. Lisp macros, goroutines, monads) then I want to learn about them rather quickly. I might not understand what I'm doing at the first but acquiring new knowledge motivates me to dive deeper. All interesting languages have "their" thing, so try to find those and exploit them as soon as you can.
Create a file per useful construct
My memory sucks and searching through books (physical or digital) sucks even more. For every new language I'll create a folder where I have one file for each useful construct. Here's an example of an array.go file I used when learning Go. I use source code files because they're "greppable", executable and by separating them it's easier to use them as reference. I add comments for concepts that I find important.
Read other people's code
There's a huge gap between "I can write a permalink function" and "I can write production code in this language". You can either fill that gap by writing lots of code, or you can go and see how someone else has solved problems you're already familiar with. Instead of writing hundreds of crappy LoC, I can take a look at something like web.go and learn the idioms that experienced programmers use. I already have a decent understanding of web frameworks, but if I'm not getting something I'll usually play inside a REPL, go back to the book or jump into an IRC channel to get some guidance. Most communities are helpful to new users so don't be afraid to ask simple questions (but do your own research first!).
Write something useful
Everyone will tell you that this is the most important thing when learning a new language. Listen to them.
When I start to feel proficient I'll create something that's useful for me, something I want to be using right now. When I was learning Emacs Lisp I decided to write a Tumblr mode so I could post updates from my text editor. The code wasn't pretty (or idiomatic), but at the time I was using it almost daily so I had a motivation to keep learning more about the language in order to make my software better.
(Don't know what to build? Give me a hand, I have a list of smallish projects and not enough time to implement them. One of might them be interesting to you).
Lastly
Don't criticize as a noob. Languages (at least the good ones) are not optimized for newbies. Don't go complaining about how hard it is to accomplish X in Y language when you've only been using it for two weeks. To stay with the Go examples: the guys behind it are pretty fucking smart people, if they decided string interpolation should be done by calling some variation of Sprintf they most likely had a reason for this (which I still don't understand, but I'm a noob).
Approach the language humbly and you'll have an easier time, trust me.
Emacs + Dictionary.app
Find the current word’s meaning in Emacs (OS X only). Bound to C-c C-d:
(defun word-definition() (interactive) (shell-command-to-string (concat "open dict:///" (current-word)))) (global-set-key "\C-c\C-d" 'word-definition)
Small minds try to form religions, the great ones just want better routes up the mountain. Where Newton said he saw further by standing on the shoulders of giants, computer scientists all too often stand on each other's toes.
...Everything we can describe can be represented by the recursive composition of a single kind of behavioral building block that hides its combination of state and process inside itself and can be dealt with only through the exchange of messages.