I wonder if this is a good analogy?
754 karma · joined April 1, 2019
I wonder if this is a good analogy?
Note: The comment I originally responded to appears to have changed their wording from "living organism" to animal. Although curiously this might not be correct either. For example, humans synthesize some “nonessential amino acids” from glucose (eg glucose → pyruvate → alanine). It's possible similar amino acid pathways can be combined into a protein completely synthesized by the human body. It also seems very likely that this happens in other animals.
https://www.quora.com/Can-the-human-body-turn-excess-glucose...
A nice mantra. Not dissimilar to the top of PG's to do list. There he also describes "the biggest regrets of the dying"..
"Don't ignore your dreams; don't work too much; say what you think; cultivate friendships; be happy."
Back in my junior days programming interviews were more about finding subtle syntax errors in some snippet of code you would never imagine writing. At the time many argued this is what compilers/IDEs are for.
It seems these days it's all about regurgitating computer science algorithms or something similar. Again many argue this is where you'd leverage an existing library. If one didn't exist you'd perhaps spend some time researching + testing your implementation. Quite a different environment to a time constrained interview with someone waiting to see you trip up.
I feel there's also a bit of a catfishing element going on here. If you pass the interview having nailed the inverse binary tree problem; you might expect the role to be just as intellectually challenging; what you find might be very different..
Just discovered this now myself. The same company sells mouse jigglers.
At $20k+ per annum cost I wouldn't expect anything less. That said we Europeans have been asking for non American date format support for years but it's a won't fix. So I guess the fee still isn't large enough.
A big complaint I have is why can't I keep the data I download off the terminal for an exchange if I'm already paying the exchange fees in addition to bloomberg's annual fee? It's like renting data. Also it makes it difficult to switch to a competing product.
Another mild annoyance is the left field approach their reps have about the tech that is visible when they make their regular visits to your office. Your company might have invested in developing data screens ,(outside of Bloomberg) and some months later those views mysteriously become available as new functionality for all users. It's even worse if you use their API; eg, you might write a private back-testing indicator specific to your market and within a day or two it appears in their public indicator list.
Seeing what you type several seconds after you typed it is reminiscent of the 90s and dial up connections.
Having familiar vi keybindings in so many applications these days has been a productivity saver.
The authors of these BBC articles (Worklife/Future) are quite independent. They are typically asked to research and write about a specific topic. Some times they can't help but bring their own bias to the discussion.
The cynic in me feels that some researchers are running out of ideas. The only experimental apparatus are poor knockout mice.
Arguably an analogy is trying to fix a compiled binary with a hex editor and replacing all your 0x11s with 0x0a. Then claiming the segfault is a good model of how another binary crashes (due to a null pointer exception or whatever really).
Basically, a python cloud-based IDE that includes a batch scheduler and object persistence backed by some no-sql database. Also has a tightly coupled DAG (think pyungo). Built on top of docker it seems.
They're geared towards insurance companies, hedge funds and banks. The system has similarities to systems used in other banks eg SecDB at GS, Athena at JPM and Quartz at BAML.
Any one have any experience with Beacon or have any views? Are there any open source alternatives out there that do something similar? Just curious.
Alternatively, aliens with more exploitative intentions might be just as bad as some humans are. Perhaps, because we are still in our technological infancy we have little to take advantage of for now. Even less to warrant the work/energy expenditure required to plan a visit to our neck of the galaxy.
I felt that perhaps defects detected by tests during original coverage might have been overlooked. It seems they were examining the defects detected by only increasing coverage.
Maybe some of the code coverage they studied were simple smoke tests without much granularity.
Code quality perception is probably very subjective.
I've considered building a custom solution as you suggest with a pi-zero. I'd need to 3d print cases and attach a simple LCD display. The option is also more versatile as one could add potentially NTP sync time via WiFi and perhaps add richer display.
That said, I'm looking something pre-canned and low powered. Developing a pi-based system would be a bit costly (time + money) for me at this stage.
I have seen a device that ticks a few boxes. Although seems a bit pricey and appears to require proprietary hardware to configure the devices:
One thing, why not stash all the function methods under a "ring" or "cache" attribute, eg
@ring.lru()
def foo()
..
foo.cache.update()
foo.cache.delete()
..
This might be less likely to clash with any existing function attributes (if you're wrapping a 3rd party function say).