3pt14159

This blogpost reminds me of the type of content that was more frequent on HN back years ago.

I am not ashamed of pumping OpenAI in general and ChatGPT in particular. The sheer amount of technological heft they've brought in such a short time is breathtaking. I've literally had an hour plus conversation, by voice, with ChatGPT and I was engaged throughout the entire affair. The tech isn't perfect when it comes to some things like links and what have you, but what does work is short of a miracle.

I do love a good joke, but this one falls a bit flat.

Logically speaking, the second bar tender could have thought to himself "no I don't want any beer, but one of these two other guys may want to double fist" and so there is really no way for the third logician to answer in the affirmative.

Have you checked out this section of the docs?

https://docs.flagsmith.com/clients/server-side#get-flags-for...

I work for Flagsmith these days, but formerly I was in charge of managing a lot of Trust and Safety related concerns for Clubhouse. This involved deleting a lot of records to appease regulators and creating custom features to handle stuff like CSAM and we used a lot of feature flags there to keep systems safe in case of an event.

The most important architectural decision that we made was pushing some of the feature flagging into the software layer. So, for example, every task had a module name and a task name that together would form the feature flag name. So out of the box any task could be disabled without adding further code. Combined with other good practices it went a long way. Another good option is to enable local evaluation mode[0] which allows a balance between keeping your feature flags up to date while avoiding API calls frequently.

[0] As an aside, I've worked on the implementation of local evaluation mode for one of our clients (I think Python?) at Flagsmith.

Thanks for letting me know! Really interesting stuff.

Oh really, that's news to me. I thought one could always read the video frames one at a time.

If an ad can be rendered on a page or if it uses audio it can be blocked. We have it easy right now with how trivial it has been to block ads, but we could face off against rendering and wiping them in real time if we need to.

I've never heard of it and I've been using Python since around 2008, including mathematical stuff like Scipy / Numpy. Sometimes people like to find old stuff and share it since it's new to others.

Something like meta.com/our_own_tech_handles_this

What do you use GPT4 for?

The reason I ask is that ChatGPT is helping me debug docker files and a lot of the times I find really hard to Google answers there. Sometimes it waves me away but usually with promptings for more information to go on first.

Since it's documents in question are those that are part of the boardroom drama it's at least understandable that they weren't released. I know it's fashionable to slag on OpenAI but I haven't given up hope in them. They've made a lot of discoveries public over the years and while it may be frustrating to wait on some of the releases they're still going to be released eventually.

The problem is that there are many of these planes that have already been delivered. They're going to have to find some way of ensuring QA for those before they're allowed in the air again.

Naw, I wanted to memorize certain ones. It's worked though. I'm pretty much there with all of the ones I picked.

Sure, it's a bit of a random list since it's not selected beforehand, but here are them:

- Romans 6:3

- Proverbs 16:9

- Matthew 5:9

- Galatians 5:22

- Galatians 5:6b

- Isaiah 55:9

- Psalm 117

- Psalm 23 (this is the largest one)

- Matthew 9:37,38

I'm pretty sure I've since memorized all of these so it is time to add more verses into the mix!

I did something similar that I hand wrote but it's different verses from the Bible whenever I cd into my main working location. It helps me memorize verses slowly over time and it's not too intrusive though occasionally I'll disable it before pair programming on something with a colleague since it feels inappropriate at work to force someone else to put up with it if they have qualms about it.

I remember watching it and I was pretty impressed, but as I was walking around thinking to myself I came to the conclusion that there was something fishy about the demo. I didn't know exactly what they fudged, but it was far too polished to explain how well their current AI demos preform.

I'm not saying there have been no improvements in AI. There is and this includes Google. But the reason why ChatGPT has really taken over the world is that the demo is in your own hands and it does quite well there.

Yes. And also, it's bad PR for the team responsible. Managers don't want to have trouble hiring people. After the first fine, the message can be "we're modernizing to stop this from happening!" But getting multiple fines over years is going to make the best of the talent poor essentially unavailable to hire.

Location: Toronto, Ontario

Remote: Sure, but in person is good too.

Willing to relocate: Yes

Technologies: Python (Django, DRF, SciPy), Postgres, Rails, JavaScript (Vue, React, Ember)

Résumé/CV: https://docs.google.com/document/d/1cq6DaK2MmwKEtlbq5O_G9qV-...

