with PostGraphile you pretty much are in complete control. You're free to write your own postgres functions/views which postgraphile will expose as endpoints. you can do so such that they are standalone endpoints or sub-queries to the auto-generated table queries. you can also basically bypass all the auto-generated table queries by creating them in a schema that postgraphile doesn't introspect, and then write all the functionality you want in a schema that it will, thus getting only endpoints/queries that you wrote yourself exposed in the api.
This is pretty cool tech--if the smart alarm system works as advertised it would replace a lot of poorly-performing manual processes I currently undergo myself. Make a version with no heating element that can run on a battery and I'll buy it.
Make a version that has active cooling and I'll buy 2 and wear the extra to work.
you might be interested in Toptal (http://toptal.com)
the enrollment process is a bit long but there are a good amount of short-term, low-hour jobs available
As a real full-stack engineer, I see more job postings for front-end than full-stack. And most of the full stack postings I see are for Ruby, which I don't have a lot of experience with, and Java, which I'd rather not do.
And JavaScript, of course. Usually these are titled "JavaScript Developer" but they really mean "CoffeeScript Developer" and no thanks.
All of the opinionating is really to say it only makes sense if it's what you want to do. I happen to like programming (including JavaScript) so I do back and front end. If you don't like JavaScript don't do front end because it can and will get complex, and JavaScript doesn't help you manage complexity.
That said, if your plan is to work on web applications, the more JavaScript you know, the more valuable you'll be (in theory) to your employer/client.
I made a file tagging system with node-webkit and Vue (+ gulp/browserify/partialify). Vue was a joy to use. Most of the complexity in the app was dealing with sqlite, Sequelize and many-to-many relationships. Once the data got into a Vue VM it was smooth sailing.
I did run into some performance problems (rendering huge lists into complex tables), but I was able to iron them out for the most part. The only downside, which is definitely not unique to Vue, was debugging--a ton of functions get called in the Vue code when model data changes, so it can be tricky to find the right combination of breakpoints to set to track down why what you're expecting to happen isn't happening.
UI/UX, Django and Flask, all things front-end and game dev. Self-taught, loads of experience. I've done coding and visual design: for consumer and b2b products; independently for small businesses; in-house, producing marketing sites and internal tools; for fun and profit nights and weekends. Extremely eager to learn and grow and make.
About: Full-stack developer, visual designer, writer. I enjoy being involved in all aspects of product development. Over the course of my career I've done everything from writing and editing copy to designing billboards, developing complex user interfaces and high-performance server applications. I'm always experimenting with new languages (most recently Elixir). I prefer smaller teams/businesses, but more importantly I want to work on interesting problems with interesting people.
Slightly relevant: Lessig is currently doing an AMA (with Jack Abramoff) over on reddit [1].It's only an hour old so there's still a chance that your question might be answered.
I guess the idea is that it's preferable to an alarm clock, whose shrieking beeps and buzzes make for an unpleasant arousal.
I have an alarm clock/lamp that slowly increases light and audio levels (I have it set to bird sounds). It's great for a gentle wake-up, but the bird sounds get repetitive if you don't snooze/turn it off after 20 seconds or so.
My biggest issue with Napwell, aside from the obnoxious information desert that is its homepage, is that I could never fall asleep with a thing strapped to my face.
With every solution that comes along to solve the "host your own email" problem, and every guide that takes you step-by-step, I always find myself just wanting a huge wiki-style site with all the topology of a good, secure email/groupware server explained in plain English rather than a package that purports to do it all for me. Something with breakdowns/discussion about the different options that exist for the different pieces that make up the whole.
It's one thing to easily obtain my own personal mail server, it's another entirely to understand and be able to maintain/improve it.
source? genuinely curious if those words are written somewhere.
It would seem to me that the IRS should tax income, specifically income that I can use to pay taxes (or which can reasonably and reliably be converted into something that I can use to pay taxes).
I'd love to send 40% of last week's corporate-paid lunch to the IRS but my guess is they wouldn't accept it.
> in most countries you get a wage AND you are free to look for jobs everywhere around you, and to get them
At some point, there will not be enough jobs to keep everyone gainfully employed doing meaningful work (in even the loosest sense of the word). With a basic income, rather than having immense swaths of poverty, each person would have the freedom of any pursuit they desire. For many, this would be some form of productive work.
> Even from a personal standpoint, most people would not really feel good to be paid to do nothing.
This is a thought process very much a product of our current socio-economic environment, where you are told that you are worth the work you put in. But when there is nothing to do, how can you argue with being paid to do nothing?
Furthermore, it is disingenuous to call it being "paid to do nothing". You are being paid a wage directly, unconditionally, but there is nothing forcing you to do nothing. You are free to do anything the law affords.
Remote: Yes, preferred
Willing to relocate: Yes, but would rather not
Technologies: Typescript, Node, React, Vue, C#, SQL, GraphQL
Resume: > 10 years experience, full stack. Previously @ Amazon, currently @ Toptal.
Email: [email protected]