It might not be perfect, but that's a possibility. And could can definitely work around your requirements with those.
IMHO you should go with Heroku and ignore anyone who's suggesting dedicated servers, VPSes, AWS, Docker or containers. Every moment you spend maintaining a server or doing devops is wasted because it's time not spent building or marketing your _app_.
New startups' biggest expense is founders' time. It seems a lot of people, even on HN, don't realise it because it's a hidden cost. But if you think that a decent developer is worth at least $50/hr and it might take you an 1hr to set up and 1hr/yr to manage a server (e.g. apply patches, update security) then you're better off not spending those 2hrs and paying an extra $100 hosting your app.
Worrying about the future infrastructure cost is also wrong-headed. It's a kind of premature optimisation. To get the real, expected future cost, the projected infrastructure cost has to be multiplied by the probability that you'll actually get big, which for start-ups, is very low.
If you have to run a dynamic site (less potential headaches if you avoid this), I would try to use something like Heroku. It's easily one of the simplest way to host a robust site that needs to scale without having to spend much time on admin and DevOps.
For the people recommending a VPS, DigitalOcean etc., you're talking about using a huge amount of your own time to make such a setup as robust, easy to use and low maintenance as Heroku. What about backups? Scripting server creation? Adding a load balancer and more servers? Security updates? Server security?
The more parts and scripts you have to put together yourself, the more things that can go wrong and the more time of yours it's going to consume. If you consider how much your own time is worth and how important your startup is to you, trying to save anything in the realm of $10 a month on a core part of your startup doesn't make any sense if this is going to cost you multiple hours of time a month.
The hosting cost may go up quickly, but if your business is successful you can either absorb it, or spend time and money to migrate away. They run on AWS, so picking the same location means you can run mixed infrastructure (part on Heroku, and part on AWS) without a latency hit. Thus, a hybrid configuration is very viable.
Another good VPS option is DigitalOcean, which offers a smaller (and cheaper) plan for $5 / month.
There are also a lot of shared hosting providers out there that will sell you cheaper space, but I would not recommend this for anything non-trivial, as most of the time, you'll be limited to using PHP. Still, if you're looking for the best bang for your buck and you're willing to settle for shared hosting, check out Nearly Free Speech -- they are head and shoulders above any other shared hosting provider that I have ever tried.
The cost/benefit analysis is ALWAYS positive in favor of Heroku until you hit super massive scale (minimum 2-3 years out for most startups, if ever). It's super easy to use. Their feature set is increasing monthly and they can handle a lot of different types of setups.
Good general advice is this: The simplest solution is often the best, but in some cases that means taking your old desktop pc, install ubuntu, configure your router to publicly share http and https from that computer. In other cases it means using a toolset like Heroku.
Please don't be mad about this, but the way you phrase your question it is very very likely you have so little skill that you don't even know how little. Please consider to pay a freelancer to support you. He likely has more skill and has experienced more "this can never happen in real life" F-Ups than you, and therefore can handle a lot.
currently i'm hosting a golang web + restful api + websocket server + sqlite3 db + redis + nginx all on a single micro AWS server, but my marketing hasn't really started yet, we're talking about <100 hits thus far per day.
 - https://www.digitalocean.com/hatch/
