Yxven
My short term memory is falling off a cliff. What do I need to do to prevent that from getting worse? Are there any other bases I need to cover that I don't know that I'm missing?
You wanted a Map<String, String>, and that's exactly what you should have made. A String is a convenience wrapper for storing a &str on the heap, so storing a String on the heap is redundant. The other options are for performance concerns, which you haven't mentioned any.
Like, I'm partial to Haskell, but if I'm actually trying to get work done, I reach for a language with a robust ecosystem. These days I reach for Typescript, but before then, python was my go-to since it's way nicer to program with than java/c++/c/javascript.
Currently, I think the nearest competitor is node with typescript, and I'd rather stick with python. Please tell me if I'm wrong.
Haskell's Yesod framework is pretty feature competitive with rails/django, but it doesn't have 1/10th of the community.
I'd love to see Haskell gain wide popularity, but I don't think it's realistically going to happen. People generally travel the path of least resistance, and learning Haskell requires a lot of time and effort before you can be competitively productive with it. Individuals will choose to make that investment, but the masses won't unless they are forced.
I think the closest thing to what we want right now is node with typescript.
The idea is that it acts as an irritant which increases blood flow and other healing responses to that area. Tendons in particular are thought to heal slowly because they don't have great blood flow. This strikes me as similar to the ideas of dry-needling and platelet-rich plasma injections.
I looked at flask, and the code for views doesn't look much different. It does look like it's missing form and model validation. Do you use a library for that or do you not do that?
1) I will tell you why category theory is relevant to you, the working programmer.
2) Here are the 2 most important data structures that you don't use in your day job.
3) Look at how they relate in this mathy not applicable way.
4) Conclusion: lambda calculus is awesome.
What I would like to see is:
1) I will tell you why category theory is relevant to you, the working programmer.
2) Here is a realistic but simplified problem and a solution written in python that is obviously the wrong approach to solving the problem. With category theory, we know this is the wrong approach because the math is wrong (and don't go into the math).
3) Here is another example that seems like a decent approach to solving the problem. With category theory, we know this is the wrong approach because the math is wrong (and don't go into the math). Doing it our way has these benefits...
4) Conclusion: learn category theory to become a better programmer.
If you can't do that, find some other way to illustrate the concrete benefits of learning category theory. If there aren't any concrete benefits, it's like telling baseball players they should learn physics to have a better understanding of baseball.
Compare that to the difficulty of writing a cross-platform GUI framework. It's not even easy to write bindings for existing GUIs because it's hard to wrap C++ in a way that doesn't have you manually managing memory or discarding other language features and philosophies.
This is why we're seeing the Electron approach to GUI apps grow. It's easier to write bindings for chromium and feed it HTML.
They both have 22g of carbs of which Lucky Charms has 10g of sugar while Cheerios has 9. Don't confuse branding with health. If your cereal doesn't taste like cardboard, it's probably bad for you.
Eventually, I'd become a decent CEO.
The trouble is our brains primarily adapt to repeated stimuli eg driving in good conditions. Since no one spends most of their time driving narrowly avoiding accidents, that activity isn't one the brain can learn to automate ( well, maybe it's possible with a realistic driving simulator), so dangerous driving requires everyone's full attention.
Since we don't usually have advanced warning of when dangerous driving will happen, the best we can do is spend as much time as possible paying attention to road conditions.
Studies have found hands-free phones are just as dangerous. http://www.cbsnews.com/news/hands-free-phones-just-as-risky-...
Cell phones are not dangerous because the driver was looking at his phone or playing with the buttons when he had an accident. They are dangerous because they encourage your mind to wander. Most people's brains are really not good at multitasking. (Try patting your head while rubbing your belly counterclockwise)
Anything that takes your mind away from the road when you're driving even if you can see the road is dangerous. (They found that talking to someone in a passenger seat is not as dangerous because if they notice danger and you don't, they'll inform you of the danger automatically by tensing up or whatever.)
If your brain worked like a single process cpu, it would be like setting Twitter to high priority while relegating driving your 2-ton SUV to low priority. It will work well enough most of the time, but sooner or later, you'll crash the SUV.
(Source: BS in psychology)
http://www.nytimes.com/2013/04/20/us/boston-marathon-bombing...
My search for phone service without a dataplan lead me to h20wireless prepaid. I expect my yearly phone bill to be $100 now. (I rarely call or text anyone)