Does what I need, and their google-drive integration makes it easy to keep track of the diagrams and share them with folks.
This should be done sooner rather than later.
I've seen it claimed that Couchbase should be on this list, but I've never seen a primary source which verifies that they were rejected from YC.
 - https://blog.blockcypher.com/what-adam-saw-that-sam-didnt-a0...
 - https://pando.com/2013/10/11/superhero-laundry-founders-laun...
EDIT - Citations
They were prepivot (Kindrid Prints) and YC didn't like their idea
* The community is great.
* Documentation is amazing, and up to date.
* Examples actually work.
* Installation is simple. Runs on multiple platforms.
* Clustering is easy. Sharding is easy. Management is easy.
* Built for today's needs, not for what we were doing 30 years ago.
If you haven't yet taken a look at RethinkDB, do yourself a favor and spend a couple hours dinking around with it. You may just be impressed.
*  http://rethinkdb.com/
Oh yeah, and something that is a cross between SPARQL and SQL 1999.
I teach community college and sometimes I wonder about the thought processes behind some of my students' papers. Paul Graham linked an essay he wrote in Stypi, where you could watch him write it in real time. This was clearly the greatest computer-assisted tool for teaching writing ever, and I immediately incorporated Stypi into one of my writing assignments. I wanted to know how much my students proofread, how they structured essays, and what they struggled with as they wrote. I was so excited about it that I wrote the entire assignment in Stypi and linked my students to the replay in case they were interested.
It was a disaster. So many students lost essays in browser crashes or were flat out unable to use the software. I ultimately had to apologize to my class, give everyone an extension, and cut Stypi out of the project.
Apparently they were acquired though, so I guess they made someone happy.
I did a quick check using Mattermark data of which YC companies got the most news since 2013 that are not still alive. It yielded (num articles / startup):67Homejoy13Tipjoy13Buttercoin6Tutorspree
This is letter known but AWS has a pen testing service.
a) simple laziness. A good review takes time and thought to write, and the time isn't necessarily in the writing the review, but in processing the experience after graduation. By the time you have a more balanced (ie, graduated, employed/unemployed) perspective, you've probably moved on to other things.
b) in my case, it's mostly due to general ambivalence about the experience. There were things I liked, things I thought weren't done well, and the overall effect is to cancel each other out. Ambivalence doesn't encourage taking the time (see above) to write down thoughts the way more extreme positive or negative views do.
c) also specific to me: I genuinely liked the instructors and most of my cohort, and writing anything negative seems impolite - not wanting to hurt someone's feelings or seem ungrateful. Irrational, but there ya go.
I imagine many people go into these programs to gain skills to get a job. If afterwards you talk about how the program failed to prepare you for that you're shooting yourself in the foot.
As to why there aren't more positive reviews - maybe it's related?
Provide ratings and info to the general public that don't just show rates, but trends, who drops out, comparisons of success rates for different groups, etc. Provide more structured but still anonymous feedback, for a price, to bootcamps as a consultant, or get a grant from a large tech firm. Publish papers in conjunction with academia on a delay.
I think what bootcamps could do, if they were willing to, is be much more agile in changing how they work based on research then a 4 year school, and actually do research and experiments to find better ways of teaching, and improve the industry as a whole.
If you review a bootcamp, you risk a permanent association with having attended a bootcamp.
It lead to several sites emailing me and asking me to write a review or to link to their sites. Here is what I wrote to coursereport:
>By completely ignoring the issue of student outcomes, your resource does prospective students a disservice. How about listing average salaries, listing graduation rates, linking to yelp profiles and linking to student directories for those schools confident enough in their outcomes to share them?
I hadn't looked at any of these sites in a long time, but to the best of my knowledge, very little has changed. They offer a comparison only of the costs of the various options, not the value. The person who emailed me did seem to express some vague interest in adding that kind of information later but two years later it's still not there.
At least for me, the main reason I avoided the "bootcamp review" sites is that I didn't feel any would have given me useful guidance as a prospect (whereas Quora, Yelp and HN threads would have if they'd been around when I applied).
FWIW: I did a bootcamp, loved it, never wrote a review. Just laziness/generally don't write reviews for things. I would guess many people don't write reviews for the same reason.
By that I mean the entry point for most participants are all different, the expectations for most participants are all different, the experience for most participants are all different (some students work harder than others), and the outcomes are all different.
I felt there was more to learn than there was time (I did a 12 week course), so how I felt after graduating was largely a reflection of my own confidence and ability in contrast to the effort I put in and not a direct reflection of the quality of the instruction.
The Dreyfus model of skill acquisition  is a useful reference here. Any program that claims you will gain mastery over a discipline in a dozen weeks is lying to you. The guys that ran my bootcamp were plain about that. They said they would help me help myself learn... which they did but not to the level I really wanted to get to. And that more than anything is why I am ambivalent about recommending them.
And sure, I'll freely cop to self-interest here. Bootcamp grads get enough shit from people in tech who want to dick-measure. I'm not going to do anything to further the cause of people who already think I'm an incompetent chimp with a keyboard.
Also, like the SwitchUp person already said in this thread, there's no reliable source of data for outcomes. I can tell you how long it took to get a job and what I made fresh out of the course, but why would you believe me, especially if you're already primed, like a bunch of people here clearly are, to believe that bootcamps are bullshit and their grads are rubes desperate to cover up the fact they got bilked? Maybe I'm just a plant; maybe I get paid a combined $200k a year by DBC/GA/HR/Flatiron to fire up 100 sockpuppets and argue that bootcamps are a good investment to con people on Reddit/HR/wherever. (That actually sounds like a super fun, super immoral job. Maybe I can trick them into actually paying me to do that. OR MAYBE I AM STILL MESSING WITH YOU. ~spirit fingers~)
My friend did a local bootcamp and now he's doing ASP.NET work and loves it! I'm just scared of doing that specific one because I don't really have interest in anything microsoft.
I used to do surgical AR. The immediate-now-future is nanodevices, rDNA pharma / gene therapy, and more exotic chemistry. Hardware and software only play a supporting role and smaller role in the final clinically approved therapy. No matter your background all require organic, molecular and various biochemistry or medical skills - probably not as much mechanical engineering as you hope now that CRISPR is here.
I'd love to work on something like this too!
Also, don't obsess about making the code and architecture good. Get it working to prove the idea works then using what you've learned you can go back and improve it. I see so many side projects fail because many coders obsess about making code perfect over more important things. Releasing a project with imperfect code is vastly better to never releasing anything because you procrastinated trying to write perfect code in my opinion.
It doesn't matter what kind of project, always include one more week.
Don't be upset if you can't stick to your plan, allow yourself an extra week.
It's not your fault, that's basically software engineerings nature.
You should get out daily, for at least 1 hour.Simply because that one hour is for recharging your brain, which again leads to better performance.
Also what I try to do, when I'm doing a hackathon, is that I'm looking for templates from themeforest or wrapbootstrap.
There are also a lot of good templates for your framework, where auth/register/signup/signin/roles etc. is already done for you.
I don't like reinventing the wheel, I'd rather focus on the business logic.
2- Work in 25-5 bursts. What that means is that you cut yourself completely from any disturbance, which include your phone, emails, social media, family members... for 25 minutes, that you dedicate completely for work. Then take a 5min rest. Its very effective and something that i do myself.
3-Hire a frontend developer or buy a ready made theme to only focus on the backend stuff. Since UI is very important.
Good luck with your project mate!
Also, I have found that at work it is ok if you get sidetracked sometimes because your guilt or sense of responsibility to your coworkers and company will refocus you soon enough. If you are like me, then you have no such thing when working on your own thing. For that reason, I highly recommend keeping regular, well defined work hours. I would even consider one of those apps that won't let you connect to FB, etc. while you work.
As far as technology goes, you can build a solid prototype website in anything these days. Pick the language you know best and also pick a solid foundation. By that I mean do as little as necessary to make the prototype work. Don't fall into the trap of using this as an excuse to try something new (if you want to actually get it done that is). Frameworks are great for this for example.
Lay out the entire 20ish blocks and post them here/email to your friends and family or to some other entrepreneurs that you do not want to dissapoint by not getting stuff done.
Every day, update the post/email with a status, did you get the blocks done and if not why not, what did you learn and what will you do differently tomorrow?
In the end, I hope you'll become a successful technical CEO and great company because you've learned a lot more than an API or two.
You should work each day like you're going back to the office in 2 days.
I did that once, a long time ago, and it took me on an amazing adventure.
check out http://7daystartup.com/ as well. dan occasionally throws a 7 day startup challenge where a bunch of entrepreneurs gather online and start a business in a week
That sounds so far up the chain of abstraction and generality, that its easy to dismiss the book. Dont! The book is impressive partially because it manages to distill useful truths which are applicable at such a general level.
It's written by Ray Dalio, who is undoubtedly extraordinarily intelligent and remarkably determined to self-improve. He is the founder of the hedge fund Bridgewater Associates and consequently the 69th richest person in the world in 2015.
The firm itself is noted for its unique company culture. He believes that people can only improve through feedback and that there are strong social conventions and cognitive barriers which prevent people receiving the feedback they need. At Bridgewater, every meeting is recorded and broadcasted to the company. At any level in the company, if someone is being considered for a promotion, they will be invited for a discussion. Senior executives will discuss, in front of the candidate, the merits of whether to promote them or not.
The book contains elegant, simple, yet crucially important truths. They seem obvious at first sight, but he fleshes them out in such a way that you realise you don't really act consistently with those truths, even if you perhaps trick yourself into believing that you do. Through reading the book, you can internalise some of his approaches in understanding the world.
Its a book which altered my way of thinking about the world in a profound way.
PDF link here: http://www.bwater.com/Uploads/FileManager/Principles/Bridgew...
> It chronicles the experiences of a computer engineering team racing to design a next-generation computer at a blistering pace under tremendous pressure.
- The obstacle is the way (Ryan Holiday)
- Meditations (Marcus Aurelius)
- Level up your life: how to unlock adventure and happiness by becoming the hero of your own story
- the six pillars of self-esteem
- so good they cant ignore you
- the power of habit
- how to fail at almost everything and still win big
- soft sell: the new art of selling
- essentialism: the disciplined pursuit of less
- the magic of thinking big
- everything is negotiable
- making things happen
- lean customer development
- what customers want
- inspired: how to create products customers love
- delivering happiness
Now that I'm working with them,I realize those books aren't fiction: they're documentaries.
Prior to reading this, my politics aligned very closely with those of Sanders and I thought everybody on the right were selfish, evil, close-minded fools. After reading the book, my politics are still left of center (but definitely right of Sanders), but I think I understand and appreciate the politics of my right leaning family and friends.
How to win friends and influence people -Dale Carnegie (The definitive guide to helping you work better with people, truly great book, should be required reading)
Blink- Malcolm Gladwell
Godel Escher, Bach - (Recursion, but not from a software perspective. Its a glorious book that will change the way you think about recursion.)
Hitch Hiker's guide to the galaxy, - Douglas Adams (Glorious book that is a fun read, when you need a break pick this up and laugh hard)
Foundation Series - Assimov (Great stories from one of the best sci-fi writers ever)
-------------------Software relatedCode CompleteConcrete MathematicsThe Art of Computer ProgrammingThe Design of the Unix Operating SystemIntroduction to Algorithms -CormenDesign Patterns Elements of Resusable OO Design -Gang of Four
It's about Stewart Brand, but really more about the scenes he was involved in, it's not a biography. Covers the Whole Earth Catalog and the WELL, but also talks about the influence of systems theory and Bucky Fuller, and clarified, for me at least, the difference between the New Communalists and the New Left, which were somewhat conflated in my mind. It also puts Stewart Brand as a character, if not an essential one, at some key events. The mother of all demos and the founding of the Homebrew Computer Club are what I'm referring to here.
Gig: Americans Talk About Their Jobs https://en.wikipedia.org/wiki/John_Bowe_%28author%29#Gig:_Am...
If you're interested in project management, Making Things Happen is good.
I've just started High Output Management and so far it seems good. Of course there are always the classics like Good to Great, What Color Is Your Parachute, etc
Some people I have spoken to say his method isn't for them but I've found it useful, even if I haven't implemented everything he suggests.
I'd also recommend "Code: The Hidden Language of Computer Hardware and Software" by Charles Petzold. It starts at simple circuits and builds up a picture of how computers work. It has really helped me get my mental models of what's going on inside a computer straightened out!
When breath becomes airhttp://smile.amazon.com/When-Breath-Becomes-Paul-Kalanithi/d...
Do no harm, Stories of Life, Death, and Brain Surgeryhttp://smile.amazon.com/Do-No-Harm-Stories-Surgery/dp/125006...
The Song Machine: Inside the Hit Factoryhttp://smile.amazon.com/Song-Machine-Inside-Hit-Factory/dp/0...
Why we workhttp://smile.amazon.com/Why-We-Work-TED-Books/dp/1476784868/
Caro, a Pulitzer winning journalist, is a wiz at writing, so you'll enjoy each page. But more importantly, even though Robert Moses was a bad buy, you don't have to be bad to learn to get what you want, in an organization, by ignoring superficial power structures, and focusing on the real ones.
Plus you'll learn a ton about how NYC was built out in the depression.
Structures: Or Why Things Don't Fall Down. About the engineering of various things, mostly buildings. Highly recommend.
The Elements of Computer Systems (better known as NAND to Tetris). Describes a computer from the bottom up.
A History of the Arab Peoples
Space and Time in General Relativity by David Mermin
Feynman QED: The Strange Theory of Light and Matter
: http://www.amazon.com/Legionnaire-Englishman-French-Foreign-...: https://en.wikipedia.org/wiki/Simon_Murray
This is a novel, but Carlos Ruiz Zafon's The Shadow of the Wind is fantastic.
https://minireference.com/ 4.5 stars on amazon http://www.amazon.com/No-bullshit-guide-math-physics/product... If you're getting a print version, I recommend the version through lulu.com, since the print quality is better.
"Code: The Hidden Language of Computer Hardware and Software", by Charles Petzold
"Rework", by Jason Fried and David Heinemeier Hansson
Ed is an incredible human being! Go read it!
If someone else is familiar with Oz/Van Roy stuff, I have a question.
So if I need a quick scifi buzz, I pick a random story from the megapack.
The Inner Game of Tennis
A Guide to Better Movement: The Science and Practice of Moving with More Skill and Less Pain
Punished by Rewards
Microeconomics: Behavior, Institutions, and Evolution by Bowles
Softwar (Larry Ellison), Matthew Symonds
A Perfect Red, Amy Butler Greenfield
Assault on Lake Casitas, Brad Alan Lewis
This Census-Taker, China Mieville
Whatever, Michel Houellebecq
Freedom from the Known, by Jiddu Krishnamurti
Think on These Things, by Jiddu Krishnamurti
The Bhagavad Gita
The Grand Design, by Stephen Hawking
The Hard Thing about Hard Things by Ben Horowitz
Strategy Rules - Five Timeless Lessons from Bill Gates, Andy Grove, and Steve Jobs by David B. Yoffie, Michael A. Cusumano
These are all timely books and recently written.
>J. Hromkovic: Theoretical Computer Science: An excellent introduction to complexity theory, kolmogorov complexity, automata and turing machine, language and grammar theory
>Harris & Harris: Digital Design and Computer Architecture: Introduction to electrical engineering, graudally builds your knowledge until you could implement a simple little CPU in e.g. Verilog.
* Nassim Nicholas Taleb. Antifragile, things that gain from disorder http://www.amazon.com/Antifragile-Things-That-Disorder-Incer...
* Jared Diamond. The World until yesterday, what can we learn from traditional societies http://www.amazon.com/World-Until-Yesterday-Traditional-Soci...
* Frans de Waal. The Bonobo and the Atheist: In Search of Humanism Among the Primates http://www.amazon.com/Bonobo-Atheist-Search-Humanism-Primate...
* John Higgs. The KLF: Chaos, Magic... http://www.amazon.com/KLF-Chaos-Magic-Music-Money-ebook/dp/B...
* Joseph Jaworski. Synchronicity, the inner Path of leadership http://www.amazon.com/Synchronicity-The-Inner-Path-Leadershi...
* Piero Ferrucci. Your Inner Will, finding personal strength in critical times http://www.amazon.com/Your-Inner-Will-Personal-Strength/dp/0...
* William Irvine. A Guide to the good life, the ancient art of stoic joy http://www.amazon.com/Guide-Good-Life-Ancient-Stoic/dp/01953...
* Chogyam Trungpa. Shambhala: The Sacred Path of the Warrior http://www.amazon.com/Shambhala-Sacred-Warrior-Chogyam-Trung...
* Tomas Malik. Patience with God: The Story of Zacchaeus Continuing In Us http://www.amazon.com/Patience-God-Story-Zacchaeus-Continuin...
* Nick Winter. The Motivation Hacker http://www.amazon.com/Motivation-Hacker-Nick-Winter/dp/09892...
* Chas Emerick, Brian Carper, Christophe Grad. Clojure Programming http://www.amazon.com/Clojure-Programming-Chas-Emerick/dp/14...
* Peter Hamilton - The Reality Dysfunction
* Neal Stephenson - Cryptonomicon (his other hit: Snow Crash is surprisingly more history then SF now...)
One reason I wanted to read the book is Kissinger and Nixon are responsible for establishing relationships with China. My parents generation were able to come to the US because of them. Many older Chinese immigrants have positive opinions of the two, despite them being amongst America's least favorite politicians.
I tend to push at the first opportunity it makes sense for other people to see my code, and then push again whenever I make enough incremental progress towards the feature to share. Our team has a culture of opening "in progress" PRs early and often to get feedback before we are too far along. This is great to share ideas and feedback about how things should work (instead of just about how they do based on implementation). It also helps keep the final code review size / time down.
Recipe for disaster. :p
> knew people who pushed / committed like every 30 seconds
Pushing and committing is completely different actions in the git world.
If it's a simple fix then I try to commit and push almost instantly. If it is a large piece of work that needs several days, then I "checkpoint" it by committing at least once/day.
But I try to never checkpoint by committing something that breaks the build or unit tests. Like if my work is rewriting module A to B, then my first commit would be to add module B, second to change all dependencies from A to B and lastly to delete module A from the repo.
But seriously, I commit regularly, and rebase locally before pushing, whenever possible.
It's not really about how often you commit, it's about documenting that commit as a single unit of work so looking at it it's clear what you did, and why. This often requires planning ahead of time, and even possibly creating a separate branch just for off topic commits that you think of while working on the same file.
I'm not perfect though, it's okay not to be perfect.
If you just updated a typo in some comments, it could make sense to commit it and it could take 30 seconds.
Now if you are always committing as frequently, either you are working on very easy tasks with no dependencies, either there is an issue.
Here's the code in case you wanted to use it:
if git diff --exit-code --quiet then echo "There are no changes to save, NONE!"; else echo "Stage everything for commit -------------"; addit; # an alias for "git add -A ." echo "Commit all changes with message $@ --------------"; commit "$@"; #commit is an alias for "git commit -m" echo "Push branch to remote --------------" psh; # an alias for git push origin $(git branch | grep "*" | sed "s/* //") fi
Use it like this: savework "COMMIT MESSAGE HERE"
In general, I try to be very atomic. As an added benefit, this makes it simpler for someone doing a git bisect later.
Fixing minor typos or copy changes across a few files could result in several commits within 15 minutes.
Working on a major feature that requires research and definition and a lot of conversation or feedback, might mean a few commits over the span of a few days.
Working on something that will take a week to be atomically complete and testable? (For instance, a major refactoring.) I'll write myself a checklist of steps and commit every time I complete a step.
As someone else said, once every 30 sec is too often, and once a day is too infrequent if you're coding 8 hours a day. When I'm in a rhythm I'll typically go anywhere from 10 min to 2 hours between non-trivial (e.g. typo-fix) commits.
I do not push every commit immediately. Once a day is a good minimum as a backup strategy and if you want to make sure you can work on the codebase from elsewhere or if you have a CI system to warn you of merge conflicts.
I'll also push whenever I complete a ticket (for long-running branches we typically have sub-tickets, or I'll push when I've completed work that someone I'm sharing the branch with can build on.) Git makes it easy to develop those units of work on separate branches, and when you merge them back to the feature branch is generally a good time to push.
I'm not sure there's a generalizable pattern there for which has a lower actual time interval between commit/pushes but I suspect that I tend to be spammier with them in personal projects.
Using this model I do work in progress commits as needed for different features using many different branches. Those wips and committed locally and are pushed to the remote fork many times per day for backup. For example I can do a quick push before going to lunch or meeting. I can also fetch, rebase, squash, and force push commits as desired because the only history I am affecting is on my own fork. The final merge to the "main" repository is usually 1-2 commits squashed from all the wip commits. Once that is merged I, since I am usually working on a feature branch, I can delete that branch locally and in the remote fork.
Every 30 seconds seems like a bit much, but it wouldn't be unreasonable to say I commit and push 10x a day.
30 seconds is too often. Once a day isn't often enough.
I agree with that but i'd add that i'll also commit at any stopping point. Need to leave for work? Commit. Need to go home ? commit. Doesn't matter how broken the code is at that point. I'll rebase the ugly commit away. Usually the ugly commit will have a message like "INTERIM COMMIT - REBASE ME"
I'll also happily push these ugly commits to a topic branch on a remote machine for backup purposes as long as I know that no-one else is working on that branch.
I push whenever I'm about to shutdown the laptop or by the end of they day.
I prefer this over trying to get every commit right the first time. I also feel there's a nice change of pace in the process of stepping back, looking over the previous work, and shaping it into something that communicates the ideas well to reviewers.
Committing every 30 seconds seems like it would knock me out of my flow so often that I wouldn't get anything done.
That being said, if I'm working in the same files as someone else, I'll commit every few minutes (and so will they) so that the amount of conflicts we're creating don't get out of hand.
New commit for new logical "part" of feature.
Rebase interactive when feature is "done" (in some way) to fix commit messages and squash some extraneous commits.
Push (as a branch in forked repo).
Sometimes I push before the feature is complete for backup/accountability purposes, but then I rebase anyway and push force the thing once it's done.
push and push regularly, in case you have merge conflicts. Get the continuous integration server building on commits and please have it email the team when the build fails too.
How often do you press "Save Game" during a new level?
You're probably committing and pushing at acceptable times. Screw the consultant.
I think you have to get this right in Silicon Valley for it to work everywhere else.
Unlike some simple SaaS that you can build while living in Thailand, this has to appeal to THE place where such ideas can work, before it can spread everywhere else.
What I will do and currently do is keep in contact with guys from old companies and they are welcome to flick me a mail and I'll reply with some guidance as far as is practical
I think it's worth a shot. I think a lot of devs and companies might be uncomfortable with the idea at first, but that's what early-adopters/trailblazers are for (to show everyone the way, and prove that the concept works).
Your company wants to use spark. And you literally have no-one in the company who has ever used spark or wants to read a book on spark.
And there is a company that knows spark, and happens to need a skill you know. And no one in this second company knows it, nor does anyone in the second company want to read a book or learn about it.
something online might work better.
Now I keep a top-10 list only, in an evernote file. If I want to add something to the list, I have to delete something else. And the next time I have spare time to build something, I'll just have 10 good options to choose from, instead of a thousand terrible ones.
Ideally, I should have placed the file under version control from the start so I could reference when a particular idea came to mind, but I didn't do that.
My actual project planning docs are all text files though, and those actually are under version control. I find using a blank commit message works best because it lowers the barrier to further editing or writing.
Easy to sync between the two using plaintext files in a Dropbox folder. About as lightweight and easy to search for simple notes (whie still working on both desktop and mobile) as I've found.
Caveats: not great for longer notes, and keeps things super simpleso mostly great for collecting ideas.
I keep stuff here that I add to frequently; other things I typically move elsewhere to organize / editI love Scrivener for this but also use Google Docs for certain things.
I always tell myself I should document them on a Trello board then I can add notes to each idea when I think of things.
Depending on the folders, I visit them once every month or so, or almost never. It just depends what I'm into at the time, but I can always get them later.
When it comes to afk, I usually use evernote, but just as a basic notetaker that I can type up later.
When using 'clip to Evernote' browser extensions to add research materials you add same tags and then you have nicely linked together idea + research material.
I used to use index cards for storing ideas, but if you move often or just away from them - they are not so useful.
Hassle of digitizing notes are compensated by better availability.
For quick notes on a move I may use voice memo or voice note and then type in when I'm at the computer.
I revisit old files at odd intervals. I have ~5 years worth of notes. What I love most is when I think I have a new idea, or stumbled upon original inspiration, and I find an almost exact sentiment mirrored years ago, albeit using different language. Then I know I've revealed some deep truth that will remain constant for me, and it is only my manner of expressing it that has evolved!
Yesterday I just finished putting all my family cooking recipes into a single JSON file so they'll easier to digest. This morning I started on compiling all my notes to a single JSON file too, adding summaries, detailed explanations, tags, and categories. After I'm done I plan on making a nice Webapp to add, search, and view entries.
Also, have another column for things to read. Things to research/investigate.
Organizing can come later once I refine the ideas.
The most important thing I have to keep in mind here is to include terms that are good for search (not too generic, otherwise they bring up too many results).
Recently I've been experimenting with markdown documents in a git/hg repo. I haven't quite found an iOS vcs+markdown editor I'm happy with though, so it's not a full migration from notes.app
I also include little icons that represent the category so I can visually browse and filter pretty quickly and easily as I scroll through it.
Simplenote mainly because I never found a satisfying way to sync my txt files across all devices
It's also easy to sync and access on all devices.
I email myself. A movie recommendation to a really really good idea.
Simplify and reduce.
@vijayshekhar Mar 4 "@ConversionChamp @vijayanands @RajanAnandan @dkhare we offer recurring on CC too!"
Wrote a blog post to document what I found: http://www.redbridgenet.com/indian-payment-gateways-no-recur....
There's some links in there to discussions of the same. The Quora discussion is starting to fill up with what I think is spam for services that don't exactly solve the problem, but it might be worth checking out.
definitely some more
Also .. where are you based (trying to judge cost of living of areas vs mine)?
Congratulations on following your dream, I wish I had the same opportunity.
I'll give it a try and tell you more later.
One piece of feedback - I get a popup to login to Game Center every time I open the app. If I don't want to login, it would be nice if you stopped bugging me about it.
Apart from that, well done on shipping!
One thing: I wouldn't place the bar that counts down a powerup's effect at the top-left beside the score. It's way too small and is pretty much outside my field of view while I'm carefully placing bumpers in the lower portion of the screen.
This is plainly some thinly veiled advertising. This belongs on Reddit imho (it also has a way larger userbase).
There are things we're working on to reduce the number of duplicates that are appearing, though. It's taking a while because the problem is trickier than it seems, but we'll get there.
"All together, we drive more than 3 million miles in simulation every day."
I would assume they run the logic unit through simulations independently of the other systems in many instances.
Edit: actually it looks like the story was submitted at https://news.ycombinator.com/item?id=11222681. Posting your text as a comment there would be a good idea.
Security engineering is largely about managing complexity and having a firm grasp on the system you're securing, so it's definitely a win there too.
It's weird that we have IPv6 widely provided by consumer ISPs (wireless & wired) but AWS & GCE are the ones holding the whole thing back. A while ago it everyone assumed that servers are the easy part and getting consumer ISPs to play along was going to be hard...
About clients ceasing to have IPv4 connectivity, that's anybody's guess. It will definitely be a "happy problem" if/when that starts happening at some point in the distant future.
- I've got a new modem from aaisp.net and didn't have to do anything.
- I've checked an "IPV6 (BETA!)" checkbox in my hosting provider's control panel.
- I've copied & pasted my new IP and added it to AAAA records for my domains.
And to my surprise, everything just worked. My mobile phone used IPv6 even before I knew. I didn't have to troubleshoot anything. The biggest snag I ran into is that `ping` has a separate `ping6` version.
Eventually all your traffic will be IPv6 and you wouldn't have noticed. Unless you have to migrate IPv4 only devices, in that case you'll be tired of hearing about it :)
The hardest part seems to be training people. IPv6 is different - it is more than just "longer addresses".It is a newer protocol that fixes many more problems with IPv4 than just address exhaustion.So this "ipv6 migration" is actually an opportunity to leverage those new features.
Designing IT infrastructure IPv6 first and IPv4 second allows for so much simpler designs.You can have your complete network IPv6 only and do IPv4 on the edge for legacy clients. (Maybe doing outgoing NAT for v4 where required)The results are a much cleaner layout (because of the larger address space), simpler firewall rules, and so on.
It is not complicated or hard to do (in contrary I think that e.g. just setting up SLAAC is much simpler than managing DHCP) but the engineers need to know how it is different.They need training for that. People are often used to the old ways, once they have seen and worked with IPv6 it is no problem.
I've helped larger and smaller companies since ~2004 with those migrations.One observation I've made is that here in europe IPv6 is a basic fact of networking where as in the US it appears as if many companies are in denial.That cloud providers like AWS don't do native v6 is absolutely ridiculous.
When you write code or security rules today that is not designed with IPv6 in mind they are outdated today. Don't do it ;-)
(Back in 1993, when a guy said that MS-DOS would be in use by 2000, I laughed at him. I made serious money on MS-DOS+xBase until 2005!)
This is driven partially by mobile deployments, partially by some ISPs rolling out support. Note, that the IPv4 address exhaustion referred to in the media is IANA-level; top-level exhaustion occurred on 31 January 2011 . Also from there:
* Four of the five RIRs have exhausted allocation of all the blocks they have not reserved for IPv6 transition; this occurred on 15 April 2011 for the Asia-Pacific, on 14 September 2012 for Europe, on 10 June 2014 for Latin America and the Caribbean, and on 24 September 2015 for North America.
None of this impacts end-users, as ISPs have large reserves of non-used IPv4 addresses; and there are multiple mitigation strategies for post-exhaustion periods.
Also note, that even if all IPv4 address would be in public use currently, we still wouldn't "migrate" to IPV6 at-once: seeing how there are roughly ~25 billion Internet-connected devices (and 3.17 billion users) using it currently, migration can't take place overnight. Also note, that "pure ipv6" devices currently would be heavily disadvantaged: the majority of sites & services can't be accessed via ipv6 yet.
A probable migration pathway might be ramping up allocation of IPv6; as usage increases, servers will roll out support for it; which might hit a tipping point (similar to the current "HTTPS for everything") sometime around the 40-50% penetration rate. Once that occurs, ipv6-only users will no longer be disadvantaged; that, along with increasing price-points for dedicated ipv4 address might shift ISPs to start deploying ipv6-only, and use relays to access ipv4 services.
However, even under these conditions, servers will almost certainly will provide v4 access points, for reasons of maximum compatibility, and low cost (relative to all dev, deployment, domain, etc costs).
In conclusion, you can rest safely knowing that the code you wrote will be in use for a long time to come.
Many users aren't even aware of this, though, because the number of consumer-grade routers that support IPv6 is very small. I think that the Apple Airport may be one of the few, along with a few higher-end Linksys/Cisco ones (although lots of $100+ Linksys units don't, and they seem to be in absolutely no hurry to implement it via firmware updates -- I'm sure they see it as an opportunity to sell new hardware in a few years).
Consumers don't know to look for "IPv6" as a feature when they're buying a router, and so as a result Linksys et al don't bother to include it, and so even though a user might have a fully IPv6-capable uplink, there's no way to use it short of plugging their computer directly into their modem.
What you've actually been hearing about is various IPv4 exhaustion milestones. The world didnt suddenly "run out" of IPv4 all at once.
The first big milestone was IANA running out in 2011. This meant that the regional registries (which actually hand out IP blocks to ISPs and large networks) could no longer get new space from the global pool. APNIC, the regional registry for Asia-Pacific, ran out a couple months later. (They didnt "run out" as much as they went into a strict rationing mode.) The same thing happened to RIPE NCC (Europe) in 2012, LACNIC (Latin America) in 2014, and ARIN (North America) last September. (Interestingly, ARIN decided not to do any sort of rationing, North America is just completely out.) AFRINIC (Africa) is the only regional registry with enough space left that they're not rationing.
What does it actually mean that the regional registries are out of IPv4 space? It means you can't just go to a registry and say "hey I need more IP addresses" and pay your annual membership fees. You now have to purchase IPv4 space on a private market. Current prices actually aren't that bad - about $10/IP. So to be honest, it's not a huge crisis despite the regional registries having run out. The serious problem will be when it becomes impossible for companies to get the IP space they need at an affordable price. Ideally we should push for higher IPv6 adoption before it becomes a huge crisis.
IPv6 adoption is already at the point where it is relevant to your security checks. If IPv6 clients are exempt from your security, that is a problem right now.
All that being said: it's about time Hacker News itself becomes IPv6 ready!
IPv6 deployment looks like now. It's finally happening, but slowly.
As a professional, you can ignore it for now, but soon you will be expected to know it and be able to operate it. I give it 5 more years.
Applications are the key driver. I could see this if IOT really takes off - autoconfiguration and unique addressing are the attributes that would make IPv6 the only compelling choice. That said, IOT still has a ton of challenges.
Until that point almost everyone is going to be dual stack.
At that point we start individually writing documentation for our respective pieces, (as if those services already existed). This might take the form of Readme files, wikis, or formal API documentation.
Normally the process of writing documentation (and getting feedback on it) flushes out of a lot of issues. When everything is documented and everyone is on the same page about what everybody else is doing, then we write our tests and repeat the same feedback process. Once everyone's tests are on the same page, then we write our code, and do a code-review when that is done.
Even with all those checks and balances, mistakes and confusions and miscommunications still happen. But having those regular check-ins to flush out issues before the real code gets written can save a lot of headache. If you get to the code review and find an issue, it's probably not going to be a huge one.
Prototyping the user interface can be done by any number of people any number of times, since the goal is to experiment with different ideas. The backend APIs are usually mandated by what the user interface requires.
http://hnjobs.io/ (I think was giving errors last time I checked)
I've seen it, but am drawing a blank as to how to find it right now. I've seen a couple different formats.
Wish I could be more helpful, but I'm in a meeting at the moment.
When http://www.productchart.com was on the frontpage and got 79 points, Google Analytics reported 2752 visitors from news.ycombinator.com. Looking at the rest of the statistics, my guess is that another 2000 came from here but without referrer.
This is the submission: https://news.ycombinator.com/item?id=8907681
From memory it was around 25,000 - 30,000 visits
What was interesting was that 2-3 days later when its spot on HN was probably on the 3rd or 4th page or maybe more, the page was still garnering a considerable number views from HN.
Make sure your S/O is onboard. If it is a serious relationship you owe it to them. If they are not you have some hard choices to make.
Your relationship is just as important (probably more so) as everything else, so give it space on your calendar. You can afford to take an hour to make dinner for your partner. Plan the rest of your work around it, even if you have to do so days ahead of time. Once dinner is ready, leave your phone in the other room.
If Obama can make time for dinner then you can too.
Most importantly: remember to thank your partner for picking up the slack so resentment doesn't build.
Specific to startups / starting a company, have a series of serious conversations about:
1. how much money you are going to set aside to get it to work
2. work life balance during the week, during the weekend, during "evening hours"
3. go / no go decision points (funding decisions, customer road map, founder / employee relationships)
4. social life
5. how much they want to be part of the company (as you will be living it, they'll be there to listen, but do they really want to listen 24/7/365?)
6. your goals, their goals, your goals together and how they match up with your goals for the company.
At this point it's just a business decision. Extra taxes and costs for you? Document what they are, bump the offer up by that amount, and counter. They most likely don't know the tax law in your country and so they won't realize this is a burden to you.
"It's fine to not pay me healthcare or give me options, but there's an issue with having to setup my own company. In my country companies are required to pay XX% tax on revenue, and then I also have to pay a personal income tax. I'm happy to setup the company to make this work, however to do so you'll need to bump your offer up by XX% + $Y,000 for the additional overhead that comes with managing the company's paperwork, registration, and legal fees."
It could be a good arrangement that could evolve into long lasting, beneficial relationship.
Maintaining all of that for a company in the US is a huge time and money cost. On top of that, maybe operating a foreign office would raise their taxes significantly.
Overall its not a bad deal just because of this. Just make sure that you factor in the cost of any benefits and if you get taxes are worse for being a contractor (though you may be taxed less if you are able to write things off like in the US).
I also work full-time remote for a US company and I bill through my company in Germany. You could be hired as an actual employee, however they would legally need to follow the law re employee tax/benefits of the country that you reside in. This is obviously a pain to manage between both parties, which is why "digital nomads" bill through their own ltd.
You could negotiate extra for benefits, but it sounds like you will have the work locked-in (i.e. you're not a typical contractor who can charge a premium as the work is fixed).
Where do you live? For me, the difference in being taxed as an ltd is trivial; actually, it's better as I can claim extra back as expenses through the business, like electricity, internet, etc.
All of hired engineers have to have own company or entrepreneurship license in domestic country. Charges are above average wages, but you have to take care about all related staff: insurance, taxes etc.
In this case it's better to hire accountant, but it's still worth.
yeah, we remote employees / contractors / freelancers / consultants do invoice through our own ltd companies
an accountant unless they are really expertized in cross-border deals usually is not of much help, but there are some knowledgeable
if you are from EU, establishing residence, registering an ltd in britain and getting paid in UK makes sense more than doing that in mainland europe. given there is double taxation treaty between UK and rest of europe (EU and non-EU) you don't owe your country any taxes as you paid them in the UK. also, you can get paid by that company without changing residence as a sole trader in your country of residence
millions of mainland europeans have their companies incorporated in the UK
Check with a local accountant who is competent in these matters.
2. It helps me communicate better professionally, whether verbally or written.
3. It's nice to share knowledge when you learn something new, especially something you think can help many other developers.
4. It's another thing to show off and market to potential employers.
5. For me, writing things out makes everything more clear in my head, and hopefully the reader's as well.
6. It holds me accountable to continue learning new things. I force myself to write 3 technical blog posts per week, and I can't do that if I'm not learning new things.
if it is something I already know, it looks too simple to write about;if it is something I know a little or nothing about, I am afraid my learning notes will be not good enough.
In both cases I don't want to show myself as some noob :)
Now I blog because I want to spread my ideas and educate people, that get me to the keyboard easily and words seems to flow from my fingers :)
- honing my writing skills
- getting better at conveying a message and explaining complex concepts in simple terms
- structuring my ideas and thoughts
This could be though an acquisition, IPO, or the board deciding to let you sell your shares (usually back to the company via the right of first refusal).
Your shares are sort of "worthless" until one of these events, that is the risk you take by allowing some of your compensation to be delivered in private stock.
The good news is they are offering you a .25% vested stake and a shorter-than-normal vesting period of 3 years. Once those shares vest they are yours forever, or until you sell. If you decide to leave the company there is a chance they will offer to buy you out of your vested shares, that is where you can make some cash.
Possible answers (not exhaustive):
1. We plan to exit
2. We plan to pay dividends
3. We plan to build and support a private market
4. We plan to institute a buy-back program with the valuation based on some objective criteria (FMV / x revenue multiple / x profit multiple)
In all cases, the thing you want is that the owners make money off of the stock in the same way you do and that they have the same class as you.
Not all small businesses are startups though. If you are working for a lifestyle business, or even a larger company that has relatively slow but steady growth, then the board may decide to issue dividends.
It's important to remember: your equity is worthless, but so is everyone else's. If you trust the company leadership and they aren't just using this as a way to get cheap labor (i.e. they will pay dividends, buy back your stock later, get acquired, or IPO) then it could be a good deal.
My recommendation: if the company isn't a traditional startup and offers fair pay (or will increase compensation down the road if they are early stage now), then add some terms that require the company to buy back your vested shares when you leave. You can set a predetermined price (like 2x the current value), or base it on milestones (time you spent there, revenue milestones, etc). Just make sure that you don't have to sell at that value if they are worth more- you can always hang on to them, negotiate a higher price with the company, or sell them to someone else.
Or, to learn basic physics in a structured and rigorous way, you could take this course (but it's quite expensive): http://www.open.ac.uk/courses/modules/s217
Personally, I believe the best way to learn anything hard is by enrolling in a course. Having some kind of commitment, and looming consequence, forces you to work through the inevitable tough patches. You can also get a lot of help from classmates, and or learn a lot from helping classmates. They can also be a social support network.
Regarding your comment in the thread, you might want to make sure that it is physics that you want to learn. Physics is more the study of how things are, the nature of reality, rather than 'why' reality is a certain way. There are not many satisfying answers to questions like "why does light have wave and particle properties", but this might be semantics. Physics explains a lot about what we observe. I get a lot of pleasure out of knowing why the sky is blue, how a rainbow is formed, etc. My BS in Physics is an excellent foundation for what I do now, which is radar oceanography.
What about physics interests you?
If you have something sensitive like an API key, passwords or proprietary algorithm then it might be worth the while of someone to find it in your code.