Email: zachaysan@gmail.com

Senior backend software developer with experience on big systems with a Nasdaq subsidiary, multiple mid-tier social networks, data science, and Trust and Safety engineering. Experience leading other developers as well, but also happy as a run of the mill backend developer. Enough JS experience to fill the role of a fullstack developer, but too weak on CSS to fully make that claim.

Nothing stopping Apple from working in SSH fingerprint gossipping with an opt-out option for weird corporate people. I already trust Apple to secure my computer and my SSH client I see no downside to protecting this threat vector automatically too.

I was disagreeing that it is easy these days just as it was back then. Back then it truly was much easier to get traction with a new product. Basically, we're post-land-rush now. There are still opportunities, but back then it was really easy to get through doors and startups were celebrated and a lot of easy opportunities weren't yet seized on the web yet.

Right but you're basically proving his point with the ChatGPT example. There was no way that was coming out by bootstrapping. They've received tons in funding and pay-for-use was sort of a built-on based on all the hype about what it could do compared to the competition.

I dunno man. I sold a small company back in 2011 and it really was easier back then. Three out of four of our first leads tried to buy us because we were doing "real" machine learning. This was almost a pure API app. We didn't even have documentation we just told people we'd integrate it for them.

It is harder these days. Also, the product you mentioned "custom mobile app for housekeepers in rich families in the UK" I don't know how you're marketing that, but that seems like the hard part to me.

As for Twitter, people forget what it was like back when they were first starting. There were a ton of people you wanted to follow, but RSS couldn't handle the sheer numbers involved. Blogging had become so big and realistically you could only follow, say, 10 bloggers before being worn out with all the content. Twitter made it possible to get little nugget sized updates from thought leaders without having to eat the whole sandwich of some massive blogpost.

I had this phase where I tried to do everything the right way. I used to check whenever I thought I could, including to my own servers. And you know what? 100% of the time the check passed.

After a while I sat back and thought to myself "is this really worth the cost in time?" And I concluded that no it wasn't. Plenty of people run scanners looking for bad stuff online, ranging from poisoned SSH to supply chain attacks on OSS. These are the people that find the baddies and the baddies eventually get targeted. Me as a lowly developer is just not spending time fruitfully by checking github.coms SSH fingerprint. It would be better if I scanned the web app that I'm working on for, say, SQL injection bugs or misapplied CORS headers or whatever else.

Ultimately security checks are an economic activity. The likelihood you are targeted via a given threat, the payoff to the attacker if you are targeted, the downside to the attacker if they are caught, etc. I think being realistic is prudent.

The problem with this type of thinking is that it undervalues the role that non-vital communication has in social species. Look at uncontacted peoples around the world. They've had music and dance even though their tribes consisted of a couple hundred people. These forms of communication serve a role in their communities but it isn't "there are fish in the pond over there" it's more special and abstract.

If we are to treat whalesong the same way then we can't immediately assume that they're just trying to communicate base concepts.

If you are calling something immediately, a try-except is ok. If you are calling with a try-except just to simulate hasattr or getattr then why do we have the built-ins in the first place?

No, no, you misunderstand. I agree with the point. I just think it was made against a strawman and could have been made even stronger. I'm not for metrics on stories to award productivity points. I'm for one-on-ones and success-as-a-team evaluations.

Well, I like the story here, but it's kinda against a bit of a strawman. Don't get me wrong, I'm not losing the overall point of the piece, a point I agree with, but that said a metrics focussed manager could have simply added an "adjunct" label to the stories and had this "worst programmer" add themselves to stories as the non-lead developer.

Ultimately the best way of measuring programmer productivity is by the assessments of the programmers on the team. This isn't as easy as it seems. For example, I once worked on a team where the best Heroku guy just had the absolute wrong idea about "easily understandable python code" since he would prefer to raise and catch an exception instead of rely on a built-in to test attribute existence or type compatibility. But nobody could get around large scale Heroku deployments like this guy. The juniors understand this nuance less well than seniors do, but even so, it does sorta come out in the wash. Your team does know its best people and they're usually happy to say it in a private one on one.

Expiry isn't the issue. In America (and Canada I'm pretty sure) you have the right to use a patent at a fair cost determined by a court. Or you can try to just use the patent anyway and wait for the court case to come to you.

Just imagine he said "say" or "for example" and see how it reads to you. This is internet work, not serious business.