skysight-inc/HackerNews huggingface dataset:
SEEKING WORK | St. Louis, MO | Remote or Onsite

I've spent the last 13 years designing and building mission-critical software and data solutions for customers in the Financial Markets, including Fortune 500 companies, Investment Managers, Hedge Funds, Venture Capital, Private Equity, and Data Vendors.

I've successfully developed cloud based web apps, custom dashboards, automated trading algorithms, factor replication & backtesting, quantamental process automation, distributed financial data pipelines, low-latency and high-throughput market data systems, natural language text analytics, Business Intelligence/Data Analytics, software/data architecture including micro-services, front, middle, back office automation, network security, and ETL systems; these systems are used in production environments around the world.

(Email) hn (at) ryansmccoy (dot) com

(LinkedIn) www.linkedin.com/in/ryansmccoy

(Personal) www.ryansmccoy.com/

(Portfolio) github.com/ryansmccoy

By Programming Languages: Python, Javascript (Node.js, Jquery, React), R, Shell (Bash, Cmd, Powershell), Visual Basic (VBA), Java, basic C++, Go, C#

By Platforms: Amazon Web Services (AWS), Google Cloud (GCP), Linux (Ubuntu, CentOS, Debian, FreeBSD), Microsoft (Azure , Office 365, Exchange, Windows, Windows Server, SQL Server, Hyper-V), Hashicorp Terraform & Vault

By Data Engineering: RDMS (SQL Server, Postgres, Sqlite, MySQL, KDB+, TimescaleDB, BigQuery, others), NoSql (Memcached, Redis, MongoDB, Cassandra, others), Message Queue - RabbitMQ/Celery, ØMQ, Apache Kafka, Big Data - Apache Spark, Airflow, Beam, Snowflake, Machine Learning, Natural Language Processing - Gensim, NLTK, Spacy, ElasticSearch, Solr, Lucene, Web Scraping
Orbiter anomaly detection is for any DB (e.g. Postgres, Snowflake) and metrics that business/product teams tend to track such as transaction conversion %, user growth, add item to basket %, etc.

Amazon Cloudwatch anomaly detection is for AWS resources & apps, and covers infra metrics like resource utilization, app performance, ops health.

In terms of the anomaly detection capabilities -- both are using similar machine learning processes to detect metric issues automatically!

P.S. If you get curious about the details of our solution, we have a 2 minute video demo ;) Cheers! https://www.youtube.com/watch?v=R7P_M6j0P2A
I qualified my original statement by saying "I think this depends on the state". Although now that I think of it, the laws in the states I know also say you can be made to pay back the costs if it is determined you could afford an attorney, however I have never seen anything done about it.

So I think you're right, it is perjury that doesn't really get anything done about it - I think based on the idea that if you had the money to get an attorney you would do it so anyone saying they can't get an attorney doesn't have the money.
Sure and the salary differential probably trumps those extra vacation days. According to levels.fyi[1], median compensation package for a software engineer in SF bay area is $237,000. That is a very big number even accounting for health insurance premiums, California taxes and the cost of living here. Can you please share a few European locations which offer a better deal than this? AFAIK: London has shitty salaries and slightly lower CoL than SF, Paris / Berlin / Barcelona have even shittier salaries with much lower CoL but higher taxes, Zurich has comparable salaries and lower taxes but as much or higher CoL.

[1] https://www.levels.fyi/Salaries/Software-Engineer/San-Franci...
I think it's really positive that these companies / networks open themselves for startups, still it would be better if they would try to change their companies so that all startups have a fair chance to work with them. This would be beneficial to them as they would have a larger sample to choose partners from. Right now these VCs present maybe 50-100 companies to them (LaFamigila for example has 34 investments as of now, I think), which is still a very biased and restricted sample, so they are almost surely missing out on some great innovation opportunities.

