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.
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.
Thanks. I had just heard their names before, but now I'm thinking maybe the combination of Elm+Elixir would suit my needs. Some other people have also suggested Elm here, didn't know why.
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 read the first chapter of the no estimates book, and have to admit that I found it weak on arguments and poorly written. I think there is real value into doing software estimations if you take them seriously, even using story points, but there must be better ways of using those estimates. One really interesting way of doing this is the Monte Carlo estimate method I linked to in the blog post. Would love to try that sometime, and see how it works out.
The notion that the business can make decision in the presence of uncertainty is the basis of No Estimates. As a participant in another accelerator our funding sources would find that laughable at best and toss us out the cohort at worst.
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.
These stories always fascinate me. At that point why even bother validating the grounds for the visa - anyone who would put up with a process like that deserves it!
I immigrated to Japan - a country often held up as an example of xenophobia and resistance to immigration, and it only took a week for my spouse visa paperwork to be examined and approved. The only cost was for translations of some paperwork from home ($40 at the embassy) and then $20 for the residence card once I was approved.
My wife and I are trying to do the same thing, we're very close to applying for Adjustment of Status(for her), and are scrambling to make sure we don't miss any nitty-gritty details, which is proving to be quite the headache. Can you elaborate on why it took it as long as it did?
