519 karma · joined May 17, 2010
Email: hn@carterventures.com
My oldest two could not do sleep training. 10 months of trying for almost every night and they did not just adapt. My middle daughter embraced it after a single night. My adopted middle son didn’t need it at all and was naturally “good” at sleeping. My youngest daughter and son will fall asleep right away if around someone, but otherwise will stay up for hours (but never cried about it).
Again, one family experience but each child has their own needs and responses. I’ve never found a single method that works universally in any aspect of parenting.
Except ice cream. They all seem to love that.
Didn’t speak the language, didn’t try to make people speak English - asked for the Japanese menu and used Google translate to figure it out.
Kyoto was incredible.
Apple does not allow for this model.
Sentinel is a cutting edge privacy technology company changing how organizations of all sizes think about privacy and compliance. We are building the next generation of privacy tools and already work with some of the largest companies in Technology, Retail and Manufacturing. Come join our team and play a key part in how the world addresses the needs of privacy for organizations and consumers alike!
Some of the technologies you'll work with: Azure, AWS, Hasura (GraphQL), Java / Spring Boot, Vue, NGinx, Postgres, ElasticSearch, and Spark. We're expanding into AI / ML scenarios as well.
We're looking for full-stack engineers, back-end engineers and anyone currently focused on the privacy space. Our careers page lists Java Engineers but willing to consider anyone with a development background if you're interested.
Reach out to me, chris at sentinelcsg.com.
We've since had it framed.
Isn't that the biography of 99% of the open source projects in the big data and distributed processing world? I understand they are open now, but didn't they start as custom tools just for a single company?
It seems like the "error" that Fog Creek made was to not open source Wasabi, though even that seems more like a hindsight has 20/20 vision kind of thing, as open sourcing a project is no small feat, especially to a small software company.
http://www.washingtonpost.com/blogs/the-switch/wp/2014/09/15...
How can you hope to defeat stuff like this in court if you can't survive the fines building up while you're waiting to see the process through?
Before I was married, all of those fears and anxieties ruled my life. I think that's partly what attracted me to the startup world and ultimately to starting that company. I wanted to chase my ambitions and fight that feeling of loneliness. However, the great lesson I learned from that company, and ultimately from the last few years of marriage and kids is that you won't be alone when you choose to value the people you love over achievements you earn, stuff you buy, or even just stuff you work really hard on. I poured it on with the 90 and 100 hour weeks the last 6 months of that company and in the end the company crumbled and my hard work left me with nothing but bitterness toward my creation (I eventually got past the bitterness). Today I invest that time in my wife and my kids, and they are my world to me. They're my best friends. There's no earning their love, but the time I spend with them is never wasted. I don't get through the week, having prioritized them over other things, and think to myself "man, I really wish I'd spent an extra 20 hours on that personal project" that will never do anything for my personal fulfillment beyond some temporary ego boost.
Now. That's not to say I don't still love the startup and technology world. I do. And I still have those personal projects. And that professional community. I also love working hard on stuff that pushes the envelope. But the funny thing is that ever since I put that part of myself in a bounded box I've enjoyed it more and been more productive. There isn't the sense of having to keep up, and yet I'm still able to. Consequently I'm happier at work and since I don't draw my personal worth from it, I can take setbacks and move on and still enjoy it.
I don't know that everyone should get married, but it seems to me that, based on everyone I've ever known, that you best fight loneliness by surrounding yourself with people who will stick by you regardless of job, religion, social status , health, or anything else. To me, the question to ask is - if the world fell apart right now, would the people you prioritize still be with you?
My wife's cousin is going through the program right now and will graduate with the equivalent of an MD. She's doing residency at a large hospital in Seattle and did clinical at another in Boise. When she graduates she'll be working adjunct at either another hospital up here, or through Stanford. I'm no medical expert, but I trust her experience and expertise. I'm not sure where you're information is coming from, but I think you may be misinformed.
I'll definitely use them again. The point though, is that for a nominal fee, it's just easier to have someone who does visas every day handle the China situation for you, at least in my experience.
The exploits have happened in ways that have exposed and hammered home the myriad places many applications expose unexpected side channels and larger attack surfaces than you'd think. These issues have opened a broader range of people to vulnerability, and I think opened a lot of people's eyes to the need for a sense of security and what that really means.
Top that with the level of explanation we've seen in at least the Rails and Ruby exploits, it's been a tremendous educational opportunity for a lot of people who will benefit greatly from it, and by proxy their users.
When the idea of a "SQL Injection" first became really prevalent, we saw an uptick in concern for security amongst framework developers, as far as I could tell. I think this will help get some momentum going again.
Speaking as a non-expert on the subject, security is all about a healthy sense of paranoia, across the board :)
Come to think of it, the Samsung Blu-Ray player we bought the year before also plays all of those services, too.
Both devices have been great - wireless support and smooth interfaces.
We are indeed a battery-based system for now, though we aren't necessarily tied to that technology long term. We've focused on building a strength is in flexibility and ability to distribute storage wherever its needed. It's always exciting to see new methods of storage being developed, as I agree with you about the economics of storage. I'm not quite convinced that batteries are an antiquated option just yet (or aren't feasible financially or environmentally, long term, especially as R&D continues to move there as well), but I'm just a lowly software engineer - I'll leave it for the rest of our team to worry about those problems :)
Congratulations on your successes thus far, and good luck for what the future holds!
Hopefully I don't sound like I'm disparaging LightSail or any of the other possible avenues - I think we need continued investment in new methods as we should always be pursuing improvement, and the LightSail approach sounds very promising. I hope Thiel and Gates' involvement in this industry will bring even more visibility to it. However, I do want to make the point that there are people doing this today, in consumer and commercial applications, and having real effects.
I have a background in data warehousing in both Oracle and SQL Server, and was part of the decision to use a polyglot persistence model. I've got at least a decade's worth of experience in the DW world, and more as a general developer before that, so I like to think I've got a relatively credible background in a variety of data stores.
I haven't looked at Mongo much - it's durability concerns and the write lock stuff pushed me away from it early on (I don't mean to disparage it, but that was where it was at when I evaluated it), but Cassandra's configurable consistency levels and operational story at a cluster level are what sold us for our time-series data (that, and the ability to construct a sparse timeline and multiplex reads/writes). For anything we need flexible querying with, we push it into specialized Postgres dbs.
The level of willful ignorance and vitrol in this thread is kind of amazing. Most of the really experienced DW guys I know are all looking at HBase, Cassandra and others because they fit a niche that we've all been looking for in certain data sets at really large scale. It doesn't mean we're ditching our relational data stores, it just means we're augmenting them with other tools because they fit the job at hand. To suggest that one tool is absolutely perfect for every scenarios seems a little short-sighted to me, possibly driven out of inexperience. I don't mean that as an insult - I know a lot of guys who've been working on the same data sets for 30 years who really do just need the one tool - however, you've got to realize there are other data sets and problems for which your hammer just won't fit.
Version 1: Get to market, prove your product, make a big mess
Version 2: Make a ton of mistakes, screw everything up trying to clean up the mess but get sidetracked with all the great ideas you don't have time to implement
Version 3: Scale back, get smart, and build what version 2 should have been in less time
In my experience, most companies either get completely discouraged or worse yet just wreck themselves on version 2. The nice thing about iterative development is that the V1 - V3 spectrum happens fast and your failures are smaller.
Certainly, the idea of what smells "good" and "bad" is subjective, but as history proves out, I think our societal aversion to odors is 1. deeply seeded and 2. probably practical - if you smell bad, you are likely dirty (and need to wash up)
The delight is in the speed at which I can quickly explore and consume human knowledge. Nothing I've seen in terms of graphical suggestions would improve that - only distract or prevent my friends in other countries from being able to use it properly.
To me, Wikipedia is embodiment of "less is more", which supposedly all of these hotshot designers are supposed to subscribe to, but apparently mistranslate it to "a metric butt-load of negative space".
When we click the build button, a small Python script is called that rsyncs over ssh the already built artifact (pulled in from the existing TC build) over to the environment, which runs JBoss, and gets auto-deployed.
For our developers, our build process amounts to committing their code, getting an email from TeamCity when the build completes, then clicking the Deploy button. The tools take care of the rest, and we end up with a nice trail of logs available in case anything goes wrong, and a clear rollback strategy.
We also don't get an ever-growing git repository, or have to maintain a bunch of FTP configuration. Everything is done over ssh via passwordless pki. Best of all, it didn't take long at all to set up (the longest part was probably writing the python deployment script, which has some basic logic to know which environments live at which addresses, and also how to run some post-deploy commands for the 1 non-JBoss deployed .jar based service we have).
It's not perfect - we don't have an automated database migration mechanism right now, though in a distributed system like ours I'm not entirely sure one would work at this point (and we've got other plans to deal with that weakness anyway). I'd also like to move to Hudson or Jenkins at some point, as there is a real attraction to the rich ecosystem there (TeamCity is a commercial product).