Do your taxes by hand/with free fillable forms (name of the online service), you’ll learn a lot. Just follow the 1040 instructions (it goes line by line through the form) and any related forms it tells you to do.
1,361 karma · joined August 29, 2011
YC Badge: 0x47703e253c647bc5f43ed06dddd023428dab8321
Do your taxes by hand/with free fillable forms (name of the online service), you’ll learn a lot. Just follow the 1040 instructions (it goes line by line through the form) and any related forms it tells you to do.
Mercury's selling poings are: - runtime performance (automatic parallelization, very efficient due to logic programming understanding and rewriting sequenced operations) - static typing (in an ml style / like OCaml) - logic programming (unification of lvars)
As a language it fills an interesting niche as logic progamming language typically aren't dyanmically typed or high performance (ie Prolog, most miniKanren implementations).
Paul Bone has some good talks on Mercury if youre interested (heres some slides from an intro talk to Mercury https://paul.bone.id.au/pub/pbone-2015-mercury.pdf)
Your brain will unlearn the touch position of QWERTY, and looking down at a QWERTY, keyboard when you type will throw you off big time at first.
Eventually you’ll get used to looking at a QWERTY keyboard and typing Dvorak, which is interesting (my mind maps different letters between the layouts).
You can relearn QWERTY fairly easily once you’re confident in Dvorak, and you’ll be able to type in both, but I don’t ever find the need to type in QWERTY. When helping a coworker out on their computer I’d just switch their settings and switch back if I was going to be working there for awhile. Additionally you can get a WASD / CODE keyboard which has a hardware Dvorak dip switch, which is in Dvorak outputting to a system expecting QWERTY.
Edit (links):
OCaml: https://caml.inria.fr/pub/docs/manual-ocaml/libref/Printf.ht...
F#: https://msdn.microsoft.com/en-us/visualfsharpdocs/conceptual...
Haskell: https://hackage.haskell.org/package/base-4.9.1.0/docs/Text-P...
When I started the ketogenic diet, I felt much better, stopped exercising, and started losing a lot more weight rapidly.
I don't think it's simply lifestyle change, the diet specifically targets ketosis (which we are in naturally after 8 hours of not eating, i.e. Sleep) and maintaining the state to prolong the effects of ketosis (maybe indefinitely).
What makes you stop though is social eating, especially if it's pizza and beer :)
Also it's possible that your carbs weren't low enough (the diet is extremely restrictive, generally you want less than 10-20g carbs which is most / all from leafy vegetables) and you may have been stuck in glycolysis/ ketosis transition which makes you feel weak.
Why stop? Bread is delicious and it make social eating event difficult / less engaging. You can take a meal off from the diet and be fine, but it's a slippery slope of will power.
I'd strongly recommend finding an easier name to remember/spell though. If somebody told me "go to noisli.com", I'd spell it noisely.com. Ideally it should be something that's easy to remember and speaks to its function (noisey.fm, ambient.fm, and backdrop.fm are all available domains).
The best reward you can give is your respect and appreciation, especially if given publicly, signaling that you value that person. You'll be a stronger team if you can show true appreciation for one another.
(PS: Take the team out for beer too, obviously :) )
As for getting noticed, if you get you get fast at developing, I'd recommend participating in a hackathon and developing a simple, but useful, app with a random team. It's a great networking opportunity, and I still get startups and recruiters trying to hire me from my last hackathon (over a year ago now) in New York (I wasn't event looking for work).
My main experiences in building my first apps were:
1. Novel UI is usually not very intuitive, using what Apple gives you will take you far. People know how to use the basic UI elements, trying to teach users new behavior is hard (learned this the hard way).
2. Managing data will be messy if you don't use Core Data. I highly recommend going back to Stanford's iTunes U course and watching the one (two maybe?) on Core Data (and watch the Grand Central Dispatch one too if you're unfamiliar with it). Believe me, Core Data is awesome and once you learn to tame it you will learn to love it. Far better than rolling your own data storage/management.
3. Getting people to use your app is hard - make something useful. People download plenty of apps, but only open a handful of them. Don't bank on being another Instagram (there are plenty of clones), but make something really useful. TurboScan is a good example of this. Their UI is rather horrid, but its really good at doing what its meant to do. Its an app that is truly useful, and has made it to my (and my closest friends and family's) first screen. I probably use it 1-3 times a day because its actually very useful.
Good luck with your iOS adventures, love to see what you'd produce.