Flipboard Tech DeskCanadian tech journalist @parismarx is trying to get off U.S. tech — and help you to do the same. Here's his comprehensive guide.
Ob Server
@observer11
- 2 Followers
- 15 Following
- 21 Posts
Observing
Greg K-HLooks like the AI companies have finally run out of money as they are asking various open source projects to test their closed source products for them for free. What could go wrong with giving access to an unknown tool to private code repos?
If I didn't know better, I would think this is an elaborate phishing scam, or they have run out of data to scrape and need more training material.
Gotta admire their brazenness...
If I didn't know better, I would think this is an elaborate phishing scam, or they have run out of data to scrape and need more training material.
Gotta admire their brazenness...
@icing aren't both cooling and radiation still unsolved problems for space datacenters?
@bradwilson thanks for the very detailed reply 😄
@bradwilson I started doing TDD through https://github.com/quii/learn-go-with-tests which I recommend a lot.
Anyway, it recommends writing acceptance tests first, so I wrote a test to download a file from a torrent peer. The implementation itself is ultra-rudimentary, right in TDD spirit. However, it has been hard to follow it up with good, structured code which is cleanly separated and tested.
Should I have to keep design separate from TDD and come up with a solid design up-front or am I doing something wrong?
@bradwilson I've been making a torrent client in Go. The hardest thing so far was coming up with a clean and logically separate code (which I haven't done yet 😆), but also I had problems with writing tests which can test the entire system.
To validate that the client is working, I have to spin up real qBittorrent clients, so I use Docker in my tests.
It's hard to articulate my thoughts. It was easy to write a bencode parser with TDD, but everything else is a hassle.