Also do apply for things like BizSparkhttps://bizspark.microsoft.com/
if you have a static marketing page, you can also host it for free ( almost ? ) on https://firebase.google.com/docs/hosting/
Heroku is easiest and relatively cheap until you scale. (Great problem)
Lots of people seem to use AWS. My limited understanding is that it is marginally more difficult to implement than heroku.
You could also go with someone like Linode. I would only go that route if you have implemented before. There is a learning curve and if you are trying to get the site up quick, I would go with a different option.
Full disclosure: I work on Google Cloud, but it's unclear you need a cloud provider.
Personally, for almost any product I start here. Even if you do need server-side infrastructure for the product, hosting all your marketing pages on GH pages is probably the right choice - they're going to be better at reliably hosting and serving static content than you are. Focus on your product instead.
When I do need server-side logic I then usually go for Digital Ocean, because they're very cheap, pretty great, and far less complicated to manage than EC2. It's also pretty easy to set up Dokku: https://medium.com/@pimterry/host-your-node-app-on-dokku-dig.... With that on top you then get a quick & effective Heroku-style deployment experience, at a fraction of the price.
At https://mnx.io (my company) we offer various options with reliability, and performance at our foundation.
Edit: a bunch of downvotes for trying to be helpful, how nice.
Reliable: AWS / Rackspace / DigitalOcean / Google cloud / basically any famous one.
When you're starting, it's probably better to rent a cheap VPS server. If you start growing fast, you can always move to the cloud. But modern cheap VPSs are quite powerful. I have 7 websites running on one that costs me $6/month.
* rsyncs the directories containing the files you want to back up
* mysqldumps/pg_dumps your databases
* zips/gzips everything up into a dated archive file
* deletes the oldest backup (the one with X days ago's date)
Put this program on a VPS at a different provider, on a spare computer in your house, or both. Create a cron job that runs it every night. Run it manually once or twice, then actually restore your backups somewhere to ensure you've made them correctly.
We basically create a backup folder (our assets and MySQL Dump, then rsync it to rsync.net). Our source code is already on git, so basically backuped on Github, and all developers computer.
On top of it, rsynch has a very clear and simple documentation to implement it very quickly with any Linux distrib.
I use tarsnap, as many others in this thread have shared. I also have the Digital Ocean backups option enabled, but I don't necessarily trust it. For the handful of servers I run, the small cost is worth it. Tarsnap is incredibly cheap if most of your data doesn't change from day to day.
My main site runs a complex series of workers, CGI-scripts, and deamons. I can deploy them from scratch onto a remote node via fabric & ansible.
That means that I don't need to backup the whole server "/" (although I do!). If I can setup a new instance immediately the only data that needs to be backed up is the contents of some databases, and to do that I run an offsite backup once an hour.
For database, I use a second VPS running as a read only slave. A script runs daily to create database backups on the VPS.
Collect your files, rsync/scp/sftp them over.
Read only snapshots on the rsync.net side means even an attacker can't just delete all your previous backups.
For a database driven dynamic site or a site with content uploads you can also use your version control via cron job to upload that content. Have the database journal out the tables you need to backup before syncing to your DVCS host over choice.
If you're looking for a backup service to manage multiple servers with reporting, encryption, dedupelication, etc. I'd love your feedback on our server product: https://www.jungledisk.com/products/server (starts at $5 per month).
I can't praise restic enough. It's fast, secure, easy to use and set up (golang) and the developer(s) are awesome!
Lots of people only do a full test of their backup solution when first installing it. Without constant validation of the backup->restore pipeline, it is easy to get into a bad situation and not realize it until it is too late.
OVH has a backup by FTP premium service but the FTP server is accessible only by the VPS it backups. Pretty useless because in my experience if an OVH VPS fails the technical support has never been able to take it back online.
Make sure you check the status of backups, I send journald and syslog stuff to papertrail and have email alerts on failures.
I manually verify the back-ups at least once a year, typically on World Back-up Day 
 https://papertrailapp.com/ http://www.worldbackupday.com/en/
Then the script sends it to s3 using aws s3 sync. If versioning is enabled you get versioning applied for free and can ship your actual data and webdocs type stuff up extremely fast and it's browsable via the console or tools. Set a retention policy how you desire. Industry's best durability, nearly the cheapest too.
I just use a simple scheduled AWS lambda to PUT to the redeploy webhook URL.
I use an IAM role with put-only permissions to a certain bucket. Then, if your box is compromised, the backups cannot be deleted or read. S3 can also be setup to automatically remove files older than X days... Also very useful.
Stupid simple and stupid cheap. Install, select directories you want backed up, set it and forget it.
All for $7.00 a month.
Use pg_dump and tar then just s3cp
All the databases and other data are backed up to s3. For mysql, we use the python mysql-to-s3 backup scripts.
But the machines themselves are "backed up" by virtue of being able to be rebuilt with saltstack. We verify through nightly builds that we can bring a fresh instance up, with the latest dataset restored from s3, from scratch.
This makes it simple for us to switch providers, and can run our "production" instances locally on virtual machines running the exact same version of CentOS or FreeBSD we use in production.
If you're not using a modern Unix variant with ZFS... well there isn't a good reason why you would be.
You can also use https://r1softstorage.com/ and receive storage + R1soft license (block based incremental backups) -- or just purchase the $5/month license from them and use storage where you want.
They'll give you all of that.
He may write programs on paper, and send them to you to type them in, compile them, and print out a listing with the errors. You then send back the listing, and he will correct his program and repeat.
He'll become a great programmer, since he will have to be extra careful to avoid losing one week on some typo.
Now, it's been a few years since gcc has been able to produce a real listing of the compiled source. You would have to write some script to combine the error output with the source file to produce a classic listing. Similarly for other common modern programming language implementations.
On the other hand, without direct access to a computer, he would not attempt to write any interactive or GUI application, only batch programs, unless the interaction is performed only by an external tester for him.
Another idea: some progress has been made on optical character recognition, so if he can write well enough, it may be possible that you may be able to scan his written programs, and convert them to source file easily, without having to transcribe them. So the process could be smooth enough.
If writing ustensils include typewriter, then even better for the OCR!
Also the following books, which I've copied and pasted from somewhere, to learn theory:
Mano, M.Digital Design, 3rd ed.Prentice Hall, 2002
Mano, M and Kime, CLogic and Computer Design Fundamentals, 2nd edPrentice Hall, 2001
Gajski, DPrinciples of Digital DesignPrentice Hall, 1997
Tanenbaum, AStructured Computer Organization, 5th edPrentice Hall, 2006
Patt, Y and Patel, SIntroduction to Computing Systems: From Bits and Gates to C and Beyond, 2nd ed.McGraw Hill, 2004
Null, L and Lobur, JThe Essentials of Computer Organization and Architecture, 2nd edJones and Bartlett Publishers, 2006
While I was stuck in school and did not have access to a computer, I wanted to challenge myself during classes. The most interesting distraction by far was to play around with the programming functions of my TI-82 calculator that was required for math classes. Even with almost no idea about programming I could soon do interesting things with it, because it is programmed using a version of BASIC. In the end I even created a clone of snake. It worked, but moving one block ahead would take 2 seconds.
I'd recommend O'Reilly's Head First books. Even if they're a few years old, really doesn't matter, given the situation. I think Sandi Metz's Practical Objected Oriented Design in Ruby is great - she does an awesome job of explaining OO principles even if you don't end up writing Ruby. The Manga Guide to Databases is another good read that explains concepts well.
I'd also consider a book that shows a quick way to build web apps, like Agile Development in Rails or maybe a book on ColdFusion. Without the ability to write and run code, it can help plant seeds for those "aha!" moments for understanding the code -> web request lifecycle without getting bogged down in ceremony.
In Texas, the books had to come from a bona fide bookseller, so don't go to B&N and try to mail the books yourself.
This will be much more productive than trying to learn to write code from scratch while also learning a language and learning how to execute the code with pencil and paper.
I would start by going through the exercise yourself: pick out a book and use one of the first sample programs, and set up a "debugger" on a pad of paper.
I used to do this kind of debugging myself: when I first learned BASIC back around 1969, I spent some time in my grandmother's basement with two pads of paper, one with my code and one for the debugger. The debugger pad had columns across the top:
Line number One variable Another variable Another one
After going through this exercise with one program, send your friend the "debugger" pad along with the book, so he has a place to start with this idea. He can then go through the same example and follow along with your debugging steps.
That way he has a solid place to start when exploring the other sample programs in the book.
Please feel free to email me if you'd like to kick this idea around - address is in my profile. And I strongly suspect that everyone else in this thread would be happy to extend you the same offer.
I also heartily endorse the suggestion to read Charles Petzold's _Code_. It's a wonderful book!
This does not give any experience in debugging, which is not taught in books, AFAIK. I am not sure what to do about that...
-- If he'll be in for a year or two with essentially zero access (no computer inside, no computer buddy outside), he should learn something related to programming (math, web design with CSS, etc.), basically re-ordering a typical multi-year learning sequence to put the coding later
-- If he'll be in for ten or more years, he should learn something else. His learning will be so slow and the field changes so quickly that he might learn a few timeless fundamentals, but that's all. He could accomplish much more in some other challenging field that didn't require tools he wouldn't have (ex: math, physics, accounting, ...)
-- If he'll be in for less than five years with access to a computer (via friend outside, for example) every couple of weeks, it could work. It would be like my situation when I was a kid and kids didn't have computers (but I was able to sneak some access). I would do it differently now from what I did then. I would read programming books and get my hands on lots of small example programs. You read the lesson, do the exercise on paper, run it on paper, and only when you are SURE it works (or you're SURE you don't know how to make it work), you read the "answer" (code written by a pro) and study it. Use worked examples as feedback when you can't get it from an actual computer. As you do this, write simple things and send them to the partner on the outside as you continue to work examples on the inside. The turnaround time won't delay you as much if you have other things to do while you wait.
Now, take his real situation, consider the above scenarios, and craft one that will work for him.
Also, you should give him realistic expectations. Learning to code isn't the panacea that many think it is. There are many broke but talented programmers out there, and most don't have the extra baggage associated with a felony conviction. If he doesn't truly have a passion to create software, and is just looking for a way to make money, there are more efficient things he can learn about - like the psychology behind viral marketing (The Tipping Point by Malcom Gladwell and Purple Cow by Seth Godin might be good for example). I know someone that couldn't write a line of code to save his life, but makes 6 figures per month creating Facebook pages around ridiculous topics and using them to drive traffic to affiliate offers and his own Adsense pages. Your friend can always hire coders when needed if creating software isn't what he actually wants to do.
Those are topics that one could make progress on with only a pencil, paper, and the occasional phone call to a mentor.
CS Unplugged: Computer Science without a computer and Nine Algorithms That Changed the Future: The Ingenious Ideas That Drive Today's Computers. I've also posed a problem for him to ponder:
"You have five fingers on your hand (usually -- a few people have more, many have fewer). Each finger can be either extended, or curled up. So a fist would be all fingers curled up, a high-five would be all fingers extended, and many other combinations exist (including the obscene middle-finger gesture, and probably a whole lot of gang signs). What is the total number of possible combinations that can be produced using five fingers? Can you do them all? What is the total number of possible combinations that can be produced using ten fingers? Can you figure out a pattern so that you could calculate how many possible combinations there would be if you had 16 fingers?"
Apart from that... reading books and solving programming puzzles might be a good way. Something that has a feedback loop, which you won't have in the normal way without a computer at hand.
I must take my hat off for this kind of determination! I hope it provides your friend with a way out and they have a better life ahead of them.
1) Edovo is a tablet learning solution that is in many jails (https://edovo.com/)
2) Another group The Last Mile, while they got their start in San Quentin, is working to bring their program/model to more prisons. https://thelastmile.org/
Regardless, I would encourage reaching out to either program to explore their options further. The people behind each are incredibly helpful and may be able to assist you with additional details.
It is aimed at school children, but it's a place to start.
But I feel like I saw an actual curriculum without a computer recently, but now I can't remember what it was, curious to see if it shows up in this thread. Great idea for the incarcerated! I'm going to see if I can figure out what I'm thinking of.
Ah, I think I was thinking of the CS Unplugged that others have mentioned, sweet!
Thanks for this post, I think I'm going to buy a few copies of Little Schemer and CS Unplugged and ship them directly to a Books to Prisoners program I know that sends books to prisoners in response to topical requests.
I recommend C++ as it is useful for a LOT of different types of electronics, embedded, pc, servers, you name it.
Also UNIX scripting is very useful.
Then he should write very small programs that he can use to build into little functions for larger ones. Something like adding two numbers at first, really simple, like almost blindingly simple, just to get comfortable with the architecture of the language.
Then write something that is more complex, something like how to make a little calculator that does all sorts of functions.
He'll need at least one reference book (which I heard you said he has, but you didn't specify what type of book, so look into it... it's a bit of a tedious process to get decent textbooks into the squares, but if you buy it new and send it to them FROM THE PUBLISHER, he can get it, you probably know this, but someone else might be reading and they might wanna help someone learn as well, so they need to know)
Additional texts of note:
Math books, especially linear algebra
Wireless Communications / Bluetooth
That'll last him at least a couple of years to really master. Beyond that, he needs to get a system of writing so that he's not having to use English constantly, as it will take a ton of time. I've seen people use something akin to semaphore, but it's not _extremely_ important unless he's older, and has used his hands a lot. Cramping sucks, and losing your ability to write is nicht gut.
Alright well, I hope this helps. Best of luck to your friend, and if he mentions a thank you, please tell him he's welcome.
When they're out the hard working ones will have programming skills which will help with the job hunt.
With music, we are taught to read before we write.
With programming, we start out writing.
This seems like a great chance for your friend to try out the music learning approach. Send them books of excellently written programs, and allow them to read before they write.
[As a side note: What is their goal? To program to become a software engineer? To program to build web applications for fun? To program to learn how to build products to produce a profit for themselves? The goals will inform the process.]
Understanding how variables, loops, stacks and so on work was all done by writing the algorithms, and our first contact with a computer was in order to write some assembly code, after something like 2 months.
That's not ideal but you can already learn a lot without actually writing code to a computer.
Having access to a programmable calculator or even better to a smartphone would obviously be better.
Would he be able to get some kind of no-name android portable media player and write code on that ?
A simple google search leads me to QPython, I am sure there are tons of other IDEs running on Android. That might be the best option if he has access to such a device.
One of the key things to also understand here is - what is missed out in this type of training. Tools. Tools. Tools.
As developers we have come far away from limited IDEs. We rely on so many tools that knowing-they-exist or sometimes mastering them is difference between good-or-bad devs. I would recommend to read printed material about IDEs, screen shots of tools.
Couple of other things I have found really helpful:* I had underestimated Medium as a platform to rely for tech news till lately. There is so much of latest developer/platform news and articles. Print outs of these definitely help. * Stackshare posts (http://stackshare.io/featured-posts) on what stacks/tools companies use (and how) are eye opening to say the least. Print outs of this.
You can draw a program on paper and follow it with a finger to "run" it. With a bit of practise, it'll be possible to run such mental models without even writing them down. At that point you're thinking like a programmer.
This skill is transferrable to any programming language.
I have used this to introduce my son to the basics - and call it "post-it" programming. We built a few obstacle courses around the house. The most advanced we got was to "unload the dish washer", that resulted in him "inventing" functions.
It typically works better when some one else "executes" the program, since bugs are easier to surface and debugging is a lot more fun.
That said, my son has since learnt to read and write. There is greater enthusiasm to "type" on a computer than use post-it notes.
Hopefully this can be adapted to your friend's circumstance. Best wishes to him.
Would help if you shared the end goal. Get hired anywhere? Get hired by Top 4 Tech Company or Hot Startup of the Year? Start a business? Don't get bored? How long is he going to be incarcerated?
I would greatly appreciate if you shared your experience.
Otherwise I would suggest combining CS with more applied programming with smaller scope (like a web stack), developer methodologies (designing, methodology, testing) or design (interaction, interfaces, experience). Those would be things that he could more easily be practice as he gets out, aren't as focused on credentials and would more likely land him some sort of job.
CS theory probably makes a good starting point, as a lot of it doesn't require actual coding, but still lays a solid foundation for future work. I would recommend SICP (Structure and Interpretation of Computer Programs, by Abelson and Sussman) as a good starting point. It uses Scheme, which isn't exactly a language he's likely to end up working in, but it will teach him a whole lot about thinking like a programmer.
He can learn the algorithms and apply them to the cards in order to check his understanding. He just needs to make sure that he acts like a computer would - only ever comparing two cards at once.
He can simulate this by having all cards placed face down apart from the two that he's currently doing the comparisons with. At the end he can flip all the cards over to make sure he got the intended result.
I'm sure by doing this he could learn all sorts of algorithms this way, and learn to code in the same way.
He may not have a computer, but don't they say that the greatest computers are the ones in our heads?! He just needs to dumb it down a bit for the sake of the exercise.
My first thoughts:
- iterate more quickly by experimenting with non-computer users who aren't in prison, as letters/email to a prisoner will have a slower feedback loop
- learn what people consider to be more fun, and and try to structure lessons within that
- see if there are some existing resources that are close to, but not exactly like, programming without a computer
- set up an open source curriculum on GitHub, so people besides yourself can contribute
OK, I guess I'll also mention Hillis's The Pattern on the Stone, which I feel has mostly been superseded by Petzold's Code. It's less technical and less detailed than Code and would be a much quicker read, where Code gives a more detailed understanding of these ideas.
One thing that did help me a lot when I didn't have computer or fast internet connection, were: the computing and programming paper magazines.
Maybe you can research for your friend programming magazines (on paper) which are available nowadays; and he can subscribe to them. Maybe he can even redistribute or perform as internal reseller once done with the chapters.
They use to treat diverse topics on monthly steps, and is a convenient way to assimilate knowledge. Ones are better than others and introduce less partial views... you must view on your own.
I can't help, because I'm many years without buying one.
It is very much an introductory text to programming, something that can be picked by someone who has an inclination to the craft but with no prior experience. It doesn't even get into Haskell's powerful type system and sticks to primitives and lists. The intention is to teach the building blocks of programming through small, pure functions.
The text is very conversational, chapters are short and sweet, and have a lot of bite-sized exercises along with their answers which will greatly help a self-learner. It will also be easy to evaluate since functional code don't tend to get very verbose.
I'd also learn SICP: https://www.amazon.com/Structure-Interpretation-Computer-Pro...
and algorithms from either CLRS https://www.amazon.com/Introduction-Algorithms-3rd-MIT-Press... or Skiena Algorithm Design https://www.amazon.com/Algorithm-Design-Manual-Steven-Skiena...
Suggestions for absolutely no computers:
* CLRS, the classic. (I just skimmed the intro, though, and if he has no background in uni-level maths, it might be a little tough to digest.)
* (maybe) the Head First series (as someone else suggested). I'm wary of suggesting it not just because I have no experience with the books (I only even mention it because I know they're ubiquitous), but also because bad habits are formed early, and this could do that.
* Patterson and Hennessy - Computer Organization and Design (5d.)
* Sebesta - Concepts of Programming Languages (11d.) (but only after finishing some of CLRS, and even then I don't know how appropriate this is)
What kind of experience did he have with computers before he went in?
Depending, you may be able to make recommendations about stuff relevant to what he's used.
Can you get him something like a TI-84? Because even that will at least allow him to go in and write TI-BASIC.
But like others in this post I would recommend CS unplugged.
And depending on how long he is in there for he might want to look at:
How to Design Programs - This is a good book, and although it's in Scheme, it teaches how to create appropriate levels of abstraction, which seems to be something many programmers struggle with.
Concepts, Techniques & Models of Computer Programs - Discusses the different paradigms and how they are inter-related.
Also something a bit more vocational like The Pragmatic Programmer or Clean Code / Clean Coder probably wouldn't hurt either.
If he can read all of those he will be very well prepared to do some actual programming when he gets out.
SICP not a bad shout either, although I've not got past the first chapter.
There is a lot to be learned from writing code as it forces you to make decisions. This can be done in part on paper and in batch programming mode. There is also a lot to be learned from reading not just snippets and algorithms but from studying complete works. Software is a lot about architecture and integration. A stack of printed code and a #2 pencil is all it takes.
I was driven by courisity, no pressure of completion and had all the time in the world. The book was thick with complete programs with outputs instead of snippets. Book also had list of all core packages, class and their members. It helped to grasp the core libs before hand.
I would suggest a comphrensive book. I have not checked any Osborne reference series since then, but check if there are similar ones for python.
I'll definitely take a look at some of the languages mentioned in this thread that are made to be done on paper. Sounds like a great exercise.
I'd then suggest moving to something like SICP and/or NANDtoTetris.
If you learn the abstract fundamentals first, you will understand how they apply in every increasingly complex system you encounter... and none of that is syntax or frameworks but instead an ability to see and extract the underlying problem domain, which will then guide you in the solution.
Most (all?) CS students learn this early on in university anyways, so it's natural to study if your friend is interested in computer science.
He can also spend the time to master math, especially linear algebra. Getting a firm understanding on math never hurt any budding programmers and opens a ton of doors.
* Once released, he can play with different DSs and experience their asymptotic performances for himself.
It might be a good place to start, at the very least. But it will only appeal to a certain sort of person.
Then buy him a RasPi (+with instal guide).
The way of thinking that such a text gives is nearly identical to the thinking needed for coding.
Just one example: We coders sometimes forget that a conditional like "if (not (A and B)) or C then..." is utterly incomprehensible to the bulk of humanity. Go through a logic book and that stuff will be second nature.
Also it helps lifelong with clarity of thinking which is nice too.
So definitely possible.
Gary William Flake: Computational Beauty of Nature
Douglas Hofstadter: Godel Escher Bach
They won't make you a programmer ready for a job at Facebook; but they will entertain the part of your head that makes you a good programmer.
The two books are also very well written and quite entertaining which give you the motivation you miss if you cannot try things out on your own.
Other than that: Study math at any level.
There are plenty of algorithms you can learn without a computer too, and carry out on paper.
I have no idea what kind of things are allowed in prisons - would a microcontroller running a simple interpreter coupled with a small LCD and keypad be allowed? If so, something like that would be really great for applying programming concepts.
We used to frequently emulate a machine by hand on paper I think it was 16-bit but it might have been even smaller (not touched it since my first year of undergrad) and you could/can write a lot of cool programs for it.
the HEAD First book series,they have fill in the blanks programming exercises.
The best thing I found http://csunplugged.org/
Is he in state or federal prison? Are there no classes available that could give him access to a computer?
He needs to find interesting things around him, and just make plans. Write it down. Without a computer he can use a paper and pencil.
I'm 'fighting' ('working' is a better definition) for civil rights in my city, so I think I will be incarcerated in the future...
I think I will organize a 'paper' version of Scratch, with me as an interpreter of lines of code.
edit: I'll miss Stallman's videos...
You don't need to have a computer (Von-Neumann et al didn't have one!) to invent a brilliant algorithm.
We'd go line by line and change the relevant registers, arrays, pointers, counters, etc. Exams consisted of doing that, too. Sometimes you're given a piece of code and asked about the state at a certain break point. Sometimes you're given a succession of register values an asked what the program is doing. A missing semicolon had a direct influence on your grade, not on stdout.
It's not guaranteed that it produces excellent programmers, but one can learn a lot and it was almost a meditation to focus like that and ask yourself "Why isn't it running?". It was cool (at least for me, I disassembled programs as a teenager and I had a computer, but I still think this was useful).
At which point the possibilities expand ...
So what books do I have?
Books on usability and web accessibility are good reads, however no obvious title springs to mind ('Don't Make Me Think!' would last your friend all of a morning).
One thing though, chess. Chess is played in prisons and some prisoners get rather good at it. Maybe encourage your friend to form a chess league if there isn't one already. Perhaps get him a really good book on chess that can be used by this chess league to be.
Print out the better ones.
Get him familiar with the lingo.
My biggest stumbling block was learning the ever changing language of all aspects of computing.
Then buy him Learn to Program by Chris Pine. I would also want him very comfortable with UNIX, and the command line.
When he gets out,if he has some support; he will do just fine.
I would probably recommend studying individual classes of algorithms, and to only move on when you feel ready, as opposed to learning algorithms in ascending difficulty (at the risk of learning them in a haphazard fashion).
VisuAlgo is another cool site that has lots of algorithm visualizations...http://visualgo.net
And, if you can handle the dude's voice, I recommend checking out Xoax.net's algorithm videos...http://xoax.net/comp_sci/crs/algorithms/index.php
What you will probably find is that it's more valuable to gain experience designing your own algorithms using tried-and-true techniques such as dynamic programming, greediness, divide-and-conqur, linear programming, etc. Also keep in mind that data structures are closely linked to algorithms, and vice versa. If you are not familiar with big-O notation I suggest you begin there as it can be used as a measure of both an algorithm's time complexity and its data complexity.
You can't. You may be able to consume the knowledge underpinning an algorithm and parrot it back but any attempt to learn it in one day is doomed to failure. Parrot knowledge has zero retention.
I guess you can also try your hand at CodinGame's puzzles ( https://www.codingame.com/training ) as they also involve known algorithms and they are realy fun to play.
But ultimately, both of these resources won't teach you how to implement algorithms.
Make something to solve a real problem every day of your life and you'll be far better at solving problems then other people. I'd rather be able to do that then just parrot back sorts, graph traversals, and what not.
The problems range in difficulty and for many the experience is inductive chain learning. That is, by solving one problem it will expose you to a new concept that allows you to undertake a previously inaccessible problem. So the determined participant will slowly but surely work his/her way through every problem.
Pretty much in the beginning of translation to English, but the original resource in Russian is a trove of information on algorithms. Suits well for the "one also a day" learning format.
Jeff Atwood aka CodingHorror (of Stackoverflow and Discourse fame) recommended this book strongly in this post titled "Practicing the Fundamentals: The New Turing Omnibus": https://blog.codinghorror.com/practicing-the-fundamentals-th...
It's old but concise and very much to the point. All of the material is highly practical.
 http://algorithm.wiki/ https://news.ycombinator.com/item?id=12670674
Would love to hear if this is helpful to you.
I have to question the value of only focusing on learning algorithms and on the idea of optimizing the quantity.
In terms of learning lots of them, it might be more useful to focus on learning more fundamental algorithms _better_ rather than tons of them. Or you might want to carefully select the most generally useful algorithms or ones in a specific field relevant to current projects.
Also, now that we have such powerful general purpose languages and efficient module versioning and distribution, learning to take advantage of those probably has more practical use.
For example, you could spend several weeks or years learning various statistical methods and algorithms for machine learning in a particular area. But then you realize that all of the algorithms are already implemented in python code libraries so you start learning how to apply the libraries in real code for applications rather than reimplementing the libraries.
But then you find out that deep learning techniques far outperform all of those algorithms you learned to implement and then apply via those libraries.
So then you train yourself on sophisticated deep learning techniques and start to implement LSTM in python. Then you realize you never quite got the fundamental understanding of neural networks so go back to work on learning that better.
Then you implement some core neural network algorithms in python and start to build back up to your LSTM implementation. Now you find out that TensorFlow exists but lacks good support for AMD which your university has (perhaps erroneously) made a large investment in.
So then you decide the best thing to do would actually be to try to fix some basic bugs that occur on your platform with the latest TensorFlow/OpenCl/AMD code (or whatever).
You manage to fix one of the minor issues and now several geniuses have their day improved by a bit or two.
The point is, trying to learn a ton of random algorithms in a short period probably isn't the best use of your time.
If you are just learning programming, plan on taking your time with the algorithms but practice coding every day. Find a fun project to attempt that is within your level of skill.
If you are a strong programmer in one language, find a book of algorithms using that language (some of the suggestions here in these comments are excellent). I list some of the books I like at the end of this comment.
If you are an experienced programmer, one algorithm per day is roughly doable. Especially so, because you are trying to learn one algorithm per day, not produce working, production level code for each algorithm each day.
Some algorithms are really families of algorithms and can take more than a day of study, hash based look up tables come to mind. First there are the hash functions themselves. That would be day one. Next there are several alternatives for storing entries in the hash table, e.g. open addressing vs chaining, days two and three. Then there are methods for handling collisions, linear probing, secondary hashing, etc.; that's day four. Finally there are important variations, perfect hashing, cuckoo hashing, robin hood hashing, and so forth; maybe another 5 days. Some languages are less appropriate for playing around and can make working with algorithms more difficult, instead of a couple of weeks this could easily take twice as long. After learning other methods of implementing fast lookups, its time to come back to hashing and understand when its appropriate and when alternatives are better and to understand how to combine methods for more sophisticated lookup methods.
I think you will be best served by modifying your goal a bit and saying that you will work on learning about algorithms every day and cover all of the material in a typical undergraduate course on the subject. It really is a fun branch of Computer Science.
A great starting point is Sedgewick's book/course, Algorithms . For more depth and theory try , Cormen and Leiserson's excellent Introduction to Algorithms. Alternatively the theory is also covered by another book by Sedgewick, An Introduction to the Analysis of Algorithms . A classic reference that goes far beyond these other books is of course Knuth , suitable for serious students of Computer Science less so as a book of recipes.
After these basics, there are books useful for special circumstances. If your goal is to be broadly and deeply familiar with Algorithms you will need to cover quite a bit of additional material.
Numerical methods -- Numerical Recipes 3rd Edition: The Art of Scientific Computing by Tuekolsky and Vetterling. I love this book. 
Randomized algorithms -- Randomized Algorithms by Motwani and Raghavan. , Probability and Computing: Randomized Algorithms and Probabilistic Analysis by Michael Mitzenmacher, 
Hard problems (like NP) -- Approximation Algorithms by Vazirani . How to Solve It: Modern Heuristics by Michalewicz and Fogel. 
Data structures -- Advanced Data Structures by Brass. 
Functional programming -- Pearls of Functional Algorithm Design by Bird  and Purely Functional Data Structures by Okasaki .
Bit twiddling -- Hacker's Delight by Warren .
Distributed and parallel programming -- this material gets very hard so perhaps Distributed Algorithms by Lynch .
Machine learning and AI related algorithms -- Bishop's Pattern Recognition and Machine Learning  and Norvig's Artificial Intelligence: A Modern Approach 
These books will cover most of what a Ph.D. in CS might be expected to understand about algorithms. It will take years of study to work though all of them. After that, you will be reading about algorithms in journal publications (ACM and IEEE memberships are useful). For example, a recent, practical, and important development in hashing methods is called cuckoo hashing, and I don't believe that it appears in any of the books I've listed.
 Sedgewick, Algorithms, 2015. https://www.amazon.com/Algorithms-Fourth-Deluxe-24-Part-Lect...
 Cormen, et al., Introduction to Algorithms, 2009. https://www.amazon.com/s/ref=nb_sb_ss_i_1_15?url=search-alia...
 Sedgewick, An Introduction to the Analysis of Algorithms, 2013. https://www.amazon.com/Introduction-Analysis-Algorithms-2nd/...
 Knuth, The Art of Computer Programming, 2011. https://www.amazon.com/Computer-Programming-Volumes-1-4A-Box...
 Tuekolsky and Vetterling, Numerical Recipes 3rd Edition: The Art of Scientific Computing, 2007. https://www.amazon.com/Numerical-Recipes-3rd-Scientific-Comp...
 Vazirani, https://www.amazon.com/Approximation-Algorithms-Vijay-V-Vazi...
 Michalewicz and Fogel, https://www.amazon.com/How-Solve-Heuristics-Zbigniew-Michale...
 Brass, https://www.amazon.com/Advanced-Data-Structures-Peter-Brass/...
 Bird, https://www.amazon.com/Pearls-Functional-Algorithm-Design-Ri...
 Okasaki, https://www.amazon.com/Purely-Functional-Structures-Chris-Ok...
 Warren, https://www.amazon.com/Hackers-Delight-2nd-Henry-Warren/dp/0...
 Lynch, https://www.amazon.com/Distributed-Algorithms-Kaufmann-Manag...
 Bishop, https://www.amazon.com/Pattern-Recognition-Learning-Informat...
 Norvig, https://www.amazon.com/Artificial-Intelligence-Modern-Approa...
Why do I need a 'stack' for a personal project ? Also, a weekend-or-two to set-up ?!? If it takes longer than 30 minutes to get going, it's not going to happen.
Or if I don't need anything dynamic, Hakyll (Pandoc integrated!), and GitLab Pages (automatic CI deploy via any docker instance from git push).
In general pick the tools you're better at.
My feedback. Ok, I can search for stock photos. But can't I already do that? There are lots of stock photo searches. But this one uses AI. So what?
Ok, let's see how your solution is better than anybody else. Oh, I can't you want my email, and I'm not really that bothered.
I'm guessing the bounce rate is like 99% right now.
If I were you, I would just let people access it if they came from HN referer
If you give us a demo page to try without signing up (at a private URL and with a clear time limit if you want), you are going to get a lot more feedback. Or at least show what we are going to get inside. And don't ask for a twitter account during signup.
1. change the title, it's still "My ASP.NET Application"\
2. It works OK (searching for 'pizza' shows some photos) and the design is pretty nice. I think you could improve it by reducing the number of different fonts you're using.
But none of this is actually going to teach you the skill of inquiry and skeptically reading different competing historical narratives. You kinda do need a class for that. A friend of mine is building a startup to make running one easier: https://www.beaglelearning.com/
 https://www.youtube.com/watch?v=Yocja_N5s1I&list=PLBDA2E52FB... , https://www.youtube.com/playlist?list=PL8dPuuaLjXtMwmepBjTSG... , and https://www.youtube.com/playlist?list=PL8dPuuaLjXtPNZwz5_o_5... https://www.youtube.com/watch?v=EbBHk_zLTmY&index=1&list=PLh...  https://www.youtube.com/playlist?list=PLB2vhKMBjSxMK8YelHj6V...
The advantages of meeting over a coffee are that it is quick, you're on roughly neutral territory, and there's an opportunity to feel things out enough to decide whether it's worth taking things to the next level both personally and technically.
Being able to concisely describe what you've done in the past, what you'd like to do in future, and why you approached the firm should cover the bulk of the work content. Having an opinion on related technology issues is good, and I usually ask semi-random questions outside of work stuff too, just to get a feel for the person: nothing too controversial, but just conversational. Even if you're interested in a purely technology role, demonstrating that you can talk to strangers doesn't hurt.
It could be a little as 15-20 minutes; it could last for hours. Be ready for either. CTOs are usually very busy people, so get to your points and don't waffle.
Try to pay, but don't insist. Thank the person for their time. Send a followup thank-you email (and do anything else you said you would too).
My side project is: "How to Make an RPG" (http://howtomakeanrpg.com/) which I released in June.
It's a collection of code samples, art and digital book that shows the reader how to make an old-school, Japanese-style RPG. So, it's super niche! I wrote a little about my process here:
There was supposed to be a second part to this article but I haven't written it yet.
It's been over $1000/month very comfortably so far but it is trending down. This isn't uncommon for this type of project - there's often a spike followed by a slow decline.
Still, for the last three months I haven't actively worked on it and it's still sold well. I've moved country and been finding a job (all sorted now), so I haven't had much free time.
I'm not really sure where is good to go after this project. For now I'm building on the base the book introduces, just for fun.
* You do have time. I work a time consuming job, have a wife and kids, and still found 1 hour per day to work on it, and that was enough. * Automate everything that you can. Early on I automated the deployment, the creation of new accounts, the management of the sales, and soon the marketing. * Have a plan and stick to it. I planned to use 1 hour per day and I did. I have a backlog and I work against that always. * Pick a market you understand. I help a lot with my kids schools and this is software to help with that. * Drop bad ideas when needed. I have started more side projects than I can think of. Sometimes in the past I have felt bad because I didn't want to give up on an idea. So I worked on a bad idea for way too long. Don't do that.
It made a few thousand in Amazon referral fees after being at the top of HN, Product Hunt, and Designer News for 4 days. As these traffic spikes wear off, I expect it to continue at at least $1k/mo.
To maximize referral fees, I use this clever service called A-fwd, which geo-redirects visitors to their appropriate Amazon.tld so that they can make a seamless purchase without switching regions. This also allows for my affiliate codes to stay intact, and for me to collect worldwide Amazon affiliate revenue.
I also had to learn the ins and outs of Amazon Associates policies, which are incredibly finicky (no Amazon links in emails, no showing product pricing on your homepage, etc.) and frequently results in unannounced account closure that requires you to pester their support team to get things back online.
It's pretty meta to be posting this here, because Indie Hackers is basically a huge collection of interviews with developers who are making money from their apps and side projects. I only include interviews with people who are willing to share revenue numbers, employee count, etc. There's also a forum/comments section where you can ask your own questions to the interviewees if you find my questions lacking :)
Me and my twin brother have had it as a passive income thingie for years. After a failed attempt at selling it (SaaS metrics are NOT easy) we met a guy who saw some potential and we're finalizing paperwork with our lawyer to create a Swedish limited company right now with him as co-founder. We will try to take the plunge and get it running as a full time company within a couple of years!
Achieving a lifestyle passive income project is surprisingly hard...
...Assuming that I ever finish a side project.
...And that I ever come up with a side project somebody would pay for.
Neither is very likely.
We organize trips around the world for developers, designers, and entrepreneurs who want to work remotely while traveling. People pay us to organize housing, accommodations, and community events wherever we go (past speakers have been CIO of Estonia in Tallin, Matz in Tokyo, etc.).
Happy; to answer questions about running more of an ops business that still is related to tech.
Feem is a great cross-platform way to share files within your LAN.
I started building the app 4 years ago. I put it on Hacker News and it blew up a tiny bit. That was enough to keep it going until now.
There is still a lot of work I can put into it marketing or coding wise. So far, it's been going well ($800ish). I recently rolled out a UI/UX improvement.
Its 4 year anniversary is in 2 days. :)
It was just an Android soundboard app for a very popular TV show in Spain. You could tap a button and it'd play some funny sentence from a character from this show. Long press, you could share that sound.
Revenue model: a little ad bar on the bottom of the screen.
It grew from 60$/month to > 1000$ in around 6 months, only through word of mouth. That lasted another 6 months or so until the show became less trendy.
Probably not very sustainable as I was piggybacking on the popularity of the show, but it taught me that making money was 100% not about writing 'the bestest codes'.
I run http://www.boxfactura.com, an email service for your digital invoices. It has been quite a journey because everyone I speak to has some kind of trouble with their invoices, but they don't know there's a product for that, so first you have to market the idea of it, and then the product.
I created this project for learning purposes and because it was a lot of fun. I open sourced the actual gantt component: https://www.angular-gantt.com
Loads of fun while it lasted! Gave me a nice income bump for 3 holiday seasons.
It's been very good to me, but also trending down as people seem to be diversifying from Meteor. Certainly not what I expected when I got into it.
The story for it is a simple one: I solved some of the annoyances during development for myself with by making a devtool, and then open sourced it.
The reaction was very positive and encouraging. Between the opportunity to make more tools, and the downside of having to maintain them, I decided to create paid tier for the tools.
I guess it's partly because we are used to these pain points for a long period of time we don't feel it as a pain point anymore or even though we have a good idea it's not easy to build it as we need lot of capital to do so.
Also even if we have a good idea monetizing is a whole new ball game altogether. Like the chrome extension I'm hacking together on weekends which allows people to search for restaurants around them. I have no idea how I can monetize it and just build it for the challenge of making it.
I think one option is to keep on making cool things. Do something challenging and keep pushing out new things whenever you can. And finally one will stick. I don't think it's easy but if one keep persistent in shipping new things definitely one will become a success.
Like in a similar post I have made like this in the past I remember one commenting, we as HN users believe that everything that we make should be like Airbnb or Uber due to the illusion of success in many startups. But that is not the case and it all comes down to being persistent and enjoying the journey along the way.
The trick is that after a few times around, the courses require a bit less preparation.
Adjuncting is an absolute nightmare if you are trying to do it as a full-time job. But as a side thing for beer money when there is a staffing need? It's pretty light on stress. Since I am not gunning for tenure track (or even a full time position), there are little to no stakes involved.
Weirdly, I think the folks in my position (teaching as an adjunct as a side gig) along with the tenured full-professors on the opposite end of the academic spectrum are actually very similar in that regard.
The majority of that is from sponsorships for the weekly newsletter, which has almost 13,000 subscribers now. Currently doing cust dev and what not to see if there are income opportunities that don't involve ads.
It was a lot of work, but it's a great passive income now that they're done, and I'm quite proud of how they turned out. The Pluralsight authors are a great professional network to be plugged-in with, and being an author is a pretty unique differentiator on your resume.
I'm going to put together a third course soon.
They're always looking for new authors. https://www.pluralsight.com/teach
The project started because there is always need for documentation for software projects (in my career), and a lot companies are not used to have one. At the same time, I want to learn Scala so I pick up Play! framework to play and build real world app.
Happy to answer any questions!
This year we're launching new features and a simple API: (https://sentopia.net/apidoc/)
We don't just copy-pasta public domain titles. We actually go through it, and create a really nice table of contents, include flourishing images to chapter headings, link any footnotes, and re-typeset so there's pleasant vertical rhythm to the paragraphs. We really pride ourselves on creating a great user experience rivaling titles from major book publishing companies that have delved into the foray of e-book publishing. CSS for e-books is a repeat of browser compatibility problems reminiscent of the 90s unfortunately.
Our average price is usually $0.99. Our genre is theology, so we publish books from Augustine, Thomas Aquinas, and John Calvin to name a few.
We make over $1K/month, but sales are on a downward trend. The hype of e-readers has faded in the past 2 years. It's not that e-reading isn't cool. It totally is. Just like the mp3 player was a great successor to the Walkman. The problem is that there isn't One Great Device for e-reading (like the iPod was).
A review of e-reading devices:
iPad: No person with eyeballs can read on an LCD screen for more than 2hrs, but I can read a physical paper book as long as I want. Dead-on-arrival in my opinion. Sales from this market never overtook sales from the Kindle store for my company.
Kindle: Better than the iPad. That's not saying all that much because they're only better because they use e-ink. That's it. Navigating and whatnot is still really janky. The worst thing about the Kindle is that all text is justified. There aren't any settings to change it to left alignment. It's nuts. You have to see a screenshot of some text to see how absurd this design decision is.
Kobo: These guys make the best e-readers. They are e-ink like Kindle, but they have this revolutionary technology called "left alignment of text" instead of justified-only text on the Kindle. You don't have the sophisticated backend infrastructure like Apple/Amazon for synchronizing your books/bookmarks/highlights/blabla. But it's not that important really. Just sideload your e-books, and dupe your e-book library on your computer. That's an end-to-end backup plan. You may not have heard about Kobo because they don't have the marketing budget like their competitors.
My company is called Fig, because I started the company on Fig St in Escondido, CA while I was in seminary. Here's some of our titles on Amazon: https://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Dd...
Footnote: I probably went too far with this off-handed hardware review, but I'm drinking wine and felt loquacious.
* The signal-to-noise ratio is too low. There are many clever or useless comments that add no value for every one that is worth reading.
* When I read topics I know about, I find the information amateurish or often just wrong. People say things they have no idea about and get voted up, consistently. It seems to be an information bubble of the ignorant, to an extent. Because of that I find little value on topics I already know about, and I don't trust the others. (That may sound harsh but it's my experience, not an exaggeration.)
However, I seldom read it and I know Reddit is vast; I'd be very interested in any sub-Reddits that don't have those problems.
If you like photography, you might enjoy /r/videography and /r/Filmmakers/ and /r/cinematography/ and /r/art.
Of the general interest the cool ones are:
Check out the article below which gives an in-depth interpretation based on their patents and whatever information/demos magic leap has shared in the past.
Magic Leap's CEO also shows the light field photonic chip which looks like a normal piece of glass, but has the property of projecting images from a fiber optic source at various wavelengths.
I am wondering whether the technology developed can be rendered in such a form factor where its very easy to wear like grasses and use in a day to day basis. The guys at Magic leap seem to be very confident that they have got most of the complex pieces figured out and its already materialized. Even a developer kit from magic leap next year or so should blow every ones mind of, if they have got the projection of images directly to the eye working even with a tethered system to start with.
Also read that they are planning to showcase their product sometimes the end of the year and in CES 2017 (http://vrworld.com/2016/04/25/magic-leap-unveil-technology-c...).
Hololens from Microsoft seems to be doing something closely similar where they are projecting images through a glass like medium. Read somewhere that hololens was rushed to be first before Magic leap delivers its technology though. Some recent videos form wired on Magic Leap shows some impressive demos taken through their technology and should have a large FOV as hololens has a very limited FOV it seems. Magic leap's CEO Abovitz seems to be very confident that their tech is way superior to whatever exists and are not worried about some products like hololens hitting the market earlier than their products release.
Some refs on teardown of hololens stuff
Nonetheless, there are still some spots with decent wages like London (particularly strong in fintech, but there's also lots of startups), Ireland (if you prefer to work for a branch of an American big-co), Singapore and Hong Kong if you'd like to change your environment entirely or even Australia. It all depends on your experience and selling skills though, as in most these places outside of US the difference between a senior's and junior's salary might determine your ability to rent a 3-room apartment vs a 100 square feet room in a shared-house with 8 flatmates :)
Most importantly, choose a place that you have a genuine interest towards. The rest doesn't really matter that much. If you pick a crowdy place you'd get a lower life quality in terms of purchasing power and living space, but higher from a cultural/social point of view and more job opportunities as well, so yeah, that's your tradeoff.
I have an American friend who came here to work for Adyen (Amsterdam-based unicorn) and recently bought a house here.
In Euro, London > Berlin > Paris.
After that, I recommend Stanford's CS231n. It's focused on computer vision tasks, but you can learn a lot about neural nets in general from it. The videos were recorded around a year ago I think, so it's up to date with the latest deep learning techniques and libraries. For some reason the videos were taken down from the CS231n site but you can watch them here: https://www.youtube.com/watch?v=g-PvXUjD6qg&list=PLlJy-eBtNF...
For "laughing at ourselves" and oddities of computer languages, there is "Wat" by Gary Bernhardt:https://www.destroyallsoftware.com/talks/wat
For an opinion on the Sun to Oracle transition, there is "Fork Yeah! The Rise and Development of illumos" by Bryan M. Cantrill, Joyent. His Larry Ellison rant makes me smile:https://youtu.be/-zRN7XLCRhc?t=33m00s
Another fantastic one is Steve Jobs' 2005 commencement address at Stanford:
Bryan Cantrill's 2011(?) Lightning talk on ta(1). It's fascinating, but it also shows you just long-lived software can be.
Randall Munroe's Talk on the JoCo cruise. Because it's effing hilarious, and teaches everybody the important art of building a ball pit inside your house.
Finally, an honorable mention to three papers that don't qualify, but which I think you should read anyway.
Reflections on Trusting Trust: This is required reading for... Everybody. It describes a particularly insidious hack, and discusses its ramifications for security.
In the Beginning Was The Command Line: If you want get into interface design, programming, or ever work with computers, this is required. It's a snapshot of the 90's, a discussion of operating systems, corporations, and society as we know it. But more importantly, it's a crash course in abstractions. Before you can contribute to the infinite stack of turtles we programmers work with, you should probably understand why it's there, and what it is.
Finally, The Lambda Papers. If you've ever wondered how abstractions work, and how they're modeled... This won't really tell you, not totally, but they'll give you something cool to think about, and give you the start of an answer.
Growing a Language by Guy Steele.
Really set me on a path of re-examining older ideas (and research papers), for applications that are much more contemporary. Absolute stunner of a talk (and the whole 70's gag was really great).
"What would be really sad is if in 40 years we were still writing code in procedures in text files" :(
"Ask HN: What are your favorite videos relevant to entrepreneurs or startups?" -> https://news.ycombinator.com/item?id=7656003
"Ask HN: Favorite talks [video] on software development?" -> https://news.ycombinator.com/item?id=8105732
The Coming Civil War over General Purpose Computing by Cory Doctorow http://boingboing.net/2012/08/23/civilwar.html
Cybersecurity as Realpolitik by Dan Geer https://www.youtube.com/watch?v=nT-TGvYOBpIhttp://geer.tinho.net/geer.blackhat.6viii14.txt
Discovering Python (David Beazley)
David finds himself in a dark vault, stuck for months sifting through deliberately obfuscated pile of old code and manuals. All seems lost, but then he finds Python on a vanilla Windows box.
Fork Yeah! The Rise and Development of Illumos (Bryan Cantrill)
History of Illumos, SunOS, Solaris, the horribleness of Oracle
These are not technical, but they are entertaining.
We can argue on some of the points he makes but we can all agree that the demos are very impressive.
1) Alan Kay: Is it really "Complex"? Or did we just make it "Complicated"https://www.youtube.com/watch?v=ubaX1Smg6pY
Take note that he is not giving the talk using Window & PowerPoint, or even Linux & OpenOffice. 100% of the software on his laptop are original products of his group. Including the productivity suite, the OS, the compilers and the languages being compiled.
2) Bret Victor: The Future of Programminghttps://www.youtube.com/watch?v=IGMiCo2Ntsc
It's a terrific window into the future of web application development.
Carmack's talk about functional programming and Haskell -- https://www.youtube.com/watch?v=1PhArSujR_A
Jack Diederich's "Stop Writing Classes" -- https://www.youtube.com/watch?v=o9pEzgHorH0
All with a good sense of humor.
It's about much more than games. To me, it's about identifying and not doing unnecessary work.
The second half of this video is a Q&A session, which I would skip.
I love everything about this talk. It walks you through building a lexer from scratch in a simple and elegant way, through a very interesting use of coroutines. I appreciate the bits of humor in the talk as well.
I think it is so easy for us to discuss the impact of big data and quickly get into the weeds, but I think in this talk Norvig does an especially great job in making you truly appreciate the seismic impact that the availability of massive quantities of data can have on your way to think about problems. This is one of the first things I ever saw of him, and I've been in love ever since.
How I met your girlfriend: https://www.youtube.com/watch?v=O5xRRF5GfQs&t=66s
I'd mention Bret Victor's work before (maybe Drawing Dynamic Visualizations?), but Bret cheats by writing a lot of amazing code for each of his talks, and most of the awesome comes from the code, not his (great nonetheless) ability as a speaker.
Then you have John Carmack's QuakeCon keynotes, which are just hours and hours of him talking about things that interest him in random order, and it still beats most well prepared talks because of how good he is at what he does. HN will probably like best the one where he talks about his experiments in VR, a bit before he joined Oculus (stuff like when he tried shining a laser into his eyes to project an image, against the recommendations of... well, everyone): https://www.youtube.com/watch?v=wt-iVFxgFWk
"Writing A Thumb Drive From Scratch" by Travis Goodspeed - https://www.youtube.com/watch?v=D8Im0_KUEf8&nohtml5=False
Excellent talk on the hardware side of security, goes into some really cool theoretical hard disk defense stuff, incredibly insightful and introduces a hardware security tech toy so fun you'll want to go out and order it the moment you're done watching. The speaker is entertaining as all heck to boot.
"Programming and Scaling" by Alan Kay - https://www.youtube.com/watch?v=YyIQKBzIuBY&nohtml5=False
Interesting talk on the theoretical limits of code size and engineering versus tinkering. Also talks a lot about Alan Kay's philosophy of computer science which analogizes systems to biological systems, which are the systems with the largest proven scaling on the planet.
"The Mother Of All Demos" by Douglas Engelbart - https://archive.org/details/XD300-23_68HighlightsAResearchCn...
This talk is so prescient you won't believe your eyes. Given in 1968, Douglas demonstrates just about every major computing concept in use today on a modern machine, along with some ones that are still experimental or unevenly distributed such as smooth remote desktop and collaborative editing.
I especially like the part in the middle where he tells the story of how a an awful GNOME applet was killing a Sun Ray server, and how he tracked down the culprit with DTrace.
not a high tech talk, or particularly technically complex, but it shows a common blindspot in a way that is both clear, enlightening and frightening.
Detailed discussion of how to get the most out of your memory cache and memory bandwidth, focusing on games development. It's full of examples of how understanding both the problem and the hardware, and working in a straightforward way, can give you huge performance gains over using poorly suited abstractions. It shows how low level thinking is still important even with modern compilers. I recommend people interested in performance optimization watch it.
This was the first time I watched pg give a talk. It was the talk that brought about the biggest change in the way I think about the world, my ambitions. The talk was the beginning, reading more about pg, I came across his essays and then HN.
The title says it all. It's really a summary of several software systems with good ideas abound. I believe all the software is 80s or prior.
Edit: I also forgot to mention some psychology and math.
It's what I direct non-technical people to when they ask what the big deal about internet privacy is.
I think this can really really change how we look at everyday programming tasks everywhere from the type of tooling we choose to how we approach problems.
Something more recent:Martin Fowler's great introduction to NoSQL: https://youtu.be/qI_g07C_Q5INot so technical, this is a great overview of the reasons why (and when) NoSQL is valuable. He crams a lot into a short speech, so it's one of the rare videos I've required students in my database classes to watch.
Now, really getting away from the technical, I have to recommend watching the IDEO shopping cart video: https://youtu.be/taJOV-YCieIThis is the classic introduction of Design Thinking to the world, in 1999. If you're using the Lean Startup or an Agile method, but have never heard of IDEO's shopping cart, you may be able to get along fine at work, but you should be kind of embarrassed like a physicist who's never read Newton.
I love his talks for a few reasons:
1. He's anti-hype 2. He's contriversal 3. He's right.
Related slides: http://static.googleusercontent.com/media/research.google.co...
Sussman goes over some interesting ideas on the provenance of calculations and asserts that "exact" computation is possibly not worth the cost.
"What the heck is the event loop anyway?" by Philip Roberts
Great talk about BBC micro and much more
3Matt Adereth - Clojure/typing
History of keyboards and a custom keyboard written in Clojure
I like the 3 for their content and how each speaker presented the background and their project/hack/ideas.
How To Design A Good API and Why it Matters  The Principles of Clean Architecture  The State of the Art in Microservices by Adrian Cockcroft  "The Mess We're In" by Joe Armstrong 
It's mostly about the history of HCI up to that point.
The best practical talk is of course this:
https://www.youtube.com/watch?v=asLUTiJJqdE - Robert "Uncle Bob" Martin, Clean Architecture and Design
Aside from the comedic aspect (which makes the talk incredible), Mickens is a genuinely brilliant thinker and has a marvelous way with words.
Bret Victor - Inventing on Principle
Philip Roberts: What the heck is the event loop anyway? | JSConf EU 2014
InfoSec talk. Best lines from talk..
"Basic lessons are not learned such as know thy network"
"You have to learn your network, you have to have skin in the game"
"Defense is hard, breaking stuff is easy"
"If you serve the God's of compliance you will fail"
"Compliance is not security"
"Perfect solution fallacy"
"People are falling over themselves not to change, shooting great ideas down."
"Perfect attacker fallacy, they don't exist, they are a myth!"
"Attackers are not that good because they don't need to be that good."
Speaker is Eric Conrad
It's fairly high level, but he really burrows into computer history and it's simply fascinating to watch, helped by the fact the person is extremely passionate about what he does https://www.youtube.com/watch?v=gB1vrRFJI1Q&list=PLbBZM9aUMs...
Watching that talk brought me over to the "a picture or a few words per slide" style of presentation, rather than the "wall of bullet points" style. It also helped me move from "stop talking, change slides, start talking again", to smooth transitions while talking.
...very inspiring if you're bored with the way websites have been looking for the past few years.
Explains a lot of recent mass-market innovations that keep the semiconductor manufacturing industry rolling, and goes into detail about the many tricks used to ensure scaling down to the 22nm node.
 https://vimeo.com/36579366 https://www.youtube.com/watch?v=cN_DpYBzKso
Jake Appelbaum's Digital Anti-Repression Workshop is de rigeur listening too:
It's well worth watching if you are interested in vms at all.
The simple and followable progression to more and more complex ideas blows my mind every time.
> Visualizing Algorithms A look at the use of visualization and animation to understand, explain and debug algorithms.
I like how this talk cuts through a lot of the BS in security. One of his points is that the US and other rich Western countries have a lot more to lose from a possible "cyber war" than our potential adversaries do.
Another key point is that we'll never make much progress unless we can somehow start building better systems in the first place, with fewer vulnerabilities for an adversary to exploit.
I think the second point has become a lot more widely accepted in recent years since McGraw started giving this talk. Unfortunately it sounds like a lot of government folks still haven't got the memo on point #1.
Humour, serious technical insight and a good reminder of why being a generalist is an advantage.
Great overview of value types, performance and how hardware that runs things still matters.
Scott Meyers' talks are fun to watch too.
A fascinating tale about using python during the discovery phase of a trial. Very fun watch. Anything by David Beazley is great!
He is kinda awesome in Herzog's recent 'Lo and Behold' too.
If you are in for something out of the ordinary.
I like it because it is the intersection of so many things. He starts slow, is very intimidated by the audience. The audience, obviously super skeptical of the clown from that 70s show giving any useful information, they could learn from. He finds his footing with a great morivational story (albeit laden with a few cliches) about a forgotten entrepreneur and how he built some lasting value.
For me, this is a great talk. The story is extremely motivational and has some interesting bits of history & entrepreneurial genius-- but the entire experience is extremely educational. About bias, drive & success.
I liked it for what it wasnt.
Anything at all by Richard Feynman:-https://www.google.co.uk/search?q=%22richard+feynman%22&tbm=...
The talk is about how Damien quit his job to hack on open source software. It shows his struggle and doubt while embarking on the project and then finally invented CouchDB. It's a passionate and human account of the process of creating something significant. I recommend every hacker watch this.
D10 conference - Steve jobs and Bill gates - https://www.youtube.com/watch?v=Sw8x7ASpRIY
TED talk - Bill gates (Innovation to Zero) - https://www.youtube.com/watch?v=JaF-fq2Zn7I
How Google backs up the internet.
At the time it changed how I thought about backups/reliability.
"The Science of Insecurity" by Meredith L. Patterson and Sergey Gordeychik (2011)
Warning: speaker likes to use profanity (which I enjoy :) but possibly NSFW if you're not on headphones
The rest of his channel is full of his talks https://vimeo.com/channels/761265
One of the best talks about code reviews and similiar things
Guy Steele's How to Think about Parallel Programming: Not! at Strange Loop 2011: https://www.infoq.com/presentations/Thinking-Parallel-Progra...
Any of Jason Scott's talks given at various hacker cons are usually historically informative and always a lot of laughs (but they're decidedly not "technical").
Not a technical deepdive, but entertaining.
"LoneStarRuby 2015 - My Dog Taught Me to Code by Dave Thomas" - https://www.youtube.com/watch?v=yCBUsd52a3s
"GOTO 2015 Agile is Dead Pragmatic Dave Thomas" - https://www.youtube.com/watch?v=a-BOSpxYJ9M
It completely changed the way I approach front-end development (Not that talk in particular though. I saw an earlier, similar talk on Youtube but this one has much higher quality).
It's worth joining a global-scale tech company (AWS, Google, Azure, Facebook) just to have your mind blown by some of the internal materials.
He was a co-speaker at TEDxGlasgow with me and I thought his talk was brilliant. Cyber-crime is a really interesting area.
A deeply thoughtful discussion of the impact of metaphors on how we think about software development.
Skip to 0:40 if you don't want to hear the MC.
For those how likes computer graphics (or want to learn), this is a gold piece.
(Plan to organize and add more categories.)
It completely changed my perspective on how design shapes our world.
This guy is just too funny.
edit: +Ryan Dahl
So many lessons in short, beautiful piece.
Not sure if it's my favorite. And the subject is more technology than "tech". But the talk that keeps haunting me is Michael Dearing's lecture from the Reid Hoffman "Blitzscaling" class at Stanford:
Heroes of Capitalism From Beyond The Grave
Dearing draws upon an obscure letter by Daniel McCallum, superintendant of the New York and Erie Railroad, written to his bosses in the 1850s. In the report, McCallum bemoans the stress and frustration of operating a railroad system spanning thousands of miles. All of the joy and magic he used to revel in whilst running a fifty mile stretch back in his home town has long since dissipated. Furthermore, the unit cost per mile seems to be exploding rather counter-intuitively!
Dearing goes on to elucidate the absolute necessity of the railroads ("the thing to know about the railroads is: they were startups once") themselves. As guarantors of civilization and progress. Beacons bringing light and reason to the dark swamps of ignorance and inhumanity. And not just in the physical transport of goods, people and ideas across the continent. But as the wealth created from that creative destruction remains the best cure for all of our other inimical maladies: poverty, injustice, disease and stagnation.
So, no pressure. But civilization depends upon you!
Links to References in the Talk:
Estimates of World GDP: From One Million BC to the Present
The Process of Creative Destruction by Joseph Schumpeter
The Visible Hand: The Managerial Revolution in American Business by Alfred D. Chandler, Jr.
Report of D. C. McCallum to the stockholders of the New York and Erie Railroad
Things As They Are In America by William Chambers
IMO. All tools are history from a distant past.
There was problem some time ago. Some people picked a tool and it persists. The reasons for a particular tool could have been anything and may or may not still hold true.
Usually the tooling ends up fragmented by team, office locations, external acquisitions... especially when there are multiple similar products available.
The alternative is to have one ruthless dictator who forces the adoption of ONE SINGLE TOOL and kill everything else. That's the only way to get decent tooling and unify it across a company. (Coincidentally, that's also the only way to migrate from a mess of old tools).
Given you are asking on HN, I would guess that you code and are looking to become better at programming problems as well.
If that is the case, check out this resource for programming games, challenges and competitions: https://github.com/dakaraphi/development-resources
Doesn't have to be a complete idea all the time; mainly you need to build yourself hands-on experience of trying to solve a problem, the more you do the more ideas you get as well as the wisdom of why some methods may not work.
Sometimes I think of stupid ideas, but even thought I'm pretty certain it wont work, I will try it out just to see anyway. Many times such attempts leads me to other ideas.
Also if you are stuck, do some research, sometimes you will find a solution, others solutions might lead you to other possible methods. Just keep trying stuff.
- Identify a structure as against finding an idea or solution. Structures help you be through and ensure you are limited to just brain waves
- Solve more problems. Solve a particular problem and then try to see if the solution is scaleable. That will help you improve your structure.
- Read more. Read a lot. Read just about anything. Good editorials can be a master class in problem structuring.
* relate it to other problems you have solved or seen solved
* break the problem down into parts. Some of those parts may be things you have previously solved or have seen solved
* research the problem
* after completing one problem, reflect on it and learn from it
2 good things come out of unit tests:
1. You'll decrease the chances of having to debug that code again2. You'll learn how to write code that needs less debugging.
Now to adress your question directly, I have developed a few techniques of debugging, which come in quite useful.
1. Going directly to the problem. Example 1: you're debugging some database problems -> put a breakpoint in the library that's interfacing with the database. Example 2: Some object has some unexpected property -> put a breakpoint at the point when that property is set. Example 3: you're receiving weird http requests -> put a breakpoint as close as you can to the code giving you the request.
2. Conditional breakpoints. Some IDEs have this feature build in. If not, you can just write code around that. All you have to do is write a conditional statement with the condition you expect, and if it will evaluate to True, put a breakpoint inside this condition - there you have it, simple conditional breakpointing (helps with loops and other scenarios).
3. Write code that minimizes state change. I know I'm being preachy again, but the worst bugs I encountered all revolved around objects being changed by code in extremely unexpected places. Don't do that! Think by default never to modify objects once created, and only stray from this rule when the alternative becomes ridiculous (e.g. when you have to write a lot of really complicated code which nobody will understand)
I use a wide range of techniques from simple printf's all the way to a full-blown methodology that has not failed, especially when dealing with coupled bugs or those caused by concurrency issues, hardware and such.
I wrote about my methodology here: http://ortask.com/wp-content/uploads/fault_localization_impr...
Deeper bugs use the IDE, breakpoints and debugger, goto definition and call stack examination solve the other 10%
Some tips for production: Put logging calls in at critical points -- e.g. initialisation of interfaces log input and output shapes (I work in mostly in vectors), DEBUG level logging, which is more verbose, can log the shape of incoming vectors to help with sanitation efforts.
If you're using an interpreted language, a REPL is brilliant for debugging individual functions (I use this mostly with Lisp, but also to some extent with Python).
Disclaimer: I'm not a professional dev...
You can see numerous examples ranging from magazines dating back to the 1800's (and before) of all the wacky inventions they pictured denizens of the year 2000 using (rocket packs! nuclear-powered cars! pneumatic transport!), and what life might be like (through the lens of the time). Readerships enjoyed and appreciated reading about the future and giving their imaginations fertile ground to romp.
Futurist was actually a job title.
I think now we're too busy or easily distracted to care much about the possibilities of the distant future. Most of our thoughts on the subject are now doom scenarios involving climate change, collision with an asteroid, running -out- of atmospheric CO2, or the Sun eventually encompassing the Earth.
Then again, maybe there's just a big opening for someone with the right marketing skills to fill an unmet need. I think I could be a futurist.
I was old enough to have been a young teenager when Netscape was released and connected to the web via a BBS (already had Usenet) and Trumpet Winsock. I would say up until 1998 the Internet boom was met with scepticism by the general public. Most people weren't even chatting on AOL. It wasn't until broadband became more commonplace (2000?) that I think the general public became obsessed with the Internet.
As to smartphones the iPhone (specifically the 3G) was the device I had been waiting most of a decade for after seeing my friend's Palm Pilot with Internet access in 1999 or 2000. I'm probably old enough that I discount the "smartphone boom" as I viewed it as the natural progression of existing technology. Also am slightly disappointed that the original premise of the iPhone was web apps on the phone through the browser but that quickly was replaced with native phone apps.
tldr: I think a very small percentage of people are future obsessed about the AI revolution. In the HN echo chamber it might be more but the majority of people don't give it a second thought outside of, "NO SIRI! I SAID WHERE IS..."
I'm not old enough to say but I imagine the magic behind the beginning of space exploration and the race to the moon could have been the peak of future obsession.
This is, of course, the same time period featured in the xkcd titled 'The Pace of Modern Life' , which takes contemporary newspaper quotes lamenting that people are always in a hurry and rarely stop to greet strangers and instead spend their commutes on the trains with their noses buried in newspapers, showing that today's critiques about people lost in their smartphones are more than a century old.
So yeah, I'd say we've always been obsessed with the future.
 https://en.wikipedia.org/wiki/Galerie_des_machines https://en.wikipedia.org/wiki/Galerie_des_machines#/media/Fi... https://en.wikipedia.org/wiki/Galerie_des_machines#/media/Fi... https://en.wikipedia.org/wiki/International_Electrotechnical... https://en.wikipedia.org/wiki/World%27s_Columbian_Exposition https://xkcd.com/1227/
