ylg

Unfortunately, the post mostly covers the lack of monotonicity in UUID <= 5 and only acknowledges at its end and only briefly that both UUID and GUID actually have versions that solve for exactly that. Leaving us with the post’s other, unexplored, complaint that UUIDs and GUIDs are "huge" and "take up a lot of space". Any good writing out there on considerations vis-a-vis PK column size in current RDBMs or monotonic UUID versions 6-8 as PKs?

You’re on the right track, the immediate value of the email addresses is near nil. Instead consider these email addresses are highly self-targeted due to the nature of the sign up. That can then be sold for direct use, for resale, or most likely for inclusion in larger data sets that aggregate tracking information about individuals for ad targeting and browsing/results personalization. For example, consider the value to Amazon to be able to match this expressed interest with the email address of my Prime account; they could then push SQL-related content on my Amazon front-page with justifiable confidence I’d buy something vs the default of showing me canned kidney beans. Of course, that they show me canned kidney beans _because_ I just bought an SSD does show how this is mostly pie in the sky/skynet nonsense.

If you change your mind, it shouldn’t be hard to handle the taxes; I think the approach would be the same as for hobby income.

If you’re in the US and filing taxes as a employee I think you’d just sum up the book sales and stick that under Other Income. If you’re already filing as a business or self employed, just roll it in no? Of course, other countries are available.

Anyway, I’d happily pay a few bucks at the very least for this. If it’s useful, it’s going to help my own income. If I see people who maybe can’t afford a few bucks can get it for free, I’ll be even happier to pay.

Sure, same as the total cost of a movie is how long it takes to type the name into a torrent search and click the magnet link. If the OP wanted a bunch of dead temp emails, why ask other people to input them. But, not my point.

I think on HN a good assumption is posters want to discuss, to get feedback. Also not a bad assumption the notion of temp email will be news to absolutely no one at all here.

The problem is not unknown value. It’s unknown cost. Until I know everything you will ever do to me with my email I don’t know the true cost. What I can guess—given the thousands of precedents I’ve encountered over the years—is that the total cost will be time taken from my short life to fend of yet more marketing and yet more marketers. For comparison, if you ask me for currency, I know the total cost of ownership. Usually, for me, a few units of currency are a rounding error compared to the value I place on time.

The reasons people choose to develop PWA or native have greater impacts on the user experience than the differences between the two.

For example, many predict PWA development will be cheaper for them in the short-term. They are first optimizing product development for short-term cost. That focus impacts the released product more than PWA’s strengths and weaknesses. Others choose PWA hoping for a way to rapidly release and iterate MVPs of experimental business ideas. Again, the rationale has a greater impact on the user experience than the tech. Some expect native stacks will let them more deeply tune and polish the user experience than PWA. Or access richer or more performant device capabilities that PWAs cannot. And, this focus on experience over cost impacts the users’ experiences more than the capabilities of native.

In short, many PWAs feel poorer because of product development goals and constraints that precede PWA. These products were always going to give a poorer experience, regardless of the choice of PWA or native.

Note that TOTP is not limited to a single authenticator. You can, for example, scan the same TOTP setup QR code once with an app on your phone and again with a different app on your laptop (or scan in one and paste the code in the other).

I use this approach with Yubico Authenticator, which stores its data on Yubikeys, so I have all 2FAs on at least two keys even with TOTP-only services that seemingly allow only one authenticator per account, e.g., AWS.

SEEKING WORK + SEEKING FREELANCER | Remote in zones from Melbourne to Berlin

* Software product development: mobile + desktop + service * Maximize return and minimize risk * Two-person team working together since the nineties.

We specialize in developing rough ideas into light and flexible software products. We can maintain and extend those products with you. Or help you build a team that will.

We choose technologies that fit the product and fit you. Technologies you can build profits and teams around.

We are https://sensedata.com

Call or Signal us: Yuri +1 720 515 5190 and Matt +1 303 886 4337

* Recognize yourself above? Design functional and beautiful human-computer interactions? Or implement lean, provable code? We’ve things to make, people to help. Reach out.

