probablyfine

@probablyfine@tech.lgbt

Average at software // Bad at games // Bi ๐Ÿฉท๐Ÿ’œ๐Ÿ’™

Interested in:
โœ… TDD
๐Ÿ‘ฅ Ensemble development
๐Ÿ”„ Continuous delivery
๐Ÿ–ฅ๏ธ Extreme programming

Not interested in: coriander, liquorice, cucumber

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

joelanman, to random
@joelanman@hachyderm.io avatar

what are some organisations and companies who actually care about inclusion and ethics, doing good work?

probablyfine,

@joelanman I've heard decent things about https://farewill.com/ from a friend, from a software development / SRE point of view so your mileage may vary

probablyfine, to random

An underrated approach to test-driving code is taking advantage of unrolled loops.

This pairs extremely well with the zero, one, many approach where you start with the empty case, then add logic to support a single input, then add logic to support two inputs, and so on.

We can use this approach to de-risk the jump from "single input" to "multiple inputs".

if (input.size() == 1) {  
 // One element case  
else if (input.size() == 2) {  
 // Two elements case  
} else if (...) {  
 // And so on  
}   

Our goal, then, is to refactor the contents of each block to look as similar as possible, such that extracting out a loop rather than a multi-step conditional is a task that can be delegated to your tooling or IDE.

Structuring your incremental test-drive development in this way may seem counter-intuitive, but it's another example of staging out low-risk changes and refactoring duplication out into a clearer form.

probablyfine,

@jacobsa @anderseknert @benjiweber Yes, that's what I had in mind but short toots aren't great for complete context!

Especially if you're exploring a new problem domain, making yourself walk through each of the early cases in order, identifying common bits of code, and refactoring out can be a helpful guardrail as opposed to just jumping into what you think the ideal solution is right away.

It really shines by letting you identify recursion too, as it becomes quite obvious when the result for an input depends on the result for a "previous" input, whether that's a smaller input set or the previous item in a collection, for example.

Sinjo, to random

So you know the problem some people were having where they came here and couldn't find enough interesting accounts to make a good home feed?

For me, Threads has the exact opposite problem. The feed is algorithmically generated and is full of influencer and brand accounts posting absolute garbage.

probablyfine,

@Sinjo @dixonary +1, the algo feed on twitter is ass, i want to see new tweets from my little friends inside my phone, not people selling tummy tea or shitcoins

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