Search
37 results for “voidbot”
-
6b. For some complex scenarios—such as testing behavior on a specific complex state to find an obscure bug—that may not be possible. Writing tests first really helps with this as it forces you to think about the behavior of your code and how you're going to test it before you write it.
Testing first encourages smaller, more modular units of code, which generally means better code. A good book for getting started with the "test first" approach is Test Driven Development by Example, by Kent Beck.
-
6b. For some complex scenarios—such as testing behavior on a specific complex state to find an obscure bug—that may not be possible. Writing tests first really helps with this as it forces you to think about the behavior of your code and how you're going to test it before you write it.
Testing first encourages smaller, more modular units of code, which generally means better code. A good book for getting started with the "test first" approach is Test Driven Development by Example, by Kent Beck.
-
7a. For unit tests (including test infrastructure tests) all code paths should be tested. 100% coverage is a good place to start. You can't cover all possible permutations/combinations of state (combinatorial explosion), so that requires consideration. Only if there is a very good reason should code paths be left untested.
-
28. Generally, particularly in tests, wait for a specific change rather than sleeping for an arbitrary amount of time. Voodoo sleeps are hard to understand and slow down your test suite.
-
22a. Smaller, more tightly scoped unit tests give more valuable information when they fail—they tell you specifically what is wrong. A test that stands up half the system to test behavior takes more investigation to determine what is wrong. Generally a test that takes more than 0.1 seconds to run isn’t a unit test.
-
22b. There’s no such thing as a slow unit test. With tightly scoped unit tests testing behavior, your tests act as a de facto specification for your code. Ideally if someone wants to understand your code, they should be able to turn to the test suite as "documentation" for the behavior. A great presentation on unit testing practices is Fast Test, Slow Test, by Gary Bernhardt: https://www.youtube.com/watch?v=RAxiiRPHS9k
-
22a. Smaller, more tightly scoped unit tests give more valuable information when they fail—they tell you specifically what is wrong. A test that stands up half the system to test behavior takes more investigation to determine what is wrong. Generally a test that takes more than 0.1 seconds to run isn’t a unit test.
-
15. The more you have to mock out to test your code, the worse your code is. The more code you have to instantiate and put in place to be able to test a specific piece of behavior, the worse your code is. The goal is small testable units, along with higher-level integration and functional tests to test that the units cooperate correctly.
-
6a. Unit tests test to the unit of behavior, not the unit of implementation. Changing the implementation, without changing the behavior or having to change any of your tests is the goal, although not always possible.
So where possible, treat your test objects as black boxes, testing through the public API without calling private methods or tinkering with state.
-
21a. Make code correct first and fast second. When working on performance issues, always profile before making fixes. Usually the bottleneck is not quite where you thought it was. Writing obscure code because it is faster is only worth it if you’ve profiled and proven that it’s actually worth it.
-
7b. Lack of time is not a good reason for not testing all code paths and ends up costing more time. Possible good reasons include: genuinely untestable (in any meaningful way), impossible to hit in practice, or covered elsewhere in a test. Code without tests is a liability. Measuring coverage and rejecting PRs that reduce coverage percentage is one way to ensure you make gradual progress in the right direction.
-
7a. For unit tests (including test infrastructure tests) all code paths should be tested. 100% coverage is a good place to start. You can't cover all possible permutations/combinations of state (combinatorial explosion), so that requires consideration. Only if there is a very good reason should code paths be left untested.
-
18. Don’t do work in object constructors, which are hard to test and surprising. Don’t put code in `__init__.py` (except imports for namespacing). `__init__.py` is not where programmers generally *expect* to find code, so it’s "surprising".
-
10. Write defensively. Always think about what can go wrong, what will happen on invalid input, and what might fail, which will help you catch many bugs before they happen.
-
1b. YAGNI: "You Aint Gonna Need It". Don't write code that you think you might need in future, but don't need yet.
The same is true for commenting-out code; if a block of commented code is going into a release, it shouldn't exist. If it is code that may be restored, make a ticket and reference the commit hash for the code delete. YAGNI is a core element of agile programming. The best reference for this is Extreme Programming Explained, by Kent Beck.
-
4. When it comes to API design (external facing and object API): *Simple things should be simple; complex things should be possible.* Design for the simple case first, with preferably zero configuration or parameterization, if that's possible. Add *options* or additional API methods for more complex and flexible use cases (as they are needed).
-
📬 Malware auf Android-TV-Boxen: Vo1d-Botnetz wächst auf 1,6 Millionen Geräte
#Cyberangriffe #Malware #AdFraudaufTVBoxen #AndroidTVBox #AndroidTVMalware #AndroidVo1d #Vo1dBotnetz https://sc.tarnkappe.info/bb0839 -
#nixbook and #voidbook side-by-side! I made a project similar to nixbook but geared towards low-storage chromebooks, feel free to check it out! https://git.ownfusion.com/ownfusion/voidbook
-
#nixbook and #voidbook side-by-side! I made a project similar to nixbook but geared towards low-storage chromebooks, feel free to check it out! https://git.ownfusion.com/ownfusion/voidbook
-
-
This Tuesday’s #HacksterCafe guest is @clomads of Voidbox Industries (https://vdbx.io)! She’s launching the PwrTool 500 – a high-capacity power and battery monitor for #HomeAssistant – on @crowdsupply soon. We have lots to dig into, from #OpenSource #SmartHome tech to running a #hardware #SmallBusiness out of a space-age school bus!
Aug. 28, 10:30am Pacific on #HacksterIO :
▶️ https://www.youtube.com/watch?v=a_r8MiX0PZU&list=PLsRBa4uXjihZwcYrwwuPhsYxWtFwMBqDF&index=1
▶️ https://www.linkedin.com/events/7365707803262386178/ -
This Tuesday’s #HacksterCafe guest is @clomads of Voidbox Industries (https://vdbx.io)! She’s launching the PwrTool 500 – a high-capacity power and battery monitor for #HomeAssistant – on @crowdsupply soon. We have lots to dig into, from #OpenSource #SmartHome tech to running a #hardware #SmallBusiness out of a space-age school bus!
Aug. 28, 10:30am Pacific on #HacksterIO :
▶️ https://www.youtube.com/watch?v=a_r8MiX0PZU&list=PLsRBa4uXjihZwcYrwwuPhsYxWtFwMBqDF&index=1
▶️ https://www.linkedin.com/events/7365707803262386178/ -
This Tuesday’s #HacksterCafe guest is @clomads of Voidbox Industries (https://vdbx.io)! She’s launching the PwrTool 500 – a high-capacity power and battery monitor for #HomeAssistant – on @crowdsupply soon. We have lots to dig into, from #OpenSource #SmartHome tech to running a #hardware #SmallBusiness out of a space-age school bus!
Aug. 28, 10:30am Pacific on #HacksterIO :
▶️ https://www.youtube.com/watch?v=a_r8MiX0PZU&list=PLsRBa4uXjihZwcYrwwuPhsYxWtFwMBqDF&index=1
▶️ https://www.linkedin.com/events/7365707803262386178/ -
This Tuesday’s #HacksterCafe guest is @clomads of Voidbox Industries (https://vdbx.io)! She’s launching the PwrTool 500 – a high-capacity power and battery monitor for #HomeAssistant – on @crowdsupply soon. We have lots to dig into, from #OpenSource #SmartHome tech to running a #hardware #SmallBusiness out of a space-age school bus!
Aug. 28, 10:30am Pacific on #HacksterIO :
▶️ https://www.youtube.com/watch?v=a_r8MiX0PZU&list=PLsRBa4uXjihZwcYrwwuPhsYxWtFwMBqDF&index=1
▶️ https://www.linkedin.com/events/7365707803262386178/ -
This Tuesday’s #HacksterCafe guest is @clomads of Voidbox Industries (https://vdbx.io)! She’s launching the PwrTool 500 – a high-capacity power and battery monitor for #HomeAssistant – on @crowdsupply soon. We have lots to dig into, from #OpenSource #SmartHome tech to running a #hardware #SmallBusiness out of a space-age school bus!
Aug. 28, 10:30am Pacific on #HacksterIO :
▶️ https://www.youtube.com/watch?v=a_r8MiX0PZU&list=PLsRBa4uXjihZwcYrwwuPhsYxWtFwMBqDF&index=1
▶️ https://www.linkedin.com/events/7365707803262386178/ -
Ritual Ascension – Profanation of the Adamic Covenant Review
By Dear Hollow
Profanation of the Adamic Covenant represents catacombs dripping with putridity and filth, the blasphemy called against the heavens from far below ground. It’s an upheaval from beneath our feet, the crawling and coagulant rot that spreads from abyss to abyss. The filth and blood clots our eyes, hearts, and minds, driving us deeper and deeper into the madness until our lungs are filled with mud. Ritual Ascension is transcendence and enlightenment achieved through the reveling and swallowing of the grime-soaked entrails through a vicious and ancient ritual, the lumbering deity whose mammoth footfalls and cloud of plague require payment in full. It’s a ritual to the god of the mud and disease, and a fist slammed into the underside of heaven.
Death/doom has many heads, but the one Ritual Ascension rears may be the ugliest. The Denver collective, alongside sharing all three members with Aberration, is comprised of members of Suffering Hour, Void Rot, Feral Light, and Annihilation Cult, promising a psychedelic affair inspired just as much by the classic death/doom acts of yore as the more experimental devastators. You’ll certainly find homages to Incantation, diSEMBOWELMENT, and Winter in its ten-ton doom hammers, but atop it is an opaque and occult breed of dissonant insanity reminiscent of Portal and a palpable filth only touched by the likes of Stenched or Rotpit, only kept in the realm of humanity by a palpable groove that reminds me of Ataraxie. Ritual Ascension offers the depths in ways few can, a collective far greater than the sum of its parts.
Crawling, slimy chaos is one hell of a first impression. Overload of down-tuned and filthy tremolo guide mammoth processions, whose dissonant constructions and atonal dirges provide a hypnotic otherworldliness. As displayed lumbering out of the gates, its attack is slimy, slow, and devastating, ultimately a feeling or a place rather than a collection of highlights – as any good doom album ought to be. From the subtle and simple chord progressions that dominate more minimalist pieces (“Womb Exegesis”) to the groovy and monolithic chugs that grace the climaxes of lengthy runtimes (“Pillars of Antecedence,” “Cursed Adamic Tongues”), interspersed by passages of blastbeats ranging from blazing to contemplative. DH’s vocals are a crucial element to the album’s subterranean and blasphemous atmosphere, ranging from the commanding chthonic bellows you expect from this breed of devastation to the tortured howls and groans more indicative of black metal.
If the first half of Profanation is subtle and crawling, then the second exists as utterly filthy slow-motion violence. I was initially disappointed that the Portal-isms were not as handily felt among the tracks of the first half, only gleaming in sporadic moments and within traditionally ominous diminished chord progressions. However, crossing into the second half with the scalding “Consummation Rites” and “Kolob (At the Throne of Elohim),” caustic slow-motion Ulcerate leads collide with the filthiest riffs Impetuous Ritual could muster, with DH’s most charismatic performances of the album. Unhinged and cutthroat are not words typically associated with doom, but the layers of overwhelm and dissonance meet the criteria with a bloodthirstiness and underlying craving for brutality. Looking back, it would have been relatively easy to incorporate the dissonant intensity in the first couple of tracks, but their later full fruition after a crawling crescendo makes them feel even more painful and overwhelming.
Even though the dissonance was not as immediate as I anticipated and the necessity for the patience required for this kind of beast goes without saying for its atmosphere – rather than a collection of songs – Profanation of the Adamic Covenant is transcendent. Encapsulating that crawling dread and ritualistic weight, monolithic groove, and dissonant layers in a tidy forty-eight minutes and held together by the dedication to unholy filth, it offers bounties aplenty for those willing to wade through the offal and mire. Bolstered by impressive performances in unpredictable percussion, riffs both mammoth and caustic, and vocals tortured and menacing, Ritual Ascension offers one hell of a debut. Get swallowed by the filth.
Rating: 4.0/5.0
DR: 7 | Format Reviewed: 320 kb/s mp3
Label: Sentient Ruin Laboratories
Website: instagram.com/ritualascension
Releases Worldwide: February 28th, 2025#2025 #40 #Aberration #AmericanMetal #AnnihilationCult #Ataraxie #AvantGardeMetal #DeathDoomMetal #diSEMBOWELMENT #DissonantDeathMetal #Feb25 #FeralLight #ImpetuousRitual #Incantation #OldSchoolDeathMetal #Portal #ProfanationOfTheAdamicCovenant #Review #Reviews #RitualAscension #Rotpit #SentientRuinLaboratories #Stenched #SufferingHour #Ulcerate #VoidRot #Winter
-
📬 Malware auf Android-TV-Boxen: Vo1d-Botnetz wächst auf 1,6 Millionen Geräte
#Cyberangriffe #Malware #AdFraudaufTVBoxen #AndroidTVBox #AndroidTVMalware #AndroidVo1d #Vo1dBotnetz https://sc.tarnkappe.info/bb0839 -
📬 Malware auf Android-TV-Boxen: Vo1d-Botnetz wächst auf 1,6 Millionen Geräte
#Cyberangriffe #Malware #AdFraudaufTVBoxen #AndroidTVBox #AndroidTVMalware #AndroidVo1d #Vo1dBotnetz https://sc.tarnkappe.info/bb0839 -
📬 Malware auf Android-TV-Boxen: Vo1d-Botnetz wächst auf 1,6 Millionen Geräte
#Cyberangriffe #Malware #AdFraudaufTVBoxen #AndroidTVBox #AndroidTVMalware #AndroidVo1d #Vo1dBotnetz https://sc.tarnkappe.info/bb0839 -
📬 Malware auf Android-TV-Boxen: Vo1d-Botnetz wächst auf 1,6 Millionen Geräte
#Cyberangriffe #Malware #AdFraudaufTVBoxen #AndroidTVBox #AndroidTVMalware #AndroidVo1d #Vo1dBotnetz https://sc.tarnkappe.info/bb0839