For the "Anymore" part of the authors title to be logical, the points in his article about decreases in income disparity over time must be considered an integral part of his argument, i.e., before the disparities were reduced, outsourcing (according to him) worked.

Regardless, the question about how other businesses can be successful in their relationships if his argument were to hold water still stands—every business relationship involves imperfectly aligned interests.

By the way, a client benefits from positive return on investment. A client who loses money and receives a well-designed and efficient code base does not, i.e., the codebase is merely one component with variable traits that must be adjusted properly for each scenario.

TLDR; the author thinks outsourcing that attempts to increase ROI by leveraging international income disparities to minimize labor costs doesn't work because providers of such work want to earn as much as money as possible for their own businesses.

My thought/question for the author would be: how then can companies that work together do so without operating as charities, or are all businesses in relationships deluding themselves? Should everything be brought in-house, for example, house building? Is there a line, or a particular type of outsourcing that works or that doesn't? (Executive management, sewing employees' clothing, trimming their neckbeards?)

TLDR; In 2014 HR conducts a survey to find out what the people they hired think of HR's other surveys and find plenty of work for HR to spend the next year on and publishing about to arrive at a four question survey for release in 2015.

Yes, "man" in this context is unequivocally gender-neutral. Hence my point that it's a visual irritant due to a very specific situation rather than saying it was an incorrect usage or a discriminatory term.

No. I'm making a pedantic (clearly) suggestion about a small visual irritant for the very good reason that because of the (hopefully) temporarily toxic environment in our field, some other human beings I care about might feel a bit put out by the choice of word A over word B. Words or humans? A different word could have been chosen at zero cost and made someone else feel better or less bad; so I'll suggest that door thank you--no it doesn't matter if those put out are being rational, expressing logic compilable by GCC, or otherwise fit with anyone else's ideas about what is proper and right, because it cost nothing to do.

I dislike thinking about stuff like this. It's a waste of time and a distraction from things that truly matter, e.g., Pluto! But, a bunch of jerks already set the stage and the tune and it behooves those of us wanting to profit on that stage to be aware.

If you have data or citations to back up the "most common and easiest to understand" please share, I'm always interested in seeing data. Here's what I have to offer, for what it's worth:

https://books.google.com/ngrams/graph?content=man-hour&year_...

