Kind of off topic but it doesn’t look like there are any tests in this repo. Is that common in the open source C community? I see several people suggesting benchmarks but what about functional tests? I don’t write much C and am curious about community norms.
Sounds like they mean “remote” because chromium uses SQLite and JavaScript loaded into your machine comes from a remote source. So because a website can run JS that can exploit chromium they’re calling it an RCE.
Maybe, but it could also reduce fossil fuels used to operate less efficient cooling systems in traditional data centers. I’d love to see a breakdown on the impact of each approach.
I spend a lot of time in python land and as of late I’ve been using Sphinx mixed with django-extensions graph_models and some hand edited graphviz. This allows the lion share of my documentation to live in actual code and for all documentation to be version controlled, architectural docs can reference real classes and code documentation can reference architecture docs, stir in the ability to hack simple Sphinx plugins in python and it’s been suiting my needs for everything from architectural overviews to operational “run books” and how-to guides.
Cool, sorry didn’t mean to come across as negative. I’m always appreciative when people share solutions to problems they’ve had. Thanks for clearing up some of my questions.
Interesting idea, although I'm left wondering what's in it for the operator of this service? There doesn't appear to be any "about us" or information about what's happening with the data I pipe to this url.
My point wasn’t that they aren’t important, just that the OP didn’t need to feel bad about not learning about them yet. It was meant more to point out that learning the history of how other people solved problems can inform the way we approach new challenges, but that everything was unknown before it was discovered.
I heard somewhere that a computer science degree is actually a history degree in how we have solved problems in the past. Programming is a creative problem solving process, but certain problems took decades to solve and it’s only by knowing the history that people are able to resolve some of these hard problems. Don’t beat yourself up for not knowing all of history and give yourself a break for not being able to immediately solve problems that took dedicated researchers their whole careers in the early days of computing.
Not sure what the author was referring to but, Airflow has gotten better / gained wider adoption during that time and my team started using DBT which saved a bunch time and was new during that period.
Very excited to see this, I've been intrigued by it over the last few months but have avoided it because I was concerned if I built a successful project with it I'd eventually reach a hard cliff in terms of pricing. It's especially difficult to weigh cost benefit of an architecture with a new framework that has specific resource based pricing when you don't have a way of estimating resource usage because you've never used the framework.
So I'm not up on the Lidar industry but $12k for a sensor seems really expensive, but then again from my casual observations Lidar is really expensive. Is there a physical / first principles reason this is true or is it just really new technology?
I feel like this assumes that the errors that might be thrown by a section of code are knowable. For some high level projects with poorly documented dependencies interacting with third party services that are in constant flux it’s nearly impossible to know everything that’s going to happen and try..catch allows you to program defensibly when an assumption the programmer made is invalidated.
Decentralization definitely makes a hard problem, that twitter has barely been able to solve on a monolithic system, harder.
I wonder if Mastodon could take techniques from things like BitTorrent that do a decent job of determining an individual node’s contribution in a decentralized way, like maybe a way for instances to pass hints to one another. For instance if someone is being banned/moderates frequently on other federates instances that might be a hint to block their content. Obviously there’s an opportunity for someone to control many instances and manipulate the system.
I love the idea of Mastodon and I’m hoping people smarter than me find solutions for these problems.
I haven't had issues with synonyms specifically, my praise for it comes more from it copying the full text of websites when I clip them and parsing the contents of hand written OCR scanned notes and being able to search over those.
I use Evernote for ebooks, papers, articles and personal notes. Probably wouldn't work well for movies or large photo albums (I iCloud for stuff like that). I use their chrome extension, desktop app and mobile app and it works really well. It's really nice to be able to search everything I've ever written in notes or clipped on the web. It also has some support for OCR for paper notes, and does a decent job of indexing text in PDFs. I searched for an open source or self hosted solution for a long time, but ultimately broke down and chose a well supported commercial solution.
Sorry, I should have clarified “accidentally downtime”. This doesn’t make anything new possibly, but will definitely eliminate a common way to shoot one’s self in the foot.
So for a project that lacks tests, I’d suggest higher level integration/smoke tests so that you don’t have to modularize in order to write tests. Don’t mock a database, use a “real” test database with fixtures, if necessary use tools like Selenium and snapshot testing. These tests may be brittle and they may not cover all branches. But you’re looking for things like “can a user register”, “can an order be placed”. For http you can use tools like Charles Proxy to record / replay network traffic from real observations of the existing code running.
Start writing tests, change no production code. You need to understand how it works (by reverse engineering its behavior with tests you’ll learn this) and you need to verify your changes don’t accidentally change existing behavior unless the existing behavior is verifiably wrong, and hey, you may find instances of this too, but don’t start making changes until you have a suite of tests that can spot behavior changes. There are times when things that appear to be bugs are actually weird features that the business needs to function. Sometimes cruft is actually a bug fix.
Start with high level integration tests of the most critical business processes. Then, work your way down to frequently used functions/classes/modules. After the whole thing is covered you can start cleaning/repairing, and I’d suggest doing so incrementally/as you’re adding new other features (make sure all new features come with tests).
The ballot-counting
equipment is part of a
broader redesign of Los
Angeles County’s voting
system, which will include
new equipment while relying
on a traditional paper ballot.
So they’re paper ballots but the machine to count them is open source?
I use Apache Airflow with BashOperator for tons of stuff like this, simple web UI for logs/retries, supports dependencies between jobs and when tasks get more complex it’s Python and it supports extensions.
Economically-questionable conclusions: although individual secretive utilities might on occasion make dumb deals,
they'll charge households whatever the market & regulators will allow,
and then charge Amazon whatever the market & regulators allow.
Because most utilities are monopolies that are allowed by regulators I'm not sure that the market's invisible hand has that much of an impact is this particular situation. The consumers who need electricity for their homes don't have much choice here.
What about running the benchmark multiple times on instances of the same type? I get that it would be noisy but lots of workloads run on shared instances so it’s a useful measuring stick in that way.
It'd be awesome if they provided a comparison of other tools on the same hardware like, "on an AWS M4.xlarge instance we were able to achieve 160m/ops/sec when the dataset fit into memory where as redis only did X"
Lacking that I agree it's a pretty meaningless stat.