Hacker Newsnew | past | comments | ask | show | jobs | submit | junker101's commentslogin

We've found https://tilt.dev/ to actually be a great alternative to docker-compose that also keeps the local setup and knowledge more inline with production (which is Kubernetes hosted)


Running Kubernetes in production, we've also decided to adopt tilt and get rid of Docker compose. Our own tooling with docker compose has been to painful to maintain, and there was too many workaround to try to replicate what we have in production.


Location: San Diego, CA

Remote: no

Willing to relocate: Relocating to San Diego now.

Technologies: JavaScript, PHP, Python, Java, SQL, NoSQL, DevOps, Cloud, Marketing & Ad Ops, full-stack, etcetera. (Anything web related: You name it, I've probably evaluated and/or used it professionally.)

Resume: Currently employed, so reach out via email for resume/identification.

email: robotsantaclaus@gmail.com

I have an entrepreneurial background, am currently the head of Technology for a major (Fortune 500) corporation, and looking to relocate to the San Diego area. Extensive experience designing/building and managing development of very high traffic web properties and software systems for major/global brands. In particular, I have deep insights in the marketing & advertising space. Would love to help a smaller to mid-size company optimize and grow their tech department.


It's typically 'SESSION' specific things with connection pooling that I've seen underlying (sometimes long-uncaught) bugs in production systems.

e.g. A 'ALTER SESSION'/'NLS_DATE_FORMAT' commands in Oracle or even an unfortunate 'USE <db>' w/MySQL.

There are of course safe solutions & techniques for this, but when you have an otherwise stateless-by-design codebase (such as with PHP), picking up "possibility state-laden" connections is a bit of an unexpected concept that I've seen catch developers more than once.


That seems a terrible idea. Don't do that!


Actually, in larger enterprises (or maybe this should be "non-startup stage companies") I find its actually often the exact opposite.

If we're profitable, we're going to invest in a better working experience so that our employees spend minimal time 'dealing with' a tool's 'issues'. -because we can.

If we're a smaller pre-profit/cash-strapped/VC-beholdened company everyone is going to be expected to tolerate working with 'rough' tools if it can save a few bucks.


If you apply zero-trust (as you are here), then its also _impossible_ to assure all those attributes are present in the current voting system. So I see no harm in attempting to solve for "better" or even "equal but more convenient" than the current. -Which does not technically rule out _some form_ of internet voting.


current voting systems actually work very well with zero-trust.

- You enter into the voting booth with your ballot and cross off your preferred candidate or party. No trust needed.

- You fold it together and put it into a ballot box. No trust needed.

- The ballot box is sealed and driven to a counting station. This is done under supervision of all stakeholders, meaning that cheating is extremely hard because your political adversary is present.

- The ballot boxes are unsealed and the votes are counted. Note that the votes are counted by all stake holders (typically one or more people from each party) making it hard to cheat.

- The final vote is passed on.

None of the above steps require trust in any one person or entity, and the probability of cheating (if the procedure is done correctly) is quite low. If there is some anomaly the votes are saved so they can be counted again.


Literally, all of those trusts in that scenario are with 'people' which are indeed quite easy to corrupt (or fail without awareness). Possibly more so than potential crypto and chain/ledger based systems.

And again if "probability is low" is the bar, then we can surely keep _exploring_ Internet voting systems without engendering rejection as academicly 'impossible' for the whole concept.


> The real programmers will say "Yeah it works but you're leaking memory everywhere. Perhaps we should fix that." I’ll just restart Apache every 10 requests.

They're cattle not pets. (/semi-sarcastic)


If by "single folder on a hidden home page containing unused default apps" you mean "App draw", then you've described Androids (arguably superior) default UX.

Put another way.. You're manually 'fixing' the iOS UX to operate like the Android "default"?


Location: San Diego, CA

Remote: no (moving to San Diego in Q1)

Willing to relocate: Relocating to San Diego January 2017.

Technologies: PHP, JavaScript, Python, Java, SQL, NoSQL, DevOps, Cloud, Marketing & Ad Ops, etcetera.

Resume: Currently employed, so reach out via email for resume/identification.

email: robotsantaclaus@gmail.com

I'm currently the head of Technology for a major (Fortune 500) corporation, looking to relocate to the San Diego area. Extensive experience designing/building and managing development of very high traffic web properties and software systems for major global brands. In particular, I have deep insights in the marketing/advertising space. Would love to help a smaller to mid-size company optimize and grow their tech department.


Also, the security aspect: Hangouts would get a bunch of backlash in the Enterprise world if they added the Allo type features to it. So they have pretty much to have separate systems for Enterprise vs Consumer if they want to integrate all the Google Now capabilities.


Also worth a look depending on your needs: https://codenvy.com/ (based on open source eclipse che IDE) http://www.koding.com/ (easy hybrid local IDE and/or cloud IDE integration)


Congrats to the c9 team, but if you have a chance would love if you would take a look at https://codeanywhere.com


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: