Tootfinder

Opt-in global Mastodon full text search. Join the index!

No exact results. Similar results found.
@n8foo@macaw.social
2024-11-23 20:50:37

Finally finished building this prototyping station, for designing synthesizer circuits from scratch. Super excited to start using it! #diysynth #electronics

@samir@functional.computer
2024-12-20 22:54:17

@… I definitely would enjoy learning more about this stuff. Do you have any good places to start?

@blakes7bot@mas.torpidity.net
2024-11-08 07:27:49

#Blakes7 Series B, Episode 05 - Pressure Point
BLAKE: Just get started on the door. [Avon fires again and starts to run but trips and falls.]
BLAKE: Avon! [The wires grow toward each other.]
blake.torpidity.ne…

@gharbeia@mastodon.social
2024-11-07 16:36:10

@… @… @…
and other

@n8foo@macaw.social
2024-11-09 14:41:12

I asked my daughter what that big machine was and she guessed “a synthesizer?” 😂 #synthesizer chaos.social/@leyrer/113452077

@x_cli@infosec.exchange
2024-10-04 13:32:55

Unpopular opinion on software development
Yesterday, I came across CI cultists.
They were preaching one should merge in main multiple times a day.
Quite frankly, I associate this behaviour to lab rats compulsively clicking the button to get gratifications (please don't do that to rats).
I think developers should refrain from becoming merge junkies. Code review is essential for good code quality. Automated tests suck at detecting logical errors, security vulnerabilities, and even decent code coverage.
Also, I believe pair programming is absolutely not a strategy to allow continuous integration. Everybody involved in the development process is drunk on their own bullshit reasons they made up to justify their poor design. Either the code review should be done by someone else, or the developers should sober up for a fortnight before code reviewing their own code.
PS: I am a software developer. I get drunk on my own bullshit as well.
#software #development #ci #codereview