No defensiveness, no push back, just a prompt to start a conversation with a potential user to better their product. :)
232 karma · joined August 6, 2015
No defensiveness, no push back, just a prompt to start a conversation with a potential user to better their product. :)
Its a signal/noise attenuation, you'll hear _more_ detail, not less.
A pair like these are what I'd consider 'high end':
https://www.amazon.com/ETY-Plugs-Fidelity-Earplugs-Standard-...
But I've always got a cheap set from the pharmacy in my pocket or the car somewhere. Something like this is perfect:
https://www.walmart.com/ip/HEAROS-High-Fidelity-free-case/15...
eg. Running the installer displays a licence agreement, then prompts to accept or decline.
"sir, you ate 4 grapes in store. Our grapes average 2seeds/grape, so we've calculated lost sales in the range of $800.
You see, those seeds could each grow into a vine that will produce an estimated $100 worth of grapes over the lifetime of the plant. You're basically stealing that money from us!"
There is a concept of IDaaS - Identity as a Service that covers the first part of your request (sign up / identity lifecycle, authentication / single sign on, user self-service for password resets, etc...).
This is one such offering, there's a good overview of the features here: http://www-03.ibm.com/security/cloud/cloud-identity-service/
Also, I recommend looking into the IBM BlueMix cloud platform: https://console.ng.bluemix.net/catalog/
I think things are heading towards what you're describing, but picture it more as a catalog of skeleton backend apps built on top of pieces like you called out, as a starting point for different types of projects.
Could you place a small magnet over the mic to essentially lock it in place? no movement == nothing to record.
Then they came for the headphone port, and I did not speak out - because I could still plug into my external audio interface or mixer _when at home_.
Then they came for my keyboard, and NOW I CAN'T ESCAPE!
Of course text editing isn't the future of programming, but when I can create and run macros as fast as I can think through a formatting change, an IDEs regex find/replace and refactoring menu with a dozen options irrelevant to the task at hand feels clunky and limited.
This device is not catering to the past, sure, but its also not catering to a large group of users the previous device did. It also seemed to have caught a lot of them off guard.
Why didn't they make the touch bar an option rather than force it on all users? they could easily have added it above the previous keyboard configuration.
60fps is roughly 16ms, for reference.
Audio is different, it's often about round trip latency (eg. from the time the sound is made, to when it is heard back) and has a few additional issues to consider. Eg. there can be phasing issues where one signal cancels out or amplifies another.
This is controlled by varying the buffer sizes, but issues can still arise due to processing latency. If the output buffer falls behind you'll hear pops as the speakers cut out.
A lot of DSP code is written to be lock-free by allocating vars when initializing so no memory allocations actually occur during updates. There are a couple great youtube talks on the subject. (look at the JUCE and CppCon channels)
password' OR 'a'='a
:PI guess they remove your manly stubble if you're into that, but my clippers keep me going for another day easily :P
Man, I can't wait for Silicon Valley to come back next season lol
> I was slightly shocked how much money they invested in synthesizers and other equipment, but it was clear they did this for the fun without any intention to make a living from it. And other people have expensive hobbies, too.
I have a friend who fixes up old cars (old Chevys, etc... from '50s - '60s)
My rule of thumb is to spend less than he is each year :P
(DevOps actually, but you're in the ballpark ;) )
This is spot on advice for anyone who seriously wants to make DJing (or live music in general) their career. Anything less than the above, at fulltime commitment, and at best you'll have a nice side gig residency at a local club (for free drinks / entry for your girlfriend and maybe a couple mates).
Don't read parent's post as bitter or negative, but a realistic view of the level of commitment in specific areas required to DJ professionally.
Its no different to us picking apart articles that give an overview of web development, for over simplifying the process of launching a successful web app. He's basically saying sure, you _can_ learn to code as a hobby, maybe even execute your idea with a level of quality on par or better than competitors, but to actually take off, you need to do all the marketing, support, maintenance and other pieces.
> I was a rave DJ in the early 2000s and opened for some of the most popular DJ's in the world at sold out clubs
I don't think this was exaggeration or bragging, and I believe it without any real scepticism. I've got friends who've done similar for our more obscure music scenes, largely due to living local to a major city, and regular offers to play for free on off nights at clubs we frequently go to anyway. (promising to bring a social group of a dozen can literally double the crowd size of the first half of a Wednesday night)
(that, and his name is probably a reference to this sexy bit of kit: http://www.juno.co.uk/products/rane-empath-rotary-10-dj-mixe... good taste, man!)
The problem with gigs being tied to popularity is as soon as you take your foot off the gas, you're overshadowed by all the new acts fighting for your spot. A lot of acts fall off the map just taking the time away to produce their next release, and struggle to re-enter the scene, I think that's the biggest negative.
I'd been racking my brain, thinking it sounded too sarcastic for a BBC doco, I didn't even think of The Simpsons.
The same people who avoid your app likely think email isn't worth $3/month, do you?
I think one of the base factors people fail to take into account is "will the outcome / result exist if I _don't_ contribute".
Sometimes the current / alternatives are _good enough_ that reasonable options are completely overlooked. I bet Yahoo could have found your last 10 searches, but you probably wouldn't say their search service is worth less than a hole in the ground, right?
If your apps were unique compared to alternatives, this could also be a barrier until some of those elements are more widespread or common. I don't know what you can really do in this case.
I'm probably not the best person to comment from a business perspective, I've never launched a personal project or anything, but your 'failures' sound like you were able to build the apps you had envisioned, which is awesome. You're basically where I'm aiming to be in the next 5 years, for what it's worth.
Upon death or filling, ownership is bequeathed to the plot of land that takes it's place.
You likely understood the consequences of your action too (and if not, you just learned! :P )
We've caught issues ranging from expired passwords, missing files / files with incorrect permissions / write failures, sync issues and other obscure gotchas.
Catching a failed step during deployment can sometimes prevent a huge rollback effort and save a lot of time.
looking back, it was the first time I _really_ understood that sitting down and learning to manage the relevant config files manually was going to be easier than dealing with a GUI app. hell, I learned for both redhat _and_ debian based distros.
I don't know if I would have gone down the path I have if it wasn't for that. that's insane...
I love when HN users give such simple, real world analogies that are so easy to visualize or relate to. For those of us from completely different fields, it really does nail down the concept. always appreciated :)
Caught me off guard, still laughing :)
Games like Civilization or X-Com could increase the level of detail by an order of magnitude, while still playing on a notebook.
For an alternative view: When an organization can't operate without your presence in that role, how can they consider promoting you out of that role?
I've seen people stall their careers by becoming the only person able to cover a particular role. I personally fell into this trap for a couple of years.
In hindsight, feeling like they couldn't do without me for a week or two for a holiday was a huge red flag. Since then, I've been conscious and cautious of this, and actively planned to avoid it.
Anything I feel I'm the only one who can cover, I make a point to properly document the process, have someone shadow me the next time I need to do it, and eventually perform the process themselves while I supervise.
Anecdotally, Rust developers are the only group I've interacted with that consistently focus on the positives of other languages when discussing different features or concepts, while acknowledging the tradeoffs and clearly outlining the reasoning behind Rust's choice.