circadian

It's a really nice idea and very good to see a familiar and simple interface, I'm definitely keen to look at this when I'm "idling"!

Two suggestions that I don't think have been mentioned:

1. It might be nice to at least acknowledge the source of the problems PDF-wise, no doubt somebody put effort into developing then and the supplementary information (assuming the PDFs are open source) would be useful for learning

2. Supporting information for learning the context subject material around the problem would be good: this relates to other comments about curation. This doesn't feel like "teach yourself math" so much as "test your math", which is still really helpful, but if you don't know the material there's nowhere to turn too

Great foundation for an amazing platform, nice work!

Being able to see glacial ice, both in the sea and when in and around ice sheets, has been one of my most cherished life experiences. If you get a chance to see the mind-bogglingly beautiful palette of blues available, you won't regret it.

Hopefully we can keep some of this ice for future generations.

Seems to be fixed in the as of about 30 minutes ago (went out for lunch!)

I would like to share some common links, as for a while I've been reading rather than writing. Hopefully there's something interesting in here for peeps to look at! :)

"It's the right thing to do for open and reproducible research."

I think this is the most important reason to do it. Research code is not meant to be perfect as another op said, but it can be instrumental in helping others, including non-academics, understand your research.

I think the sooner it's released the better (assuming you've published and you're not needing to protect any IP.) There's some great advice here: https://the-turing-way.netlify.app/reproducible-research/rep...

"This page summarizes pretty good what web technology is capable of, when in the hands of a real professional."

I was looking at this when I went to bed, and though the subject matter isn't completely new to me I was enthralled by the execution and stayed up and read all of it...

Absolutely LOVE the way this has been put together, it really speaks to me of beauty in simplicity, at least from the visual perspective!

Hehe, good Friday fun, nice one! :-)

I must admit that I'm ever so happy to have seen this post, QBasic was massively important towards me becoming a programmer. Kudos for the post, it's important for me to know that my nieces and nephews might see computers the same way I did: through an uncomplicated lens.

The appeal for me was to give, as you wrote, a simple interface to programming. The Apple RAM II I had was not as easily accessible for programming at my single digit age. QBasic was available on the 486 SX based MS-DOS OS we had, and it opened my eyes. Within a year or two I was reading Herb Schildt' "Teach Yourself C" and using Borland C for the first time. But at a young age you need that first step to be accessible!

Nice one...

First of three roles I'm long-overdue publishing this weekend, be very grateful for any feedback! :-)

Hey HN!

I've been meaning to do this for years, and have enjoyed taking the opportunity to start playing around with blogging. It has given me the opportunity to blog about Lektor/Ansible/Antarctica so far, but there's much more to comes, especially on the latter as I spent several years out there.

Tech wise I get up to all sorts, so watch this space.

Hope you all enjoy...

:-)

I have three tactics that I think primarily contribute to staying interested in projects (in or out of work), even if I find them somewhat dull or unnecessarily laborious:

1. Find a good space of the day when your brain is optimally productive and lock into a tasklist that you've preplanned. For example, I will often create a tasklist in the evening for what I want to achieve the next day, then hit it hard in the morning as that's when my enthusiasm and focus is best.

2. For any given project find an interesting approach to the solutions you need to provide. I won't take a run-of-the-mill approach to solving things (unless it's a quick win or mostly appropriate to do so) but will use solutions as a platform to approach things in a new way, with a new technology or just by improving what already exists.

3. Exercise: the reason I find the morning my most productive time of day is because I cycle to work every day, I think. If I have too much sedantary time in front of the computer it does my head in, but even a quick walk around the building will let my mind work on itself to meet the other two points I mention. If you're frustrated at your desk, you're already losing.

Hope that helps! :-)

Just the proverb used for the premise of the book has hooked me in: "What one fool can do, another can"

Love it, thank you for sharing

I used to work for a large multinational group whose core financial systems were written in COBOL during the seventies. I was told need to think of making the core systems future proof was identified as the company grew through the eighties and nineties, but never addressed. As time went by this attitude turned from one of "let's try and get on top of this" to "it can't be done because it's too risky / complex / old"...

The net result of this is that this ignorance spilled into the attitude towards technology across the group. I found it very demoralising as you always had to fight to convince non-technical staff why they needed to address technical debt that was 10/20/30 years old. In the end I managed to undertake some big and interesting projects successfully in spite of the "you'll never achieve that without a disaster" attitude, but the core COBOL system were just ignored as if somehow it'd go away (the reality was much more political and complicated than that, as it is with all multinationals...)

In the end I left for a position where people wanted me to build or rebuild things, rather than just spring the leaks around the problems. My point here is that unless you wield obvious experience or weight in this arena (as the "COBOL-legends" undoubtedly do) you'll have a job convincing people that it needs doing, at least until it goes up in flames.

I'm very happy he's not only won the award, but also that he's used it as a springboard to highlight ongoing privacy, security and information freedom issues.

Personally I think that's a mark of a great pioneer who is still using his capabilities for the best interests of us all.

Do what you feel happy doing!

In terms of thinking on a path for your career, think only of whether you are putting all your eggs in one basket. If a job role later becomes difficult to get / stay employed in, and you can't adapt, then that's the most likely problem you'll face.

I have always tried to be interested in a lot of things, so that I can turn my hand to new things once I need a new challenge. It has worked well for me so far ;-)

Nope, it's awesome and this same topic is clearly covered under the plumbing and porcelain section:

https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Po...

Worth noting that this article is overlooking the definition of our mark on the planet in terms of a geological age. ;-)

I don't normally comment, but given my background and general interest in the subject areas discussed, it's sparked an interest in commenting on the subject.

It's an interesting article, but I am a proponent of the idea that AI / deep learning / neural network based computing is still in it's infancy. I've worked in several of these industries and though newer companies are cutting into market share through a mixture of "intelligent" design and large-scale ingestion of data, I believe that it's important to admit we're a long way from being able to say that there is really a dramatic revolution through adoption if artificial intelligence / algorithms (bearing in mind I'm keeping well clear of the strong-vs-weak argument in using that term), in any given industry. Instead I think there are many fringe cases that carve out what might become the wider adoption of the future. These are nicely exemplified herein, but limited to mostly brute forcing the computational abilities of our limited (though fast and vastly impressive) advancements in technology.

For sure, the last 20 years have seen great change and so too will the next 20. However, I think it's sensible as (if/a) technological practitioner(s) to greet the change with a level and realistic perspective, we are still developing simple "AI" like systems. Also, businesses are extremely hesitant and cautious, both universally and especially across sectors, when make more than the necessary change required to one up each other. If you scrape off the top layer of innovation and hype, there is still a long way to go before we're swimming in the waters of a technical revolution (and one may argue how wise we are to seek it; one for another time)...