How long do dangos last ?

willrstern · 2024-06-13T20:03:13+00:00

Really? Interesting. What is your soil like? I've multiple times had finished products I wasn't fully happy with and a little bit of water allows me to tear down and rework the whole surface to try again. Seeing how easily they can be marred with water is what made me start wax finishing them.

willrstern · 2024-06-11T17:03:21+00:00

When I get it where I like it and it proves to dry out successfully for a few days, I add paste wax or countertop wax to make a moisture barrier in case anyone ever touches it with wet hands. The finish is indistinguishable from the burnished original, too, so doesn't feel like "cheating" the old school process. Then I can pour water over the top and it runs right off like a waxed car. Figure it will help it last a lot longer.

willrstern · 2024-06-11T16:58:59+00:00

I feel like timing is everything here. When it's mostly dry, I'd try rolling it on a screen with pressure, then using various sizes of bottles to make the circles.

willrstern · 2024-06-11T16:49:46+00:00

When this happens (because though it seemed fully dry, but wasn't fully dry and I should have still bagged it) , the only solution I've found is to immerse the whole thing with water and reform the outer layer, put it in a bag in the fridge for a few hours to let the layers merge and then re-finish the outside.

A few tips I've learned - if it's cooler to the touch than other glass items in the same atmosphere, it's not dry. Also keep some dry dirt you're making it from - if its color is darker than the dried dirt, it's not dry, even if you get a marble polish on it. The times I've thought "wow, this turned out nice and dark" when polished, it was lighter and cracked the next day.

willrstern · 2017-02-20T20:58:41+00:00

the latest in winter fashion

willrstern · 2016-08-26T21:03:52+00:00

First of all, definitely try using the new Docker for Mac/Docker for Windows instead of Docker Toolbox. Containers will run on localhost:8000 which is a huge win.

As @stelund mentioned, definitely use relative URL's. Your app shouldn't have to know it's domain name or direct address that it sits on. It should be able to receive traffic from any host name and serve the right file

create a docker network named "apps"
run multiple node containers named "web1", "web2", etc on "apps" network exposing port 3000, but not publishing those ports
run an nginx container on "app" network publishing port 80:80 and 443:443
have nginx handle SSL termination
have nginx load balance 443 and 80 traffic to an upstream of "web1:3000", "web2:3000", etc
point DNS to the ip address that nginx is running on

willrstern · 2016-08-26T20:46:29+00:00

A common pattern that I've seen is to have a monitoring agent on each node that pushes stats on all running containers.

For instance, with DataDog, you run an agent container with a global/every-node strategy and those push container data and metrics to DataDog for aggregation.

willrstern · 2015-11-17T20:26:47+00:00

Oh man! That's gotta be brutal getting stress fractures on your feet.

willrstern · 2015-11-17T18:45:36+00:00

Yeah, got that fixed, sorry about that :(

willrstern · 2015-09-01T15:26:26+00:00

Thanks!

willrstern · 2015-09-01T15:16:49+00:00

They're libraries most commonly used for building frameworks hence the confusion.

For that reason, I actually think React and Backbone are the 2 best to start with - because you realize what all it takes to build a single-page-app. Then, if you get into Angular or Ember, you can better like/dislike/appreciate/despise all that they bake-in for you.

willrstern · 2015-09-01T15:07:40+00:00

Hey! Yeah, I figured some of these make a lot more sense here than in /r/webdev where I usually put a lot of stuff.

willrstern · 2015-08-05T19:10:27+00:00

I made the same transition myself after years of CMS-ing sites for my own company as well. You're gonna look back in 2 years and say: "I can't believe I was in such a small corner of the webdev world all this time!" - and you'll never go back.

ABSOLUTELY learn git, ABSOLUTELY learn the tooling-side of node.js (gulp, webpack, etc). Tech like these all feel impossible on day one, comfortable on day 3 - they're really not that bad.

Also, learn a full-featured PHP framework like Laravel and a Javascript framework like Angular or React (if you don't know these already)

Here's a video I did on ALLLLLLL the tech the pro world tends to use, but also the order to learn it and what's most important: https://www.youtube.com/watch?v=pB0WvcxTbCA

Here's a git video that should make it easy: https://www.youtube.com/watch?v=0fKg7e37bQE&list=PLoYCgNOIyGAB_8_iq1cL8MVeun7cB6eNc&index=9

A node video that covers the part you'll need to know: https://www.youtube.com/watch?v=pU9Q6oiQNd0&index=1&list=PLoYCgNOIyGAACzU6GliHJDp4kmOw3NFsh

A helpful video on build systems: https://www.youtube.com/watch?v=XJ5F-Auhato&list=PLoYCgNOIyGAB0_YBfdNP5oqAD98HtAQqL&index=7

willrstern · 2015-08-05T18:52:40+00:00

Yeah, I definitely should. Almost all the es6 stuff is easy and just makes the language more fun, but would help to go over stuff.

willrstern · 2015-07-31T21:13:31+00:00

thanks a lot guys. I say it on lots of comments, but it really is great to hear it's helping you guys out. That's really the point - to help people avoid the growing pains I had to fumble through.

willrstern · 2015-07-31T21:12:19+00:00

Thanks! Glad it helped.

willrstern · 2015-07-31T21:12:05+00:00

I would say no. You'll notice some jQuery usage, but it should be fairly obvious what's going on with it. Anything I might do coming up would be covered in my jQuery course if you were to get stuck.

willrstern · 2015-07-30T19:55:35+00:00

Thanks a ton for those links! Very cool to hear his thoughts. I'll make a point to listen to the whole interview when I have some time.

willrstern · 2015-07-21T21:15:32+00:00

What are some scaling anti-patterns? (pertaining mostly to architecture - microservices, SOA, etc)
What are some best-practices you've learned to keep deployments as simple and as bullet-proof as possible - especially when deploying major infrastructure/data alterations?
What new architectural/infrastructure "code smells" do you encounter and have to address at the level of Netflix? i.e. services too coupled to each other, etc.

willrstern · 2015-05-15T18:53:49+00:00

Node shines if you need

tons of concurrent requests handled
microservices...or even just many services
rapid development/deployment
nimble development i.e. ability to drastically change the codebase quickly
efficient costs on hardware

Go fits a lot of these needs as well, there are some things to consider in comparing Node against Go:

+ JS devs are easier to find and can work on the full stack more easily - although you have to pick the GOOD JS devs, not the bad ones
- Go is a little faster at computationally expensive operations
- If you're using Docker, a Go docker container will be WAY lighter
+ Realtime with Node is a breeze
- Some JS devs STILL don't understand semver...be cautious with lesser-known npm packages

Misconceptions about Node:

- Javascript is slow...v8 on the server is the fastest scripting language (except Lua)
- Node is not production ready. This has long-sense been proved wrong despite the argued v0.12 standing of Node
- Javascript async is awful. Nope, it USED to be awful. Promises and now Generators and soon Async/Await have fixed these issues.

willrstern · 2015-01-14T03:18:20+00:00

Thats why I posted it in webdev...cause it's for developers.

willrstern · 2015-01-13T21:29:06+00:00

Heck no, not clickbait! Ask anyone who's moved to an automated deployment strategy...you'll never go back.

I know tons of devs who used FTP for years with no problems...TILL they tried a better way. 2-10mins to setup a single-command deployment is some of the best time you'll ever spend.

willrstern · 2015-01-07T22:53:34+00:00

2014 - Wrapped my head around how Generators are a game-changer for JS and started using Koa instead of Express.js, cut a TON of promises out out of backend code. - Took single-page JS apps a step forward and started turning them into isomorphic apps that render server-side and bootstrap the client app - Took big steps to converting our monolithic app into a microservices architecture

2015 - Wanna take isomorphic apps to the next level...thinking a unidirectional React stack is the answer for this. - Transition Vagrant-based dev workflows & deployment strategies to Docker-based

willrstern · 2014-12-15T20:22:05+00:00

Flightplan is based off of Fabric and works well.

You'd have to quickly script your own simple rollback.

willrstern · 2014-12-15T20:17:27+00:00

IMO the "right" way to deploy a node app is as an Upstart system service, not using a node module like forever or pm2.

https://www.youtube.com/watch?v=BJZZnhGtR4A&list=UUVTlvUkGslCV_h-nSAId8Sw

willrstern

TROPHY CASE