@jamescooke@fosstodon.org
@jamescooke@fosstodon.org avatar

jamescooke

@jamescooke@fosstodon.org

Python developer working with data and royalties at Mixcloud.

Lover of testing and linting. User of Linux.

Author of https://github.com/jamescooke/flake8-aaa

This profile is from a federated server and may be incomplete. Browse more on the original instance.

jamescooke, to random
@jamescooke@fosstodon.org avatar

🎉 New blog post 🎉

Why isn't the UK switched over to DST yet?

Digging into why my mental model of "it switches over 2 weeks after the USA" is wrong...

https://jamescooke.info/why-isnt-the-uk-in-dst-yet.html

jamescooke, to random
@jamescooke@fosstodon.org avatar

After 1 minute of uptime and no changes in any of my synced directories, Dropbox is running 95 threads and taking 285M RAM.

Syncthing is running 10 threads and taking 46M RAM. 👌

remoquete, to random
@remoquete@hachyderm.io avatar

A few days ago I had an interesting conversation on the pros and cons of Markdown for technical documentation with Ed Marsh and Eric Holscherin a webinar hosted by Scott Abel. Here are some of the things I said during the webinar.

https://passo.uno/pros-cons-markdown/

jamescooke,
@jamescooke@fosstodon.org avatar

@remoquete This is really helpful 🙏

We already have "hairy" bits at work like:

  • Where does spell checking happen?
  • What happens when linting breaks? (yes - we added a Markdown linter).
  • How do we template repetitive tasks like writing up decisions?

cc @hamatti

jamescooke, (edited ) to random
@jamescooke@fosstodon.org avatar

Discovered that pip-tools has a "--build-deps-for" flag on pip-compile.

Am exploring using it to replace "base.in" dependencies when using a src layout and editable install...

pip-compile --build-deps-for editable --output-file requirements/base.txt  

jamescooke, to random
@jamescooke@fosstodon.org avatar

Big-ups to @davep for smashing through my grumpy and pedantic Markdown and versioning GrumpHub Issues today 😊 🙌

jamescooke,
@jamescooke@fosstodon.org avatar

@davep Hey! Don't make me retoot this to my tribe of faithful followers! 😂

jamescooke, to random
@jamescooke@fosstodon.org avatar

Has Tom of TOML put his actual birthday on the TOML homepage in an example?! 🙀

https://toml.io/en/

jamescooke, to random
@jamescooke@fosstodon.org avatar

Starting after this toot, I’m banning myself from tooting on my phone.

jamescooke, to random
@jamescooke@fosstodon.org avatar

The embarrassment - DST doesn’t even start tonight 😬🤦🏻‍♂️😬

jamescooke, (edited ) to random
@jamescooke@fosstodon.org avatar

Tonight’s UK shouldn’t impact our family as badly as I had expected…

child[0].get_temperature() is returning 39 😬 and the sleep schedule has gone to pot.

But I’m hoping we can all wake up tomorrow in UTC +1 and .get_temperature will be returning normal values and sleep schedule will have magically shifted.

jamescooke, (edited )
@jamescooke@fosstodon.org avatar

@underlap yay! I knew this but forgot it again 🤦🏻‍♂️

https://fosstodon.org/@jamescooke/112078336467376877

jamescooke, to random
@jamescooke@fosstodon.org avatar

Oh dear - this has become a pipeline... why does everything become a pipeline?!

jamescooke, to random
@jamescooke@fosstodon.org avatar

At PR time, I really need to do more than "just read" the code to give meaningful feedback... And what I mean by "meaningful" is something more than being a human linter.

I've just pulled code that I approved at PR a couple of hours ago and was merged. Now I'm looking at it in a whole new light because I'm actually trying to make a change to it - and now it's a whole different ball game. 😬

For starters, it's got two 15s long integration tests that I'd never have approved if I'd realised 😞

jamescooke,
@jamescooke@fosstodon.org avatar

On the plus side, it seems pretty easy to squash those two tests into a single test and to reduce the duration to 10s by simplifying how the data is generated.

