latte

9 ms·

61.
by latte 9y ago
Python + Django + Pythonanywhere if I want to very quickly test an idea and make the prototype available on the internet instantly. As the project grows bigger, I would switch to PyCharm. If I need a front end, or easy to set up background
62.
by latte 9y ago
How good is the static analysis tooling (IDE / editor plugins) for Haskell? Given Haskell's powerful type system, I imagine that it must be possible to see warnings, hints, autocompletion and other early feedback about the code i
63.
by latte 9y ago
I use the RSS feeds ( https://hnrss.org/ ) for the HN front page and also for the Show HN (I find the average quality of all Show HNs to be surprisingly high - ever of those that don't make it to the front page). To read
64.
by latte 9y ago
Did a quick search to find out the background - it turns out that the author had almost no prior Android development experience, and in 2013 it won the first place in the Android app challenged conducted by Telegram. https://vk.c
65.
by latte 9y ago
Telegram's Saved Messages feature (which is basically a chat with oneself) helps me a lot - it loads in the web interface instantly and works like an ultra-light notes app, where you can also post files and images, search your notes, e
66.
by latte 9y ago
Thank you for posting this! What does your development workflow for CLJS browser extensions look like? Do you have to rebuild and reload the extension on your development machine each time you change the code? Is it possible to use Figwheel
67.
by latte 9y ago
Once you achieve the right result from the function you are writing, you just add that REPL invocation to your test suite. Then you just re-run your tests from time to time as you change the code further. A REPL makes writing both code and
68.
by latte 9y ago
You can't concatenate a path with an integer: >>> Path.cwd() / 1 TypeError: argument should be a path or str object, not <class 'int'> Also, note that the '/' operator is left-assoc
69.
by latte 9y ago
Just a minor note, in a couple of places there is "inherit" written where the author clearly intended to write "inherent".
70.
by latte 9y ago
I'd love to join - can you please share the link?
71.
How a tech CEO biohacked his intelligence(hackernoon.com)
2 points by latte 9y ago|2 comments
72.
Sulolive: 30k LOC full-stack Clojure online marketplace open sourced(github.com)
4 points by latte 9y ago|0 comments
73.
Wine glass size increased 7x over the last 300 years(bmj.com)
3 points by latte 9y ago|0 comments
74.
by latte 9y ago
Can you please elaborate how doing a project in Python (I have less experience with Java and am not familiar with Go) is less 'painful' than doing it in Clojure? Every time when I am trying to switch back from Clojure to Python, I
75.
by latte 9y ago
I have a site with Hebrew verb conjugations ( http://www.pealim.com ), which generates c. $150/month with 60k visits and 6 pages per visit. Re: scraping - I don't think it makes a big difference whether you have subscrip
76.
by latte 9y ago
From my experience, atoms are indeed rarely needed on the backend, where you have a DB to store the app state, but you can't do pretty much anything without them in cljs / Reagent.
77.
by latte 9y ago
Clojure's * can accept any number of arguments, including zero (returns 1 in this case), one (acts as identity function on numbers) or more than two (returns the product of all arguments). This helps to simplify arithmetic expressions
78.
by latte 9y ago
I find the advice on prefixing atom names with * very useful, especially for Clojurescript / Reagent code. I have never encountered such style before though - is it a widely accepted convention?
79.
by latte 9y ago
I was a 4th-year student in a maths / CS programme in Eastern Europe and had a part-time job as a web developer. Over time, I got the impression that being a dev is a low-prestige job with very slim chances of moving into any position
80.
by latte 10y ago
Exactly - core.memoize (or core.cache) is for production vs clojure.core/memoize for prototyping.
81.
by latte 10y ago
Thank you, an excellent explanation of how to use the JVM tooling! Also demonstrates why you shouldn't use certain functions, like clojure.core/memoize, in production.