- Published
- Author
- Iffyuva
How to extract a nested yaml key from a file and write its contents to another file?
js-yaml | jq ".topkey.nestedkey" | js-yaml > output.yaml At Codemancers, we believe every day is an opportunity to grow. This section is where our team shares bite-sized discoveries, technical breakthroughs and fascinating nuggets of wisdom we've stumbled upon in our work.
js-yaml | jq ".topkey.nestedkey" | js-yaml > output.yaml git show: git show ':(exclude)package-lock.json' curl -s checkip.dyndns.orgmockRejectedValue with axios the data should be inside response.data. Eg: mockRejectedValue({ response: { data: {errors: []} }, status: 400, statusText: "Bad Request" })mockRejectedValue with axios the data should be inside response.data. Eg: mockRejectedValue({ response: { data: {errors: []} }, status: 400, statusText: "Bad Request" })echo $PATH | sed -e $'s/\:/\\\n/'g or echo $PATH | tr ":" "\n" to see each entry in $PATH in separate line.:focus-within to keep the parent element visible when focus is on child. Helpful on making dropdown menu.jest.fn we can use mockFn.mockRejectedValue and mockFn.mockResolvedValue instead of mockFn.mockReturnValue(Promise.resolve({data: { message: "Failure", count: 1 }}); https://jestjs.io/docs/en/mock-function-api.html#mockfnmockresolvedvaluevalueShowing page 59 of 83
AI is everywhere but it's unclear which investments will actually move your metrics and which are expensive experiments.
Most AI projects fail at the data layer. Pipelines, quality, access all need work before LLMs can deliver value.
Your engineers are shipping product. They don't have capacity to also become AI specialists with production-grade experience.
Aging, undocumented codebases make AI integration slow, risky, and expensive. They need to move first.