Doing B2B sales to large enterprises in Germany I found that it takes a lot of side channels & social engineering to sell into large organizations as a startup. Maybe this is just part of the "game" but I can't stop thinking that those companies miss out on so much innovation because they simply don't have good processes in place to systematically and fairly build relationships with small, innovative tech companies.

Founders from different regions, how is your experience with this?
You've missed the point. I'm not talking about processes at all. I'm talking about the relationship and trust between company management and the team. That is the core problem here. If management want to play Command and Control the whole time and your team is happy to be treated like children, then no, you can't do scrum in any meaningful way, and yes it will suck.
If you want to compare worst or average of the US, why not compare it to the worst or average of Europe - say, Romania or Spain or Moldova or Greece? Why compare it to one of the best places in Europe?

Or, to use your words - the Germans will always be better off in Europe. But everybody else, not so much.
When what you are requiring is your own additional method?
> Dangerzone can optionally OCR the safe PDFs it creates, so it will have a text layer again

I'm not completely sure, but wouldn't this parse links and make them accessible again, possibly even clickable?
I so dislike questions like that. In my opinion, a job interview shouldn't attempt to judge someone as a whole person. It should measure their ability to perform the job, nothing more. If a lizard showed up and demonstrated that it can perform the job, I'd hire the lizard.
Agreed. Wasting countless hours on the engineering end doesn't seem wise when those same hours could be spent doing something meaningful. This requires education on the user end. Education that will help them understand the world around them better so everyone wins in the end.
Not archaeology, but I use git reflog constantly as my workflow:

I push to master infrequently. I keep a series of topic branches off of master, one per project phase. For changes that affect other developers, I pull those out and PR them to master, then rebase the topic branch chain once the PR completes. When I switch projects I use git reflog to remember where I was working.

Basically I take advantage of git rebase and use it like time travel constantly. Somehow I stay sane..
Indeed, I was hoping for something smarter, that would remove only the "risky" bits of PDF, but keep the overall structure (and size).
Practically daily. Every bugfix or feature starts with looking at the already done mistakes engraved in the tree.

Though we stand on shoulders of midgets usually, you still get a better view.
Elon Musk's endeavors are more about vanity, I think. I found all the twitter antics to be quite odd for someone in his position.
CppCon 2018: G. Nishanov “Nano-coroutines to the Rescue
The First Week Projections for Lil Uzi Vert, Jhene Aiko and Megan Thee Stallion
We just switched from Perforce to git at work, and about the first 2/3 of a project I work on got squashed together. It took me less than a week to bump in to that "initial commit" when trying to figure out why a bit of code is the way it is.

"git blame" (or the p4 equivalent) is my usual archaeologic tool in this context, but "git bisect" has been very helpful in others. For the first, it should be easy to look at your current codebase in SVN and see how far back the history goes in any particular area. I've found that bisection is most useful for relatively recent history, because I usually have wanted to build or run the software to test for a bug or something - beyond some point in history that becomes impractical.

Moving from SVN to git shouldn't require losing history though...
Frequently. Whenever I run into something that makes little sense to me, I go back and look at the commit messages, the related bugs, the evolution of the code, and who wrote it.

It's called software archeology. It's not important if you keep exactly the same people working on the same project and they have perfect memory. But if you, say, move people between different teams, or lose people, or hire people, it's a gold mine.
Lots of the value for me is in well written commit message bodies.

Especially if I have written them since when someone asks me how something works or why it's written that way I can read the commit body and explain it to them/refer them to the message (otherwise my answer is, I don't remember!)

Additionally if you choose your changes well and don't squash commits it can be a good guide to what else touches the thing I'm looking at.
If your ticket explains why the query is slow and suggests an alternative that would be faster I'd welcome that. If anything, I would expect a good DBA to do that.
> The hardest part of Emacs is to learn what Emacs can do, what it offers.

Nah, for me the hardest part is finding out about all the things it doesn't do. Unless you code it. Maybe you find some half-arsed packages, but they might just make you more frustrated.