The question is - how could I have spotted this at PR time? 🤔

jamescooke, to random
@jamescooke@fosstodon.org avatar

> please don’t imply that everyone who uses computers in a different way from you is dumb and wrong.

This thread from @b0rk is vibing with me: https://social.jvns.ca/@b0rk/112128320620010601

hl, (edited ) to uk
@hl@social.lol avatar
jamescooke,
@jamescooke@fosstodon.org avatar

@hl Wetherspoons next ☺️

jamescooke, to random
@jamescooke@fosstodon.org avatar

Preparing for clockpocalypse this weekend 😬

jamescooke,
@jamescooke@fosstodon.org avatar

@adamchainz Could be a winning hashtag 🤔

jamescooke, (edited ) to random
@jamescooke@fosstodon.org avatar

Update on my terrible home project - by slowing down, writing proper tests, and cleaning up directories I’m actually going faster.

Who’d have thought it?!

https://fosstodon.org/@jamescooke/112005829758129857

jasongorman, to random
@jasongorman@mastodon.cloud avatar

"Submit separate Pull Requests for refactoring" is a very succinct way of telling us that you're not doing Test-Driven Development. Or, in all likelihood, refactoring.

jamescooke,
@jamescooke@fosstodon.org avatar

@jasongorman @nikoheikkila So - a question… My work team has a large pipeline with a suite of tests, repo on GitHub. Our policy (which I wrote) is to split out a "refactor" PR before the feature PR.

My guess is that doesn’t mean I’m not doing TDD (though I can’t speak for the rest of the team). I think it means that our definition of refactor doesn’t tally - could that be possible?

jamescooke,
@jamescooke@fosstodon.org avatar

@jasongorman 🤔🤔🤔

Our refactor PRs are definitely not the same "size" as the refactors in red-green-refactor… I think they’re "bigger", but there’s no external behaviour change for our downstream report consumers.

(Maybe the key difference here is to call these "bigger refactors" a refactor at all.)

jamescooke,
@jamescooke@fosstodon.org avatar

@jasongorman For example, very often we find a fixed value is, in fact, going to have to vary over time.

Say - 50% of X goes in Y right now. But we find out that from 1st January it’s going to be 45%. The "refactor PR" splices in a date based rate loader with a single rate for all time at 50%. After this refactor is merged, 50% of X still goes in Y, but we’re now open for change.

The "feature PR" then adds the new config for the 45% rate.

Hope that makes sense - it’s been a long day 😬

jamescooke, to random
@jamescooke@fosstodon.org avatar

Wishing there was an existing license model that would allow me to build a new Python linting tool - free for use by individuals and FOSS projects, but requiring a small license fee to be used in a commercial setting.

Since this would be a tool, "use" means execution of the software, not integration into another project or package.

As I write this, it sounds like how "shareware" used to be 🤔

jamescooke,
@jamescooke@fosstodon.org avatar

@cosmoscalibur Thanks - that’s super helpful. I’d got to a similar place too - but the idea of writing an EULA seems a bit daunting. 😬

I also realised that businesses with FOSS projects that also have service / hosted offerings manage to swerve writing a license agreement for the software - they can leave it on a FOSS compatible license. Meanwhile, the service offering generates revenue to cover both (hopefully).

ghorwood, to random
@ghorwood@mastodon.social avatar

the thing i thought would happen to bandcamp is happening to bandcamp

jamescooke,
@jamescooke@fosstodon.org avatar

@ghorwood @meejah 👋🏻 hi - I’m not up to date with this changes and I can’t find any related news or articles via DDG. Could you help me understand what’s going on?

Are they booting licensed artists?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • thenastyranch
  • ethstaker
  • osvaldo12
  • mdbf
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • Youngstown
  • ngwrru68w68
  • slotface
  • GTA5RPClips
  • rosin
  • megavids
  • cubers
  • everett
  • cisconetworking
  • tacticalgear
  • anitta
  • khanakhh
  • normalnudes
  • Durango
  • modclub
  • tester
  • provamag3
  • Leos
  • lostlight
  • All magazines