shepbook

I've used the same EFF sticker for about 5 years now. They are great and whenever it stops sticking, I just rinse it off under warm water and let it dry. Good as new again.

Is there a way to be able to point JSPM to a different, non-github repo? A remote clone of the repo might work then.

Given you'd like to focus on functional languages and you'd also like to be productive enough to build and monetize apps as an individual, you might like and want to look into Elixir and Elm.

Elm is a nice functional frontend language that compiles to JS, which you'll need for web apps.

Elixir is a very good and solid functional backend language that is good for general purpose programming, as well as web app programming (via Phoenix) and embedded (via Nerves).

Both of those languages are functional and focused on developer productivity and have some very good tooling around them.

I feel much the same way as much of what you've said in this post. I'm curious what you think of things like the #NoEstimates camp that removes the ambiguity and "gut check" nature of things like points or even time estimates?

I think this is a clear win for individual users that have been paying for GitHub. For organizations, I'm curious how many organizations they have just bumped above the $300-500/month mark. A lot of companies allow managers discretionary spending limits that they can spend without requesting approval, and if makes me wonder if they just made a bunch of managers need to start asking for approval for their GitHub bill. Another comment mentioned that having it filter up that the cost of a service just increase several times, will likely result in people being told to investigate alternatives. If that's the case, there are a fair number of alternatives to go to, depending on your specific situation.

No, but it depends. One thing to remember about technical debt is the concept of interest. Each time you have to go into a part of the code with high technical debt, you pay interest.

There is also something to be said for building a v1 MVP to prove product/market fit, and then build an entirely separate v2 that is refined to what you have learned.

Based on it's shape, it seems the business end of the tube is where the majority of the pressure difference would be created. I suspect that the mask is more to prevent air rushing into the nose/mouth than providing the seal for the suction. With the curved tube extending into the back of the throat, and at the size it seems, I suspect that the soft palate and back of the throat would provide a sufficient seal, with enough pressure applied to the mask and a sharp enough pull on the plunger.

Also, many sailors on industrial boats that I've seen have beards, so I'd suspect that it was a consideration in it's design and probably why the tube is there, instead of just a mask, like the yellow plunger thing.

OP Here: My team and I have spent the last several months building a system to convert study abroad offices away from inefficient paper processes and to help them better engage with their travelers. We built an algorithm to help people find a program that matches their interests and subjects that they want to study.

On the back office side, we collect information from the travelers that the advisors can use to help them start discussions and not waste time with multiple exploratory meetings.

I know that pain. Took me and my wife almost 5 years, near $2,000 and three interviews to get her green card. And that was with her already being in the states when we met and got married.

Keep at it. The feeling when it's finally over is great.

Have you ever read the E-Myth books? A fictional character can convey truth just as clearly as any other.

I second Middleman. I've used it for a number of static sites.

For responsive layout, I highly recommend Gridism. It's simple and lightweight.

They use campfire so giving anyone access to the chat logs would be as simple as adding them. They could then look at any logged history (almost all of it, unless the room was locked) and search through it however they liked.

There are two points I don't get with such a system.

1) The logic/functions needed in each "black box" still need to be written. How is that handled? Is that where the line of "programmer vs non-programmer" is crossed?

2) Programming is, more or less, the skill of breaking down a problem into the parts needed for its solution and providing the solution. The value of a programmer isn't the ability to type in code, so much as the ability to logically break down the problem and solve it. How would such a programming paradigm actually solve that problem?