For example, I still haven't found a way to do vim-like completion. I still haven't got a good cscope interface that doesn't crap all over my windows (a common problem for many things in emacs, not just xcscope). I still haven't found a way to make my custom keybindings just work everywhere; every so often I happen to end up with focus in a window where, for example, my normal window navigation bindings don't work and I'd have to go out of my way to fix it.
If a doctor were to ask a patient for 100k$ or they won't do a life saving operation, then the patients consent is fabricated. Their need for a life saving operation is the third party.

I think you misunderstood what I mean by third party; it's not necessarily a person, legal or natural, interfering with the transaction, it can be a force of nature, circumstances and many other things. It won't go away because you don't like it.

And yes, there is such things as "coerced by circumstances", see above example. Normally, when you buy food, water or medical care you're not in a life threatening situation or perceived or real emergency. If you are then you cannot give informed and free consent, simple as that.
I regularly find myself trawling back through code that's 5+ or 10+ years old, and the best way to understand a detail of code can be to look back to the commit message where it was documented.
Last Week on My Mac: Deceived by the Finder
Cann't bitlbee switch to that scheme Ripcord uses, with an auth token taken straight out of a web request to "normal" Slack in the browser? Or is Slack going to plug that hole as well?
One of the more frequent uses of source history where I work is to see when an issue was introduced to help gauge the priority of a fix. When something is discovered and someone wants to make it a stop-the-presses fix-it-now type thing, we look back in history to see when the change was introduced. If it's been there a while, and especially if an external customer has never created a ticket on it, we come back and say, "Well, it's been that way for five years now, so why don't we just put it into the next scheduled release instead of an off-cycle emergency fix."
Again, this means you have a broken team and not a broken tool.

In the situation you describe, there are three possibilities: either the new dev makes a reasonable estimate and everybody else is wrong; the new dev is overestimating and more experienced devs are able to see that; or the new dev is not yet familiar with the point scale in use.

In the first case, great! We expose some hidden complexity in a system that might be taken for granted by the existing developers, and this helps refine an estimate for the new team structure. In the second and more likely case, we can respond by tightening up the scope and specification of a task to make it clear what is in and out of scope. And in the third, we can work to make sure the new team member gets a feel for the sizing system in use, which tends to take a little bit of time when changing team makeup.

These are not rituals and they are not unrealistic. They are specific tools aimed at solving real problems. It’s no surprise you have a bad experience if you are this aggressively dismissive of them.
+1 for git bisect, criminally underrated!
I often wonder:

- What is this trying to accomplish?

- Why are you doing it this way?

- Why not this other way?

Ideally these things would be answered in comments, but they often aren't. The commit message hopefully answers #1, and it links to the code review tool which may shed light on the others.
Taiwan sets up 60 face mask production lines in a month
I'd second that. I've also used old revisions to try and figure out when a particular bug I've found was introduced too.

Depending on how long it's been there can help you assign a priority, e.g. minor bug has existed for 10 years without anyone noticing is probably not something you have to fix right now. The opposite of that is a nasty bug has existed for 10 years until some data structures or control flow changed and exposed it, so it's not a hard and fast rule.

Once or twice I've seen bugs be introduced by merging huge commits from another branch, so there's lessons to be learned from history too. In this case, avoid large merges with conflicts, especially something you cherry-picked.
Yes, every day. Well-written commit messages are like comments that never go out of sync with the code they’re attached to. Often it’s the stuff from years (vs months) ago that’s the most valuable, because that’s the information that nobody who still works at the company can remember.
Bubonic Plague Strikes in Mongolia: Why Is It Still a Threat? (2019)
Echoing mates here, a written conversation can be supportive though I offer as an experience is to make the conversation friendly, interactive, use of simple phrases and avoid proverb/slang and getting a recap at the end could be constructive.
I'm working in a travel startup, so this is quite scary. I hope that travel picks up quickly once the initial hit is ingested. But honestly right now I worry more about the health of older relatives than my job as a developer.
First, understand that DevOps is not a tool, process, or methodology. It's a philosophy. There are many elements of this, but the most important ones are IT infrastructure, the cloud, scripting, and knowledge of the various DevOps tools (AWS, Docker, Ansible, Kubernetes, Jenkins, Chef, Puppet, &c.) You don't have to know all of those tools, they are dependent on what you want to do and what your software stack is all about.

