Home of the devvy Kjörndogs. Buckle up, get comfortable. We’ll be pushing automated updates from any major developments on our core application, while publishing technology insights, code related findings, and general dev musings.
To use appropriate corporate terminology our initial quote Fuddle Duddle now has bolster application awareness...
To use appropriate corporate terminology our initial quote Fuddle Duddle now has bolster application awareness...
(The kind of cadence that doesn't cry foul over oat almond milk, if you know what I mean)
Having one to several pages in a state of refactor means we can move on to integration strategies now.
(The kind of cadence that doesn't cry foul over oat almond milk, if you know what I mean)
Having one to several pages in a state of refactor means we can move on to integration strategies now.
medium.com/nightingale/...
medium.com/nightingale/...
⚡POWER + WASHING ⚡
⚡POWER + WASHING ⚡
In other news, we need to talk about fresh produce being handed into a pillow case at the end of the month.
Socially progressive, and yet comparably socially destructive.
Fibre? Or fun police...
In other news, we need to talk about fresh produce being handed into a pillow case at the end of the month.
Socially progressive, and yet comparably socially destructive.
Fibre? Or fun police...
By being able to ~conjure~ the
1) suspense and SSR lazy loading pattern with
2) code splitting on page sections with
3) adequate react router handling paradigms with errorBoundaries, interstitial placements and reusable designs
By being able to ~conjure~ the
1) suspense and SSR lazy loading pattern with
2) code splitting on page sections with
3) adequate react router handling paradigms with errorBoundaries, interstitial placements and reusable designs
The challenge I am giving the team is to
1) enact test coverage on a per page basis while
2) using deltas in code changes such that our coverage is adaptive to revisions.
Now that is a "thriller", to us.
The challenge I am giving the team is to
1) enact test coverage on a per page basis while
2) using deltas in code changes such that our coverage is adaptive to revisions.
Now that is a "thriller", to us.
𝘪𝘵'𝘴 𝘫𝘶𝘴𝘵 𝘢 𝘫𝘶𝘮𝘱 𝘵𝘰 𝘵𝘩𝘦 𝘭𝘦𝘧𝘵....
𝘪𝘵'𝘴 𝘫𝘶𝘴𝘵 𝘢 𝘫𝘶𝘮𝘱 𝘵𝘰 𝘵𝘩𝘦 𝘭𝘦𝘧𝘵....
We did need the branch for the core upgrades to INFORM the coverage. So while divergent from our QA branch, we can at least stipulate what is going on, and what needs coverage to begin to trunk.
🧟Otherwise we would haunt the project🧟
We did need the branch for the core upgrades to INFORM the coverage. So while divergent from our QA branch, we can at least stipulate what is going on, and what needs coverage to begin to trunk.
🧟Otherwise we would haunt the project🧟
Madness: 𝑇𝑎𝑘𝑒𝑠 𝑖𝑡𝑠 𝑡𝑜𝑙𝑙 👻
Madness: 𝑇𝑎𝑘𝑒𝑠 𝑖𝑡𝑠 𝑡𝑜𝑙𝑙 👻
One thing that doesn't invite Freaky Feelings is using LLMs to scan for dependency updates combinatively.
As many have experienced before, it is almost like in the past you change one dependency and a mutant hand shoots out of the ground while the stakeholders
One thing that doesn't invite Freaky Feelings is using LLMs to scan for dependency updates combinatively.
As many have experienced before, it is almost like in the past you change one dependency and a mutant hand shoots out of the ground while the stakeholders
The real "Thriller" is an appropriately tested and thoroughly documented pull request for a major release?
...𝘰𝘵𝘩𝘦𝘳𝘸𝘪𝘴𝘦 𝘺𝘰𝘶 𝘮𝘪𝘨𝘩𝘵 𝘧𝘪𝘯𝘥 𝘪𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘢𝘯𝘢𝘭𝘺𝘵𝘪𝘤𝘴 𝘵𝘩𝘢𝘵 𝘤𝘢𝘯 𝘩𝘢𝘶𝘯𝘵 𝘺𝘰𝘶 👻
The real "Thriller" is an appropriately tested and thoroughly documented pull request for a major release?
...𝘰𝘵𝘩𝘦𝘳𝘸𝘪𝘴𝘦 𝘺𝘰𝘶 𝘮𝘪𝘨𝘩𝘵 𝘧𝘪𝘯𝘥 𝘪𝘵 𝘪𝘴 𝘵𝘩𝘦 𝘢𝘯𝘢𝘭𝘺𝘵𝘪𝘤𝘴 𝘵𝘩𝘢𝘵 𝘤𝘢𝘯 𝘩𝘢𝘶𝘯𝘵 𝘺𝘰𝘶 👻
1) Is the jack-o-lantern positioning itself a fire hazard?
2) Does the team have any pumpkin allergies?
3) What is the risk of haunting?
1) Is the jack-o-lantern positioning itself a fire hazard?
2) Does the team have any pumpkin allergies?
3) What is the risk of haunting?
😱
😱
Baseball is pretty cool. 👍
www.youtube.com/watch?v=iyDx...
Baseball is pretty cool. 👍
www.youtube.com/watch?v=iyDx...
1) cross-referencing an application's package.json with
2) a risk assessment prompt in your flavour of LLM such that
3) upgrades can factor in regression risks and report on simultaneous upgrades required throughout an application stack from
1) cross-referencing an application's package.json with
2) a risk assessment prompt in your flavour of LLM such that
3) upgrades can factor in regression risks and report on simultaneous upgrades required throughout an application stack from
Welcome to the party.
Welcome to the party.