patrickwiseman

Got a PR put together, but need to QA it in the morning because no sounds exit my laptop after 11pm ET. https://github.com/thephw/claude-meseeks/pull/4/

Well apparently optional fields with a default are not configurable so I have to make them required... unexpected.

They are suppose to be boolean fields, but it looks like the UI got mangled. I'll take a look.

It will surely be the npm package port

Love that warcraft II and starcraft were also top of mind for fun packs.

lol I got that prompt working on this

I built a proxy number for my sister who has to deal with her abusive ex-husband. She has court ordered visitations via phone for their kids. He would give her number to any multitude of people that would send harassing messages on his behalf.

The proxy allows any calls or texts from her number to send out with the proxy number. Any calls or texts from his number connect to her phone. All other communications are given a notice that they don't have access to call or message the proxy number and communications are recorded for court. It does not forward blocked communications to her phone. He continues to give out the number to harass her, but the family court judge gets a monthly report of all the attempted harassment.

To be honest I think this happens naturally and it's fine. The median age in the community feels older and more folks are working in management and business roles. Interests in a community ebb and flow in relation to what folks are working on these days.

The DNS hack is a nice low fidelity way to avoid procrastination helpers. I have also used https://www.rescuetime.com/ which provides a bit more of a polished interface for accomplishing the same effect.

One aspect is that LinkedIn is protective of plugins that incidentally cover up their own ads. Notably several entries on this list once had such grievances filed against them.

Special thanks to @the_thagomizer for publishing her excellent article “Diversity is not a check box”. Prompted me to finally finish this article.

http://www.thagomizer.com/blog/2016/08/12/diversity-is-not-a...

Might we be making the mistake of confusing neglect for malice?

Have you reported it to someone with prosecution powers?

http://www.fbi.gov/about-us/investigate/cyber

http://www.ic3.gov/default.aspx

Much agreed. Verilog/VHDL are simply not programming languages. They are Hardware Description Languages. They describe parallel components that will actually be "wired" together.

My advice if you are a programmer or computer scientist and you get tasked with writing Verilog of VHDL "code" you need to be able to explain the difference -- You've just been offered a job as a hardware designer and engineer. Having spent 5 years doing hardware engineering and a lot longer doing software consulting I can say it's an entirely different set of skills if not an entirely different career path.

Time to market and developer productivity matter so much more than capital expenses that it is ridiculous. I could buy another server in the time it takes to pay a developer for a days work. Not to mention, not all the features on a web application need to serve more than 2500 requests per second. The ones that do can be refactored into a web service with higher throughput or designed to be scaled separately from the rest of the features. It doesn't make sense to daisy-tank (to pick daisies with a tank) every single feature to support throughput it doesn't need at the expense of developer time. More over until there are analytics for what your users are using deciding what to optimize is entirely speculation. Bad science. The best way to get those analytics is to be live and the best way to be live is to have a built product.

The benchmarks of linux on a physical machine rather than a virtual machine is not representative of performance for (gawd help me) cloud-centric deployments. These benchmarks assume the maximum benefit from compiler optimizations that would not be available on a virtualized machine.

I'm not sure what compilers check more than syntactical errors. Those aren't any slower to fix in a dynamic language. I'd recommend checking on Sandi Metz on testing

The rest is just language preference. And my preference is ruby. Python is fine with me too. Javascript makes me a sad panda, but it runs in all the browsers and it's a lot better with the magic of coffeescript.

It's been a much more acute phenomenon lately, but that's what I'd expect when there is an onslaught of stories that are going to upset hackers.

Nope, facebook wasn't around yet.

Don't worry I just figured out the totally bone-headed programming mistake I made at noon today. Time is a good mediator between skill and stress.

With timings that are several orders of magnitude in difference I'd just ignore the constants between factors as they change too frequently. Also there is a difference between latency and bandwidth and the chart is simply inconsistent.

CPU Cycle ~ 1 time unit Anything you do at all. The cost of doing business.

CPU Cache Hit ~ 10 time units Something that was located close to something else that was just accessed by either time or location.

Memory Access ~ 100 time units Something that most likely has been accessed recently, but not immediately previously in the code.

Disk Access ~ 1,000,000 time units It's been paged out to disk because it's accessed too infrequently or is too big to fit in memory.

Network Access ~ 100,000,000 time units It's not even here. Damn. Go grab it from that long series of tubes. Roughly about the same amount of time it takes to blink your eye.

I believe one of the main points the article is highlighting is that science would have better representation in U.S. law if more elected representative were scientists, but this is not really true. Most laws aren't derived from regulatory law, but rather from common law set through court cases. In my opinion scientists are most useful as scientists, expert witnesses, and lobbyists in that order.

Not necessarily true. Large companies can and do currently benefit from higher corporate tax and a complicated tax code. It creates barriers to entry for new companies competing in their market. If you make the tax code simpler it provides them less opportunities to specialize in avoiding taxes.

The simpler solution to the proposed problem is an estate tax on capital holdings. This could be done by simple requiring the shares be sold on death and repurchased in the beneficiaries name.

Mark-to-market adds voodoo to tax valuation, has the government managing investor cash flow, and rewards investment losses more than the current system. Why reward poor market performance?

Personally, I think this seems like a suggestion for bad governance trying to appease wealth envy.

Being able to syntactically assemble several parallel requests together has an obvious advantage in making code more readable. Having a hard time wrapping my mind around the keywords. From the examples I think more wait/collect than await/defer. For instance:

Await these items that I want to defer.

Wait on this code block and collect these items.

I still was able to replicate, albeit with some effort. Used a bobmail.info address, "Jake Doe", and had to have them actually call to deliver the pin.

Results were not that unexpected save one, but it seems like a friend of a friend.

I think IT and devices are two different problems entirely. Most of the healthcare groups I've worked with have their IT purchasing decisions made by the IT department with minimal input from the senior staff or medical staff. The IT departments are making their decision based on begin largely underfunded and are trying to implement any solution that requires the least amount of effort on their part because of labor cost savings. Which is why you don't have too look very hard to find high cost solutions with terrible interfaces for physicians but decent interfaces for IT administrators.

Medical devices have mostly been vetted by physicians and provided to the IT department who tries to discern what works well in their current network. All the fat cat decides is a yes or no to the entire proposition. It's a people system, sales isn't about convincing one person its about convincing many.

The largest problem is always in getting innovative products into the hands users. With IT its no different than normal and with medical devices you have to make disclosures to the FDA because of patient safety considerations, but this paperwork isn't particularly difficult.