I think a good first step is upping your bash/zsh scripting game, and making sure your infrastructure chops are good (TCP/IP, HTTP, etc.)
While 30 days vacation is kind-of standard, the statutory minimum is 20, and I've had job offers fresh out of university where employers offered me only 26 days.

I knew that I could easily get another job offering the "standard" 30, but I'm sure that quite a few graduates fall into that trap.
What about DDG? Has their quality increased by your metrics?
Molto – Mission Designer
Some of these JPEG features are great for optimising JPEG resizing, which can be significantly faster than fully decoding the image then resizing.

https://github.com/mattes/epeg
It has nothing to do with size and everything to do with politics. Plenty of small countries have crap internet too.

Australia's internet sucks because the conservative government nerfed the NBN plan.
Nice desing
> they haven't transitioned from SVN to git solely because of the logistical challenge of migrating 30 years of commits

lol, I don't think that's the reason. At the only place I worked that used SVN the real reason was that the old guys didn't want to learn something new.
If locking down a whole city - "cordon sanitaire", doesn't work, why did Italy just do so? Do they not have the same public health experts, or were they educated at different schools.
Along these lines: git-log has a --grep option which returns only commit messages that match a regex, and git-grep searches over revision controlled files like above.

>I like to work on small systems and prevent them from becoming large systems.

This is very wise!
> Yes, I think most of us are dismissive of some values of some others and that's OK.

I don't believe this is a very useful property of a conversation which is about trying to understand how the world squares with opinions that people can hold.
5% Nationwide will require ICU care. That's 18.5 million people.

No, that is not what the CDC says, and it is not even remotely what your link says.

It says "5% of those who contract Covid-19" would require ICU, which is .5% of those exposed to Covid-19, which is itself a small subset of the population.

You're off by well over two orders of magnitude!
Nothing of value in that article, just an ad for the app. I don't think installing one more app is going to improve my habits.
Our codebase is around 20 years old and was in CVS, then SVN, then git. Then several years after git, a new git repo without any history due to poor use of the first git repo (someone added binaries, bloated the repo to GBs instead of maybe 200-300MB, which made git export horridly slow).

In all the steps we preserved the commit history, except for the final git->git. However also when we moved from SVN to git we kept the old svn server running as a historical archive for several years, as we didn’t carry across all projects (some were already EOL’d years ago).

During that time I looked at it maybe twice, and ultimately we decommissioned it.

Likewise with the new/old git repos, we still have the old git repo if we need the history.

One final thought: git blame was nice, until someone reformatted the entire codebase and committed it back in (we’ve since adopted better git workflow and code review practices!)
That's fair, state level they're all as corrupt as each other, but Labor is still a union base.
Libs are more cosy with banks and business in general.(and pro privatisation)

I dunno about the left saying that though. I see it most from people who aren't really into politics in general justifying their lack of interest in voting. Definitely agree on abc having a weird split identity, but that's due to external pressure and a lack of funding.
Couldn't DDG use the users location in a non evil way instead of not using it at all, like 1998 Google?
I don't see how MDMA can be useful for exploring relational issues. It's primarily a controller of emotion and mood, not a psychedelic.

So all it's going to do at best is make a client artificially imprint on the therapist - because the client would experience intense emotional closeness after it was administered, followed by a real downer after the session.

I'd consider that abusive by definition. It's certainly not going to have the much broader and risky but potentially more productive ego softening effect of real psychedelics, which would focus much less on the therapist and more on the client's interior world.
>As a devoted emacs addict, I can attest that plan old emacs is also pretty slow and clunky

