What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
2
0
0

@steveSteve Bate I've just seen a FEP-34c1 today which uses the TREE hypermedia vocabulary (which I wasn't familiar with) to ask from servers a particular representation of existing collections. Have a look if it's similar to your ideas.

codeberg.org/fediverse/fep/src

@evanEvan Prodromou @smallcircles🫧 socialcoding..

0
0
0
0
0

What is honestly the point of house or car alarms. Literally noone cares. It'd be into hour 3 of people tutting and rolling their eyes before anyone even thought of calling the cops. You could burgle an entire street, fence the goods and retire to a warm non-extradition country by the time anyone came to investigate. We need a new system. Is there a noise that would make you drop what you're doing and spring into action? Or perhaps insurers should offer a percentage incentive? Or if you catch a robber in the act, the po-po should allow you to do whatever you want to them for half an hour. Really go to town on them. Silly makeup, cut their hair, do that really annoying finger in the ear thing. Anything. Say unkind remarks, spin them around until they're dizzy, make them eat a salad with no dressing. Just totally dry salad them. It would serve as a deterrent aswell. Noones gonna be out there robbin' knowing they might get dry saladed. I honestly don't know why I'm not paid for my very great ideas.

0
0
0
0
0
4
0
0
0
0
0
1
0
0
0
0
0
18
0
0
0
0

The software engineer work has changed with AI tools.

AI engineers have already become used to the mode of operation where you need to keep the machines working on valuable things, otherwise they are only depreciating in value.

Software engineers are becoming to be like that as well with AI assistants; they need to keep them working, and not only that, working in a way that creates value.

This has always been what managers have been doing, keeping software engineers productive.

It requires not only different skills, but also a different way of understanding work as it transforms from labor-intensive to capital-intensive.

Have you noticed a change in how you understand value creation when you have a machine creating the value?

0
0
0

The software engineer work has changed with AI tools.

AI engineers have already become used to the mode of operation where you need to keep the machines working on valuable things, otherwise they are only depreciating in value.

Software engineers are becoming to be like that as well with AI assistants; they need to keep them working, and not only that, working in a way that creates value.

This has always been what managers have been doing, keeping software engineers productive.

It requires not only different skills, but also a different way of understanding work as it transforms from labor-intensive to capital-intensive.

Have you noticed a change in how you understand value creation when you have a machine creating the value?

0

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

  • you don't need a bouncer (friggin finally)
  • there are moblie clients that work well
  • you can see backlog when joining a channel
  • you can browse chat history
  • you can connect from multiple devices with one account and nickname
  • if you disconnect, your nickname is still present in a channel you joined, marked as away
  • you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
  • there is a "last read message" marker and it is synchronized between multiple connections
  • messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
  • messages can be redacted (for moderation)
  • you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
  • there are typing notifiers, if you want them
  • there are message reactions, if you want them

here's the things it does not offer:

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

0
44
1
0
0
0
1
0
0
0

生活感のある情報というか生々しい具体的なことはあまり書かないできたんだけど、SNSでまで社会的な属性をひっさげて人とやりとりしたくないのが理由の1つなのかなと今更自分でちょっと思った

0
1
1
1
0
0
0
0

Turns out Amazon had two outages in December caused by their IaaS management slop generator:

Amazon’s cloud ‘hit by two outages caused by AI tools last year’
theguardian.com/technology/202

> Reported issues at Amazon Web Services raise questions about firm’s use of artificial intelligence as it cuts staff

Sounds like things are not going well over at AWS.

> Michał Woźniak, a cybersecurity expert, said it would be nearly impossible for Amazon to completely prevent internal AI agents from making errors in future, because AI systems make unexpected choices and are extremely complex.

> “Amazon never misses a chance to point to “AI” when it is useful to them – like in the case of mass layoffs that are being framed as replacing engineers with AI. But when a slop generator is involved in an outage, suddenly that’s just ‘coincidence’,” he added.

Henlo.

0
2
0
1
8
1
0
0
0

It's Friday again, so it's time for another update on Diesel, the Rust query builder and ORM.

I attended RustNation in London this week. It was a great conference, I enjoined giving a workshop on Diesel there and had quite a lot good conversations with different folks. If you are interested in attending a Diesel workshop the next one will in in May in Utrecht as part of the RustWeek.

Nevertheless it was a busy week for Diesel as well. We received 9 PR's and 1 new issue. This might be a new record.

0

오래 기다리셨습니다!!!

BlueBase: Python으로 밑바닥부터 직접 만들어보는 DBMS

https://theeluwin.github.io/BlueBase/

결국 완성은 못했지만, 일단 공개할 수 있는 부분이라도 공개합니다.

RedBase DBMS을 구성하는 PF, RM, IX, SM, QL 중 PF와 RM을 여러분들이 직접 구현 할 수 있게, 과제의 형태로 제공합니다.

PF는 paged file의 약자로, file을 page 단위로 관리하는 컴포넌트입니다. 대충 4096 바이트 단위로 관리하는데요, file에 바로바로 read하거나 write하지 않고, 자주 사용되는 page는 가능한 memory에 있도록 중간에 buffer manager를 둡니다. 그렇다면 buffer에 공간이 모자라면? buffer에 있는 page 중 누군가를 evict 할 수밖에 없습니다. 그럼 뭘 기준으로 하면 좋을까요? 이 부분을 잘 생각해서 구현해보고, 성능을 비교해보기 바랍니다. 제가 cache hit/miss 시뮬레이션 구현해둔게 있으니, 제 custom 보다 높은 성능을 달성해주세요!

이후 RM은 record management의 약자인데, PF를 사용해서 record들을 가져오거나, 새로 넣거나 등을 하게 해줍니다. 그렇다면 전체 record를 순회하는 scan 연산이 중요하겠죠. 이 부분을 구현하는 것이 핵심입니다. record는 page 앞 부분에 bitmap을 둬서 slot이 비어있는지 아닌지를 확인하는데, 만약 record 삭제 명령이 마지막 slot을 비우게 된다면 해당 page는 더이상 필요 없겠죠. 그렇지만 이를 바로 free로 만드는건 조금 비싼 연산이 필요합니다. free page list를 다시 계산해야하거든요. 그래서 보통 DBMS에서는 이러한 작업들을 vacuum 연산으로 해결합니다. 추가로, 지금은 고정 길이 record만 다룰 수 있습니다만, 가변 길이를 허용하려면 어떻게 해야할까요? 이 부분들은 자유롭게 구현해보시면 좋겠습니다.

문서와 테스트는 모두 공개되어있습니다. 기여해주시면 감사하겠습니다! 다만, 정답 코드와 핵심 로직은 마지막까지 저 혼자 해보고 싶습니다 (도전).

https://github.com/theeluwin/BlueBase

밑바닥부터 직접 만들어보는 DBMS에서 page cache policy에 따른 성능 비교.
5