submitted by codeinabox to security 7 points | 5 comments https://depthfirst.com/research/containers-are-no-longer-safe

submitted by codeinabox to programming 7 points | 0 comments https://martinfowler.com/articles/healthy-peer-feedback.html > Peer-to-peer feedback is a powerful growth tool, and yet candid feedback is rare. We treat all feedback as positive — either to strengthen confidence or improve effectiveness. Based on this principle we can form several patterns for both giving and receiving feedback to help teams improve their interactions.

submitted by codeinabox to webdev 1 points | 0 comments https://aarontgrogg.com/blog/2026/09/23/how-to-recognize-web-performance-issues-a-visual-guide-to-core-web-vitals/

submitted by codeinabox to aicoding 7 points | 0 comments https://earendil.com/posts/measuring-code-sloppiness/

submitted by codeinabox to mobiledev 2 points | 1 comments https://redmonk.com/kholterhoff/2026/09/22/shopify-native/ > Last week the frontend and mobile dev community sat up when Shopify announced it was moving its mobile apps off React Native and back to Swift and Kotlin. Shopify went all-in on React Native in 2020, and as recently as January 2025 Shopify’s head of mobile Mustafa Ali wrote that its future looked bright and that Shopify would keep investing in it. Not quite two years later, the company has reversed course.

submitted by codeinabox to programming 9 points | 1 comments https://purplesyringa.moe/blog/write-while-learning/ > When you face a problem and spend days finding a solution, write about your successes – or even failures. This will help others who are stuck on the same issue, and it will help experts find missing information or unclear wording in their docs (which is why documenting failures is useful, too). Blogs, social networks, anything goes, really – even if only your friends see it, some of them may still find it useful.

submitted by codeinabox to programming 64 points | 25 comments https://blog.herlein.com/post/build-another-engineer/

submitted by codeinabox to programming 14 points | 4 comments https://alexn.org/blog/2026/09/17/executable-scripts-with-dependencies/

submitted by codeinabox to programming 9 points | 2 comments https://cel.cs.brown.edu/blog/design-space-async-await/

submitted by codeinabox to java 11 points | 4 comments https://mostlynerdless.de/blog/2026/09/15/java-27-is-only-boring-on-the-surface/

submitted by codeinabox to aicoding 3 points | 2 comments https://blog.pragmaticengineer.com/the-pulse-tech-companies-move-to-open-ai-models/

submitted by codeinabox to aicoding 8 points | 1 comments https://terriblesoftware.org/2026/09/10/ai-is-breaking-this-thing-we-call-trust/ > AI makes it easy to generate code, explanations, answers to review questions, and entire docs without the author understanding any of it. Everything can look finished. Actually, more often than not, it can even be correct (!) without the author having checked it. > > And that is the part that I’ve been struggling with recently, and what most of this post is about… I used to start reviewing work with the assumption that the other person did their homework. Now that may or may not be true, so instead of starting the review with a _“is this a good change?”_ Now I often start with, _“does the author understand what they’re sending me?”_

submitted by codeinabox to html 7 points | 2 comments https://vale.rocks/posts/html-relics

submitted by codeinabox to programming 35 points | 14 comments https://blog.jim-nielsen.com/2026/stop-with-the-uptime-percentage/

submitted by codeinabox to webdev 1 points | 1 comments https://svar.dev/blog/building-data-grid-in-react-vue-svelte/

submitted by codeinabox to css 1 points | 0 comments https://css-tricks.com/css-random-function-polyfill/

submitted by codeinabox to programming 19 points | 14 comments https://www.seangoedecke.com/you-have-to-beat-the-models-at-something/ > I think it’s more useful to look at the tasks models _haven’t_ gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are: > > 1. Deep familiarity with the codebase > 2. Technical communication >

submitted by codeinabox to programming 60 points | 16 comments https://deadsimpletech.com/blog/no-such-thing-as-just-a-tool

submitted by codeinabox to programming 56 points | 6 comments https://newsletter.eng-leadership.com/p/good-culture-is-the-biggest-productivity

submitted by codeinabox to webdev 4 points | 0 comments https://amberweinberg.com/recent-improvements-in-web-development/

submitted by codeinabox to programming 70 points | 10 comments https://techhub.iodigital.com/articles/am-i-learning-or-am-i-just-prompting > Recently I gave my first ever presentation at iO. It was about what it actually feels like to be a junior developer in a world where AI is just always there. This is a write-up of that talk, including what the room said back.

submitted by codeinabox to python 8 points | 1 comments https://nathancooper.io/blog/2026-08-10-ipython-is-all-you-need > “I use IPython as my terminal’s shell.” > > “IPython in the shell?” > > “No, IPython is the shell.” > > “IPython? As the shell?” > > “Only way to live.”

submitted by codeinabox to Aii 16 points | 5 comments https://dontpastetheai.com/ > When someone asks you something, they want your answer. Not a wall of ChatGPT text. A short answer from a human will always be worth more than one from a robot, even if the robot is right.

submitted by codeinabox to programming 55 points | 9 comments https://www.seangoedecke.com/you-should-never-be-angry-at-work/ > If you routinely “get heated” at work, the best-case scenario is that you’re part of a tight-knit team of confident people who aren’t put off by it. No harm, no foul. But the second someone comes onto your team who’s not so confident, or you have to communicate outside of your team, it becomes a big problem. It’s a bad way to treat your colleagues — even undirected or casual anger intimidates and alienates the people around you — and it makes you a less effective engineer.

submitted by codeinabox to programming 13 points | 10 comments https://www.noemamag.com/why-is-everyone-in-tech-so-sad/