it's true in the sense that it's true for almost anything once you start to add a plugin or two or add personal customizations.

The only thing for me that is actually consistently, superfast is terminal vim without any plugins. Which is too barebones for my daily use.

In a realistic, daily working environment with all my stuff loaded emacs is clunky, but not necessarily slow. It's honestly still pretty responsive.
Very rarely, beyond a couple weeks of commits. In those cases it is more a question of "did some particular commit hit branch XYZ?". I wouldn't call that source-control-arachaeology.

I'm at the stage where if someone suggests that we try to keep a linear history in git I push back and argue that it isn't worth the extra effort compared to the gains.
The number of accusations of rape is absolutely tiny compared to the number of sexually active couples, which proves that "a lot of women" don't redact consent.
What I heard is that it does not stop the virus, but it does slow the spread, which is key considering that we are currently in a flu season. If 40% of the population is going to get infected, it's better to deal with them over a couple years than have them show up all at once.
Show HN: HTML to PDF API with Chrome Automation
There are numerous comments showing why git history is useful, but I think nobody mentioned this.

In Goland/idea you can look on the git history of only the selected code. I use this constantly to see how the code has been previously modified before I make my own changes.
nice. But why are you attributing tesseract solely to google when it was initially developed by HP ? Does it help marketing nowadays?
What? I expect to get drivers even after the sun explodes
I'm sorry, but a scorecard where Uber, of all companies, gets a perfect score, simply isn't credible to me.

Remember, that's the Uber that tracked people, identified by name, and showed their location to guests at a party on a map. Just for entertainment.

It's the same Uber that has had so many privacy and customer data scandals, I have lost count.

But sure, they "have our back".
why do I care that this is "cute"? I want a cute puppy, not my software to be cute. If your product has novelty animations, stupid colours or uses emoji's in any way I want nothing to do with that childish bullshit.
A LoraWan Pager
I think React would be a pretty good example of the kind of thing I'm talking about, actually. Just to be clear: I like React and I'm building a product with it right now of my own free choice. It does what it was built to do very well.

The point I'm trying to make is that people often think in absolute terms. The problem isn't thinking "React is good for SPAs" - it's thinking "React is good for all websites". I've come across a number of engineers now who genuinely think React is a good fit for e.g. totally static sites, "because it's fast".

I've come across similar persistent beliefs around NoSQL databases. Some teams wouldn't begin to consider an RDBMS for their primary data store, even while their data is heavily relational - because "SQL databases don't scale".

It's not that technologies are good or bad - it's the blind belief that a given technology is best for all situations. The hype drives the development. Not of the underlying tech itself, but in the teams using that tech.
MBS review: why Trump and the west took a pass on the Khashoggi killing
Or in guessing have patients who have the flu and covid concurrently.
https://www.discovermagazine.com/planet-earth/mammals-made-b...
Speaking of "proximate vs. ultimate causality", WHY did they make "an unstable plane with a dangerous MCAS"?

The answer is to reduce emissions. That must be acknowledged if we're also supposed to acknowledge the cost pressures mentioned in the article.

Both the reduction of emissions and the effort to avoid retraining are regulatory impositions.
> how many mainstream platforms and physical stores allow porn to be prominent

Less than 15 years ago, it used to be common in UK supermarkets for there to be a section at the entrance dedicated to newspapers and magazines. A good section of the top shelf would feature porn magazines. The printed covers of the magazines would generally be masked with some cardboard, so you couldn't see the explicit content by mistake, but could still see the title of the magazine.

Print media is generally in decline, so these sections no longer exist in quite the same form as they used to in supermarkets, but this is as prominent as it needs to be. In the past, this meant it was (literally) out of reach of children, but still readily available to adults, and only if they reach for it.

Why isn't that acceptable anymore?