Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jrumbut
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
135 ms
·
1621.
▲
by
jrumbut
11y ago
I agree with you that that is a necessary part of the process and a great first step for small teams moving away from "just release it and see if it works". The unfortunate reality though is that people in the same role on the sam
1622.
▲
by
jrumbut
11y ago
Generally when I'm using a new framework, I like to scan the code to pick up on style, undocumented features, etc. Sometimes this results in a few typo-level pull requests. I never though of this as being resume line item grubbing beha
1623.
▲
by
jrumbut
11y ago
Even as someone who prefers a functional style, that quote is pretty unfortunate. Any Turing complete language is going to be able to express the same ideas (with varying degrees of gracefulness, resource usage, ease of debugging, etc).
1624.
▲
by
jrumbut
11y ago
I'm so happy to learn the term kebab-case (and agree that it's very usable and supremely typable)
1625.
▲
by
jrumbut
11y ago
Especially for the kind of glue scripts we're talking about, having to install new language packages across a heterogeneous environment consisting of thousands of boxes is not an easy option. For me the greatest advantage of the Perl5&
1626.
▲
by
jrumbut
11y ago
I think the energy spent supporting Python 2 and the inability to really unify and focus the community on Python 3 is preventing or delaying that kind of dramatic improvement. If people would rather move to another ecosystem rather than upd
1627.
▲
by
jrumbut
11y ago
It's not necessarily about breaking or maintaining backward compatibility that matters here. It's about how supporting two similar looking yet ultimately incompatible versions creates confusion for new users, driving them away. Th
1628.
▲
by
jrumbut
11y ago
Am I alone in finding SQL/normalized relational databases to be easier to learn? In the relational world, you can get a lot of insight into what will and won't work with simple math. There certainly are surprises in every database
1629.
▲
by
jrumbut
11y ago
Joining the various social networks, LinkedIn, Github, Twitter, HackerNews, etc is the place to start. Having your own website might be a decent idea too. If you post even the smallest of code samples you'be shown an employer two thing
1630.
▲
by
jrumbut
11y ago
It does appear, if the citation of IPUMS at the bottom (a cool source of data, for those who haven't seen it: https://usa.ipums.org/usa/ ) means anything, that they are at least using standard classifications. Tha
1631.
▲
by
jrumbut
11y ago
Whenever you aggregate data, particularly about human behaviors, the grouping is always going to be somewhat arbitrary. An underlying assumption, which we can make because the consequences of being wrong are so low (god forbid we be enterta
1632.
▲
by
jrumbut
11y ago
PHP and other languages have a . vs + distinction. I would say that the one area where you're right, and you are so very right, is context. Have %/@/$ cause such chaotic (and not terribly consistent, at least outside the core
1633.
▲
by
jrumbut
11y ago
We have some understanding of how an image becomes a viral hit, the mix of intrinsic properties and random chance. I would really like to know more about how individuals end up falling in love with other works, like in the first paragraph w
1634.
▲
by
jrumbut
11y ago
I guess Slothrop's prediction rate wasn't so unlikely given the density of those impacts :)
1635.
▲
by
jrumbut
13y ago
Sorry if this is off topic, but I remember having this exact issue when I was learning Ruby, maybe I can provide some clarity. For raw access to your MySQL database, the gem 'mysql2' is preferred (github with a simple tutorial: h
1636.
▲
by
jrumbut
14y ago
You might also enjoy Philip K Dick. His style is very different than Snow Crash, but I feel like their visions of the future have a lot in common.