Plugging in rates would seem to be more applicable to me (a professional in the field) than to the target audience (people who don't know about app development.)

Maybe for the audience I think you're targeting: a few big buttons with labels such as "Thailand", "USA", "Western Europe", "Russia", "San Franspesive" and so on?

You're correct. It's just that our field is not in a good state with gender equality at moment, so some consideration beyond the literal meanings found in dictionaries is often worth the tiny effort. See: "to add insult to injury."

This seems to me to be estimating the cost to get from a fixed spec to "works on my machine (or simulator)" rather than the total cost to go from an idea to shipped product with non-technical stakeholders (whom your estimator is targeting), a diverse product team, changing understanding of the target, i.e., all the bits that investors struggle to understand seem to be omitted or minimized.

I've found in many years of building apps for clients, the easy part is forecasting simple programming costs. The hard part is helping folks understand time spent keying in code is only a small part of shipping successful software--and one of the more predictable ones. So, the cynic in me reacts with: "great, another over-simplification that instills more of those unreal expectations that so often cause failure."

Minor points worth reiterating from others:

* The rates are off for areas other than yours (how about making rates/regions an option?). And, I'd make it much clearer that the viewer is likely looking at offshore outsourcing pricing as that is a very, shall we say, unique approach to new product development.

* "Man" hours is a small, visual irritant due to the problematic gender relations and inequities in our field at the moment.

I find my interest is most piqued by non-programming fields. So, for me the answer to this question has been: listen for opportunities in the communities around fun, non-programming fields. In my case, listening to a NASA Twitter account led to a weekend hackathon that showed the possibility of programming around live telemetry from space vehicles, which I've been noodling with ever since: https://github.com/sensedata/space-telemetry

Another idea I've been messing around with for ages is a mobile app to support bicycle wheel building; something else seemingly non-programming that I love doing and so looked at specifically to see if I could invent a way to a hobby project.

And, games are another arena that have worked well for me, i.e., programming around them is fun enough to keep me well enough engaged to learn and understand new things. Mods, play-support tools, and of course actual (mini) games. If this sounds interesting, I recommend finding a moddable indie game to start with; micro-studios can be very friendly and supportive of modders in ways that keep you coming back for more.

PS From the OP's context, I'm assuming the real question is "How do you come up with hobby, programming projects that keep your professional abilities fresh and varied?"

SEEKING WORK - Remote (Colorado Rockies)

Hello there, Yuri here. I’m an independent, full-stack developer whose focus is providing folks like you great return on investment and managing risk: keeping projects lean and agile, clear and documented, and simple and extensible. I believe in flexible plans, sound forecasts, and disciplined execution.

I’ve a bit more than fifteen years seasoning in most every major (and not a few obscure) platform including: Node.js, Ruby on Rails, .NET, J2EE (I know, the cool kids don’t say jay-TWO anymore, but I started with it when it was snowing and uphill both ways), and even Windows DNA. I’ve helped tiny startups and large companies, and even tried bootstrapping a startup or two of my own. I’ve written the business plans, built and trained the teams, designed the architectures, programmed the code, and designed and programmed the test suites.

These days, I work alone and as part of a group as fits each project’s needs each week. When needed, my partners can collectively bring a century of experience designing, developing, and managing complex software and it’s user interfaces. I specialize in back-end APIs, services, and HTML5 web apps and my partners add iOS and Android mobile apps as well as user interface design.

I can work with you remotely from the Colorado Rockies using GitHub, Slack, Trello, Google and Skype Video, and Google Docs and Sheets; we can also meet near us or you to kick things off and to keep them going.

Whether you want to launch a new product, a one-week prototype, figure out the development budget for your startup, rework a monolithic system into services and clients, or just stabilize a legacy product, get in touch and find out more about me here:

http://sensedata.com/about/us#yuri

1. Food, as already said, but so very important it bears repeating. I've found there's nothing like a lack of available chemical energy (or water to facilitate the reactions) to drag down my kinetic expenditure. Just being aware of this is helpful, e.g., "I don't feel like doing anything… Wait, I haven't eaten right today… OK, time to fight through that now that I know the cause isn't some cosmic force outside my control!"

2. I've found I've a strong connection to musical context, i.e., when my ass is dragging, playing tunes I have listened to while doing things I find fun (in my case, careening down mountains on bikes with earbuds in) can give me a good jolt out of a lethargic moment.

3. Redirect the slack. Few time-wasters out there compare with surfing the web. So, if I'm falling down that rabbit-hole, I surf to find things I find motivating and energizing, e.g., reading about the training regimes of athletes I admire, or find youtube clips of them demonstrating significant badassery, or finding training clips I can follow (I've been enjoying Ryan Leech's 30 Day Wheelie Challenge lately.)

4. Take a nap. In the sun if possible.

5. Listen to Car Talk (while eating some proper food, but be careful with liquids that can come back through the nose.)

6. Smile. If you can't do #5, just plaster a big, fake grin on your face. I find it rare my brain doesn't say "hey, we're smiling here, crap we must be happy and energized and I just missed the memo, time to get on that!"

Sure: CSS is better managed and maintained and more easily understood by future maintainers outside of React and JavaScript, i.e., more cheaply and with less risk. And there are plenty of sugars for making it even better, e.g., SCSS, LESS.

The way CSS in React should be is not to be.

I'd say the fundamental issue is that they are solving the Yellow Pages problem, i.e. "how do I find a list of people who say they do what I need" or "… need what I do". That's not been a valuable problem to solve since, well, the Yellow Pages.

A valuable, related problem to solve is "how do I find a few people I could rationally believe will help me get positive return on my investment." And, so far as I know, no one has figured out how to convey the information we humans need to arrive at that belief or trust via web pages (or printed yellow ones)—notions like "we only register l33t with GitHub cred" and Ebay-esque star ratings not withstanding.

Interesting and well written; if it were me, I might only change the ending a bit:

"Whereas, const […]. It is not nearly as useful as immutable data, because the problem it solves is easy, not hard."

To something like:

"const may be more useful than adding something like immutable data to an imperative language with mutability deep in its DNA might be because it helps with one of the hardest problems; long-term, correct re-reading by humans doing maintenance or extension."

But, the OP covers that well earlier in, so I'm not sure a third take on it would add much. Thanks for doing the exploration!

SEEKING WORK - Remote (Colorado Rockies)

Hello there, Yuri here. I’m an independent, full-stack developer whose focus is providing folks like you great return on investment and managing risk: keeping projects lean and agile, clear and documented, and simple and extensible. I believe in flexible plans, sound forecasts, and disciplined execution.

I’ve a bit more than fifteen years seasoning in most every major (and not a few obscure) platform including: Node.js, Ruby on Rails, .NET, J2EE (I know, the cool kids don’t say jay-TWO anymore, but I started with it when it was snowing and uphill both ways), and even Windows DNA. I’ve helped tiny startups and large companies, and even tried bootstrapping a startup or two of my own. I’ve written the business plans, built and trained the teams, designed the architectures, programmed the code, and designed and programmed the test suites.

These days, I work alone and as part of a group as fits each project’s needs each week. When needed, my partners can collectively bring a century of experience designing, developing, and managing complex software and it’s user interfaces. I specialize in back-end APIs, services, and HTML5 web apps and my partners add iOS and Android mobile apps as well as user interface design.

I can work with you remotely from the Colorado Rockies using GitHub, Slack, Trello, Google and Skype Video, and Google Docs; we can also meet near us or you to kick things off and to keep them going.

Whether you want to launch a new product, a one-week prototype, figure out the development budget for your startup, rework a monolithic system into services and clients, or just stabilize a legacy product, get in touch and find out more about me here:

http://sensedata.com/about/us#yuri

SEEKING WORK - Remote (Colorado Rockies)

You bring the idea and I’ll bring fifteen years of developing complex software products on Node.js, Ruby, .NET, Java, and Windows DNA for tiny startups and large companies. I’ve bootstrapped the startups, written the business plans, built and trained the teams, designed the architectures, programmed the code, designed and programmed the test suites, and managed the multinational departments release to sunset.

Return on investment is my focus and so managing risk my priority: keeping projects lean and agile, clear and documented, and simple and extensible. I believe in flexible plans, sound forecasts, and disciplined execution.

I work alone and as part of a group as fits a project’s needs in a given week. My partners collectively bring a century of experience designing, developing, and managing complex software and it’s user interfaces. I specialize in back-end APIs, services, and web clients and my partners add iOS and Android apps and user interface and experience design.

We work remotely from the Colorado Rockies, San Diego, and Madison WI, using GitHub, Slack, Trello, Google and Skype Video, and Google Docs; we can also meet near us or you to kick things off and to keep them going.

Whether you want to launch a new product, a prototype, figure out the development budget for your startup, or rework an monolithic system into services and clients, get in touch and find out more about me here:

http://sensedata.com/about/us

If people are willing to give you an interest free loan it's probably a decent indicator that you could charge more per month.

I'll second that. As a customer given the option of paying $1 a month or $12 a year, I'll chose the former unless I've had a stroke. Yearly prepayment is wasteful, that money could be put to use for me instead of you.

So, if a customer agrees to pay me annually the same they'd pay monthly rather than staying monthly or leaving if that's not an option, I've made a mistake in valuing my product. Moreover, by replacing apples with oranges, I'm risking turning away customers for whom the price is right but not the structure in exchange for income statement foofaraw (and I still haven't addressed my original mistake.)

As an aside it's a great validator for your business model if a lot of people are willing to pay a year up front.

That or the sales context is one where rational thought is …limited; candy bars at kid height in the checkout aisle. And, now I'm imagining buying a giant box of a years worth of candy. Time to go outside.