Comments URL: https://news.ycombinator.com/item?id=41167744

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=41164879

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=40963612

Points: 94

# Comments: 84

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.

I'm curious on the need to do use selenium script to google to iterate, here's my script: https://gist.github.com/bobbywilson0/49e4728e539c726e921c79f.... Just uses the api directly and a regex for matching the title.

Thanks for sharing!

repo: https://github.com/bobbywilson0/hn-whos-hiring

Comments URL: https://news.ycombinator.com/item?id=40877158

Points: 8

# Comments: 2

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

[1] - https://hackaday.com/2016/02/01/3d-printing-fumes-new-scienc...

[2] - https://www.cdc.gov/niosh/newsroom/feature/2022print3D.html

Comments URL: https://news.ycombinator.com/item?id=32215854

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=32114730

Points: 2

# Comments: 0

    1. Business Entity
    2. Business Bank Account
    3. Accountant
    4. Invoicing software
    5. Contract
    6. Workspace

Good Luck!

[1]https://medium.com/@bobbywilson0/six-steps-to-start-a-consul...

Are folks using these kind of things for non-trivial production applications?

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.

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.

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.

You should consider with RSA keys have a limited size message that can be encrypted (e.g. for 2048 bit keys you are limited to 256 bytes in your message). My solution was to use the SSH key to encrypt the secret I used to encrypt the message with.

Comments URL: https://news.ycombinator.com/item?id=4565398

Points: 1

# Comments: 0