1,466 karma · joined January 29, 2020
Finding a way to fund this is going to be an uphill battle, although I like the creative ideas amadeuspagel mentioned. Like anything else, find a niche somewhere (possibly related to performance/memory for clients not using React) and serve it with a modest upsell. But it's an enormous market, with entrenched competitors who don't need to make a profit on their offerings, so expect fierce competition all the way.
Amazon benefits here by sanctioning a price history tool with restrictions when others could take its place and include its higher margin goods (if you look, there are CCC competitors that aren't sanctioned in this way, but you have to look). Less measurably, the price history tracker provides better consumer experience, in line with Amazon's customer obsession. And finally, Amazon's warehouse space isn't unlimited, so informed consumers who know a particular price is extraordinary may help it free up space more quickly.
But, the ecosystem is really something different entirely, and this isn't meant to be a slight to JS at all. It's just reality when running production code in 2020. Python's standard library is comprehensive, well-maintained and well-documented throughout. JS, by comparison, relies on packages from npm for the same features. Which means the issue my org has with the JS ecosystem is the stuff that's not built into the language spec or otherwise maintained by a central body, not that the things built into the language isn't standing the test of time or something like that.
I hope that explains things.
If you can do it without noise and with 10s of microseconds of resolution, your attack just got much more efficient. And it probably opens the door to timing things more crazy then simple equality.
On the other hand, Python gives a growing and continuously maintained standard library and none of the headaches that, say the JS ecosystem gives.
That said, not all of the features are great all the time. Async/await comes to mind, which adds a lot of complexity without the performance gains even senior programmers might expect. But overall, we're already using features in Python3.8 for projects, and have upgraded our instances to Python3.8 without issue. I guess it's possible we leave some pip dependencies in the dust because they may have some incompatible code with a future 3.x release, but we haven't had a problem before. Tests permitting, we'll do the same for 3.9 if we find something we like or might wait a few years.
You can check a lot of those boxes by 1) some content on your website describing previous projects (like whitepaper PDFs or long-form blog posts), 2) GitHub projects, 3) references/testimonials. Then give a giant call to action form including asking for a phone number (I hate giving out my phone number, but it seems like everyone requires it, so I imagine it would help you more than not).
Note that these needs are very different then what I'd need from an employee. For instance, I can invest in employees and give them time to learn our tech. For consultants, I can't.
> And, yes, it turns out that Telia's client does not attempt to verify the remote server's [customer's router] public key ...and then... Using malicious SSH server to trigger server side RCE !!
> First, Telia did not have a PGP key and did not know how to use it, so instead they asked us to ZIP the report with password and send the password over a separate email (private GMail). I hope Telia's engineers will be reading this article, so I would like to explain why the report should be encrypted. !!
> Thank you for the information. We will continue to check whether you made your report legally without violating any law. And we will ensure that no fake information will be published that could do any harm to the company's reputation and to the critical part of Lithuanian network infrastructure. !!
> And finally, we found that the hash was cracked and was available in the old "weakpass" database !!
And, the bonds in question will yield ~1.5% at today's rates. In other words, less than inflation. Meanwhile, McKinney has lowered property tax rates in response to higher appraisals (inflation is a major driver of increased appraisals on balance).
So, I take 2 issues with the article. First is the payback period, since property tax revenue only makes up 1/2 of the ex-services income and will increase with inflation. And second, with the idea that every area must cover its own expenses. In general commercial, high-dense and/or rich areas subsidize projects in other neighborhoods. You're going to be able to cherry-pick a project that can't be paid by its beneficiaries in every single city.
[1] https://www.mckinneytexas.org/ArchiveCenter/ViewFile/Item/22...