That reminds me of something sort of similar I observed. I was driving with a friend who drives all day for a living. He said that the fellow drivers told him that if you want to get over and you're in heavy traffic, roll down the window, and say "Hi there, do you mind letting me in?" I watched him do it and sure he showed me putting on his blinker didn't work at all, but the direct ask always worked.
Is that assuming windows are rolled down or do they just speak nice and loud? I'd consider most drivers in my area to be relatively easygoing in heavy traffic but this sounds fun to try nonetheless.
Cool analysis with GPT-4o! I was doing some messing around with the same dataset recently around the "Who is Hiring" and "Who wants to be hired". Although I was just using pandas and spacy. (I was job supply and demand with the US FED interest rates here: https://raw.githubusercontent.com/bobbywilson0/hn-whos-hirin...)
I can actually see how nice it would be for an llm to be able to disambiguate 'go' and 'rust'. However, it does seem a bit disappointing that it isn't consolidating node.js and nodejs or react-native and react native.
What the author could have done, and what I should have (but didn't) also, is add a bunch of possible values (enums) for each possible field value. This should solve it from coming up with variations e.g. node, nodejs
In zod/tooling it would look like this;
remote: z.enum(['none', 'hybrid', 'full']),
framework: z.enum(['nodejs', 'rails']),
But this just shifts the problem further down, which is now you need a good standard set of possible values. Which I am yet to find, but I'm sure it is out there.
On top of that, I am working on publishing a JobDescription.schema.json such that the next time the models train, they will internalize an already predefined schema which should make it a lot easier to get consistent values from job descriptions.
- Also I tend to forget to do it a lot recently in LLM days but there are plenty of good NER (Named Entity Recognition) tools out there these days, that you should run first before making robust prompts
This seems to have a similar problem in the Apple notes calculator where items that you set to as a variable in the new calculator mode can’t have spaces or any other delimiters.
The training data or some kind of enrichment of the data would have to make the systems understand node.js and nodejs are the same just like on the new notes calculator Apple-sauce = $2.50 * 8 makes the first statement a variable.
I recently purchased a 3d printer, and I looked for articles talking about the risks associated with PLA fumes. This article[1] seems to be popularly cited, which includes the statement "PLA doesn’t look like a problem." I think this is what in my experience has been largely the sentiment when I have asked around, and read forum posts about the topic. At my local library there is a makerlab space, they are free to use and they basically run them non-stop uncovered in the room.
One of the other points I found interesting was that someone mentioned that a lot of the printers are manufactured in China where there isn't as much regulation around required safety warnings. However, NIOSH does have a short page[2] on 3d printer safety.
In my mind as a new hobbyist it seems like the combination of two issues.
1. The way 3d printers are currently designed and marketed is primarily an open-air style that can be used just out of the box. Enclosures are usually at least as much as a consumer level printer, and you need to have a way to vent it to the outside.
2. The thinking from the community is largely "PLA doesn't look like a problem" and only use an enclosure for ABS and more toxic materials.
I understand the comments around hobbyists shouldn't be the ones designing filtration systems, but it does seem reasonable to
I know that if I print PLA and stay in the room, it will give me a headache after a while. And I can definitely smell it, so at least something is getting released into the air. I don't know if that actually means it's harmful, but I stopped staying in the same room if a printer is running.
In over a year I've never noticed a smell from PLA during a print.
Maybe that varies between manufacturer, some "PLA" filaments are actually weird mixes (like PLA+).
Agree; with PLA there’s a definite recognisable smell.
Also, when I first got my printer, I had it running in a corner of my office room and found I would reliably get a sore throat after a few hours printing. It’s now shifted to the basement with a extractor fan nearby.
IIRC, enclosures aren't common on consumer models because there's a patent on that design. Not sure if the patent has expired or not but with the trend already in motion, consumers are accustomed to open air printers. Printing the parts for an enclosure is also a good way to break in a new printer.
Yep this prevented any commercial options. It's why the Ikea Lack became so popular as an easy and low cost enclosure to make - I've got one for my Prusa Mini+ and it obviously does nothing to help with venting.
Enclosures aren't common on cheap bed slinger (the ones where the bed moves in the Y axis) because they would need to be much bigger than the print area. CoreXY machines are more likely to be sold with an enclosure.
I have just written the first steps for starting "solo dev" work. The tl;dr is:
1. Business Entity
2. Business Bank Account
3. Accountant
4. Invoicing software
5. Contract
6. Workspace
My post[1] includes more detail, and I have also written about finding your first clients as well. Feel free to follow up in this thread with any questions.
My main purpose of tools like these has always been prototypes, or hobby one-off type stuff. For SPAs, or a sketch with a Jupyter notebook. They're great for this sort of thing because in my experience, this used to require building some sort of API just to get a simple json interface to the database. It was my understand that the purpose of these types of tools was mostly that.
Are folks using these kind of things for non-trivial production applications?
disclosure: I used to work at Galvanize as an instructor, a couple years ago.
I don't have any connection to Galvanize now so I don't feel the need to defend or promote bootcamps, but I do feel like I have some knowledge on the situation. When I was instructing I was constantly worried about there being enough jobs for my students. This was also when the startup market was "hotter" than it is now. The thing that I came to realize looking back is that there is actually still a huge amount of steady demand for software engineers.
It isn't necessarily startups though. I have definitely heard from startups that they feel like they are inundated with bootcamp grads. I think part of the reason is because working at a cool startup is part of the picture that is painted to perspective students.
The less exciting (to the graduates) opportunity is working with big companies that are replacing their previous outsourced staff with internal junior engineers. They also didn't want to hire one or two grads, they were interested in hiring five to ten.
To me at least it seems like larger companies are trying to adjust their staffing to accommodate a more fluid staff that comes and goes rather than the longer term employees of previous generations. Which includes always having a broad opportunity for new employees, which dovetails into the bootcamps constantly producing graduates.
I always got the impression that most of the truly entry-level software jobs (the kind where they routinely hire people with associates degrees or no degree) are in unglamorous companies, in cities all throughout the country, writing code in unsexy languages like SQL, C#, and J2EE. These companies don't typically try to pretend they only hire the top 10% of the entire industry, and they're willing to train people on the job. They don't pay the big bucks, but it's better than working at Kroger.
Unfortunately the narrative of "you too could be writing ugly line-of-business applications for $40k/year" is not an exciting sell, as you've said, to people who have watched a few episodes of Silicon Valley. So there's an expectation mismatch. We want to point at the Bureau of Labor Statistics about openings in the software industry and think that they're about changing the world with node.js and AWS lambda, because that's a more promising vision of tomorrow that doesn't involve encountering Windows Server 2005 in the course of your daily work.
Sure, doing your time in those sorts of places and then moving on is a good approach. That's more or less what I did. (I went to college for CS, but I'm oldish.) But those jobs can suck for reasons that don't really have anything to do with technology.
While you're unlikely to catch me extolling the virtues of cool-guy startups, they do tend to have the benefit that they "get" developers and bias towards facilitating the work rather than the endless bullshit you tend to get sucked into in the bigger places.
Most, if not all of the previous tech they abandoned seemed too early at the time. It forced those who were making products for Apple to follow their lead. Apple has always tried to reduce clutter with design, and a lot of that times it means getting rid of something that doesn't seem like it need to be removed, e.g. limited ports, no removable micro sd for iPhone, wireless devices and accessories, removing drives, soldering in laptop parts. There is a population of people that absolutely despise Apple for doing this. This seems like a classic 80/20 situation where the 80% don't have the need for a headphone jack or are willing to use wireless headphones and be fine with that. While the 20% are upset because like many of the replies below people have specific use cases for why they need it.
It is more likely that we will see other manufacturers drop the headphone jack as well because Apple did. Again, most people will be fine with that. Bluetooth headphones and ear pieces have already been around for awhile. You also have to think about Apple's purchase of Beats Audio.
With that said I will concede that I am also a bit bummed about them removing the port now as well, but I have learned that Apple is incredibly stubborn when it comes to listening to their consumers about these decisions, and you just have to abide, or buy something else.
Since I have worked on something similar, in my opinion, it isn't the downloading software that is necessarily a hurdle (although I agree that it is a bit of one); it is around the general difficulty and pain around your local setup and finding the user you are trying to contact's pgp key. This has been discussed at length, but I think it comes down to pgp being enough of a hassle that people who aren't focused on privacy/security don't bother using it.
With ssh keys, at least we can assume that if someone has a github account they have a private ssh key, and it is accessible through the github api. With pgp there isn't a guarantee that they even have a pgp key, and accessibility is on the users themselves to publish it in some way. I think that keybase.io has tried to become the go-to spot for pgp keys, but the adoption is nowhere near what github has, and again, someone has to be interested in privacy/security to want to do this as well.
I mean with all do respect that you are correct in terms of a better protocol, and that there are tools that exist that already do this. The concern that I think OP and myself are interested in solving is creating something that is quick, easy, and piggie-backs on top of the huge github userbase and provides a base level of encryption.
I just don't buy it. Using Github-registered SSH keys to communicate is also an idiosyncratic and complicated way to exchange messages (evidence: far, far more people use PGP than use schemes like this). It's also much less secure.