And basically I feel like that's it for my lifetime. There will be incremental changes from here on out. I really hope I'm wrong though and some huge breakthrough in energy or astrophysics or biology or whatever knocks me on my ass.
Stanford economist Paul Romer once theorized that breakthrough technologies don't really become productive for a generation. That lag time has shrunk to about a decade.
So instead of obsessing over the "vertical" invention, think about what it means to solve the "horizontal" problem. That in less than ten years time, something you take for granted today could be at the fingertips of 4B+ people ;)
That was the dot-com bubble: even though the internet was a big deal, pets.com and Webvan were not viable internet companies as they took on something the ecosystem wasn't ready for. They did, however, anticipate, and market to, a future where their business became viable, in the form of today's Amazon. 1990's Amazon was purely a bookseller, and perpetually viewed as sitting on a knife-edge.
Now we have a second hype cycle for VR, and while it's much better stuff this time, that doesn't mean it's actually the future. The hype around AI is similar. There was hype over previous AI techniques, too: expert systems, for example, had a period in the 80's where they were promised to do everything, assuming "everything" meant encoding a huge decision tree. Now it's the neural networks that will do "everything". NN also had a hype cycle in the 90's, but without the data and computational power, they weren't able to achieve the results we're getting today.
Developments in AI today are enumerated in achievements that become banal moments after you first hear of them: Watson beat a Jeopardy! champion. AlphaGo beat a top-level Go player. We can detect cats in images. Cars can self-drive a course better than trained race-car drivers. And so on.
It's good to be excited about the future. The marketing hype is not evil, it's necessary - it creates a dialogue, focusing people to think in terms of new technology. It's not the same as its realization, which tends to be more of a "one morning I woke up and realized I was in the future" self-reflection.
It seemed like that in 1980, as well, and then this happened:
I make no predictions around AI, although I'm skeptical it will work well outside of specialized, rules-heavy environments. Been wrong before, happy to be wrong again.
My sense is we are less future-obsessed than people were in the 1950's, during the blow-off top of the atomic age. People seem more concerned with the environment, sustainability and so forth, Moore's law is slowly grinding to a halt and technical innovation, in general, has slowed down.
Culture churn has definitely increased since the 90's, however. I attribute this to us finding ourselves at the end of modernism and post-modernism, with nothing left to deconstruct, strip away, transgress or mock. This, coupled with the internet, is leading to a blow off top in culturally combinatorial attempts to avoid a return to tradition (unthinkable) or facing up to end-state nihilism (unbearable).
It's not all bad: https://www.youtube.com/user/NewRetroWave
That said, I'm not sure if it will work in case because I've noticed that some websites block at least 2/3 of the exit nodes. So I guess that there's an IP list of shared exit nodes for all if not most VPN providers. Even if it doesn't exist is really easy to create by creating one account per VPN provider.
Torguard supposedly doesn't track/keep logs and hides your IP in IPv4/6 when torrenting. There's a tool to check if you are leaking packets which show your real IP through torrents.
In your case (Turkey) I'd go for a single VPS instance and setup an OpenVPN server, it takes 10 minutes to do so... Chances are that the VPS will never get blocked, I can't say the same for VPN's exit nodes.
The HN search has a couple of recent 'best VPN' discussion threads https://hn.algolia.com/?query=best%20vpn&sort=byPopularity&p...
Just the other day HN had an article on them. They are in Atlanta, so not far from you.
They are looking to hire 150 new employees within the next year.
>> "[MailChimp] now employs about 550 people, and by next year it will be close to 700"
Since OpenTable sends email confirmation for restaurant reservations, your team might bring interesting insight for MailChimp since it's possible you might be a current customer of them.
Interesting. I know there are Very good reasons for not relocating to either Los Angeles or San Francisco, but what were the specific reasons (aside from family/homes, if any) you and the team had for opting not to relocate?
Further to this:
2) Were team members offered raises as part of a relocation package?
3) Were team members offered the opportunity to work 100% remotely?
4) Has OpenTable approved this message?
5) Regardless of #4, are there certain conditions others would need to be aware of such as non-competes? I know NCAs are fairly (if not entirely) powerless in California, but I'm not aware of the laws impacting them in Tennessee.
Edit: per user @rfc's jogging of my brain, Stripe has a program for hiring full development teams. @wilwade, this might be worth applying to. I know I posted it in another comment, but it's worthy of top-order visibility: https://stripe.com/blog/bring-your-own-team
I was in Chattanooga from 2013-15 and have nothing but good things to say about their team. Most notably they ran a functional programming meetup that covered pretty advanced topics but was still inclusive to beginners. I'll remember the encouragement I got there for a long time.
If anybody who cares about the Chattanooga tech scene reads this: do your best to keep the OpenTable team intact. A lot of the programming community's enthusiasm is either directly coming from or being encouraged by them.
DISCLAIMER?: I was in Chattanooga a couple weeks ago and they gave me a bunch of useful, free advice on my current project. This isn't really a disclaimer though because IMO it just reflects even better on them.
I'm not saying it's impossible, just that I believe you would be better served to either find individual jobs here, or be willing to relocate. (And just to be clear, I'm not pushing the relocation thing. I love this city and wouldn't want to move either.)
I decided not to move because I didn't think the local economy offers a lot of choice for software engineering jobs. When I visited people remarked, we've got VaynerMedia, we've got OpenTable, we've got CarbonFive, etc. etc.
This news sucks because I really want to see Chattanooga grow into a techhub, but it also confirms the suspicions I originally had. :/
If you're trying to get hired as a team, that sounds new, so employers might not have heard of such a thing.
It's the first time I've heard of something so preposterous. Maybe if it was a progressive state like Colorado, I could understand, but Tennessee? I can't stand the hot, humid summers myself. Then you have chiggers and scorpions to worry about. ;)
My email is in my profile if you'd like to work together
I think a lot of people would love to contribute their free time and together that would mean thousands of hours of help into these projects which could mean that the goals could be achieved sooner. The problem is I don't know where to start and which projects would benefit from my 5-8 hours a week. This seems like the same problem I have with contributing towards open source projects.
I would love to talk more and see if there is a viable solution out there.
PS: I'd love to help but I don't think I'm qualified enough in that field! Good luck!
For php Magento and Wordpress do exactly that (ecommerce and blog).
For blog there are also some nice "markdown static blog" software that are super ez.
In my experience, a DB with hundreds of tables doesn't usually model its data any differently from one with a few dozen tables. It just has a couple dozen topical clusters of a dozen or so related tables, instead of just a few clusters of a dozen or so related tables.
1. Abondon SystemD, while there is still time! (that ship is sinking. Rumor has it many of the SystemD tools develop by governmental agencies for offensive hacking, are focused on the numerous problem with SystemD.
Just 'emerge' the best parts of OpenSuse into a Gentoo Fork.Gentoo is being raped by CoreOS, rackspace, google and a hoard of other commercial interests. So, OPenSuse could easily become the best (secure) distro on the planet, and bring a robust installation semantic to Gentoo, that is so desperately needed. Change 1/2 of the folks on your Board of Directors:: align with the little people.
Gentoo severely needs a robust installer. Then focus on UNIkernel solutions for the cloud that are secure (very small attack surfaces.
Dirt Simple:: Make money off of corporate consulting
dirt simple::you can then focus on UNIkernel clustered codesthat provide little in the way of attack surfaces.
Switching to NixOS these days, because it has dev specific features I really like (Nix, hurrr). I don't see that much benefit from switching from Ubuntu to SUSE or Fedora etc.