Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
amzans
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
241.
▲
Go Is a Shop-built Jig (2014)
(robnapier.net)
103 points
by
amzans
8y ago
|
76 comments
242.
▲
by
amzans
8y ago
It isn't necessarily about solving a problem that we had with virtualenv. For us it was already working quite well. It just simplified a few things for us. Like isolating Python versions, and also made the process of downloading and in
243.
▲
by
amzans
8y ago
I've recently had great success at work in switching from virtualenv to pyenv + pyenv-virtualenv. It makes it much easier to reason about your Python installations and it helps in keeping the system Python (MacOS) from interfering.
244.
▲
Managing Multiple Python Versions with Pyenv
(akbaribrahim.com)
2 points
by
amzans
8y ago
|
3 comments
245.
▲
Python Concurrency from the Ground Up
(youtube.com)
1 points
by
amzans
8y ago
|
0 comments
246.
▲
Frequentists vs. Bayesians
(beyondthelines.net)
2 points
by
amzans
8y ago
|
0 comments
247.
▲
by
amzans
8y ago
We don’t do it for every type, instead on a case by case basis. IDs are usually the obvious ones since we might have a Product class with fields like ProductId, BrandId, List[TagId], SellerId, etc... and it’d be nice to not mess that up. An
248.
▲
by
amzans
8y ago
Usually you would lookup the definition of those types just as you do for the function that you are trying to call. At least it’s a good idea to know what a function accepts before passing around your customer IDs ;) And to answer your last
249.
▲
by
amzans
8y ago
The problem with named parameters is that you can theoretically still pass the wrong value, and in practice not everyone is using named parameters on every function call. By relying on the type system you can catch that issue at compile tim
250.
▲
by
amzans
8y ago
Something that I enjoy very much in Scala is sealed traits + case classes. sealed trait Food case class FishTaco(size: FishSize) extends Food case class Burger(numPatties: Int) extends Food case class Spaghetti(sauce: PastaSauce)
251.
▲
Leveraging the type system to avoid mistakes
(beyondthelines.net)
167 points
by
amzans
8y ago
|
116 comments
252.
▲
On the design of distributed programming models
(blog.acolyer.org)
2 points
by
amzans
8y ago
|
1 comments
253.
▲
Macros: the plan for Scala 3
(scala-lang.org)
1 points
by
amzans
8y ago
|
0 comments
254.
▲
May 2018: Python and Scala climb the ranks of language popularity
(infoworld.com)
1 points
by
amzans
8y ago
|
0 comments
255.
▲
Monad transformers down to earth
(youtube.com)
1 points
by
amzans
8y ago
|
0 comments
256.
▲
Remote Procedure Call
(christophermeiklejohn.com)
3 points
by
amzans
8y ago
|
0 comments
257.
▲
Conflict Resolution for Eventual Consistency
(youtube.com)
1 points
by
amzans
8y ago
|
0 comments
258.
▲
An introduction to practical computing
(blog.krobinson.me)
1 points
by
amzans
8y ago
|
0 comments
259.
▲
Goroutines vs. OS threads
(groups.google.com)
2 points
by
amzans
8y ago
|
0 comments
260.
▲
Continuous Profiling of Go Programs at Google
(medium.com)
2 points
by
amzans
8y ago
|
0 comments
261.
▲
Threaded vs. Evented Servers
(mmcgrana.github.io)
2 points
by
amzans
8y ago
|
0 comments
262.
▲
Distributed Cache on Kubernetes
(jobs.zalando.com)
4 points
by
amzans
8y ago
|
0 comments
263.
▲
Functional programming is the libertarianism of software engineering
(erikbern.com)
1 points
by
amzans
8y ago
|
0 comments
264.
▲
The Software Engineering Rule of 3
(erikbern.com)
1 points
by
amzans
8y ago
|
0 comments
265.
▲
Three Months of Go (from a Haskeller's Perspective)
(memo.barrucadu.co.uk)
3 points
by
amzans
8y ago
|
0 comments
266.
▲
The Science Behind Functional Programming
(47deg.com)
2 points
by
amzans
9y ago
|
0 comments
267.
▲
Futures and Promises
(dist-prog-book.com)
1 points
by
amzans
9y ago
|
0 comments
268.
▲
Disorder and Tolerance in Distributed Systems at Scale
(slideshare.net)
6 points
by
amzans
9y ago
|
0 comments
269.
▲
Synchronous or asynchronous and why wrestle with wrappers
(blog.softwaremill.com)
1 points
by
amzans
9y ago
|
0 comments
270.
▲
by
amzans
9y ago
Your point of view resonates with me. Over the years, I've learned to test "what a thing is supposed to do, not how it does it". Usually this would mean to write high level tests or at least to draft up what using the API mig
More ›