#codecraft — Public Fediverse posts

Codecraft: Native Amiga IDE for Coding and Debugging
#Amiga #Codecraft #AmigaDevelopment #SASC #AmigaOS #RetroComputing #AmigaSoftware #OpenSourceAmiga
https://theoasisbbs.com/codecraft-native-amiga-ide-for-coding-and-debugging/?feed_id=2787&_unique_id=67fe59c52fedb

Codecraft: Native Amiga IDE for Coding and Debugging
#Amiga #Codecraft #AmigaDevelopment #SASC #AmigaOS #RetroComputing #AmigaSoftware #OpenSourceAmiga
https://theoasisbbs.com/codecraft-native-amiga-ide-for-coding-and-debugging/?feed_id=2787&_unique_id=67fe59c52fedb

Codecraft: Native Amiga IDE for Coding and Debugging
#Amiga #Codecraft #AmigaDevelopment #SASC #AmigaOS #RetroComputing #AmigaSoftware #OpenSourceAmiga
https://theoasisbbs.com/codecraft-native-amiga-ide-for-coding-and-debugging/?feed_id=2787&_unique_id=67fe59c52fedb

Codecraft: Native Amiga IDE for Coding and Debugging
#Amiga #Codecraft #AmigaDevelopment #SASC #AmigaOS #RetroComputing #AmigaSoftware #OpenSourceAmiga
https://theoasisbbs.com/codecraft-native-amiga-ide-for-coding-and-debugging/?feed_id=2787&_unique_id=67fe59c52fedb

Codecraft: Native Amiga IDE for Coding and Debugging
#Amiga #Codecraft #AmigaDevelopment #SASC #AmigaOS #RetroComputing #AmigaSoftware #OpenSourceAmiga
https://theoasisbbs.com/codecraft-native-amiga-ide-for-coding-and-debugging/?feed_id=2787&_unique_id=67fe59c52fedb

Codecraft - die integrierte Entwicklungsumgebung (IDE) von Camilla Boemann - ist in Version 1.16 erschienen.

http://boemann.dk/codecraft/

#commodore #amiga #amigaos #amigaworld #codecraft #ide #developer #coding #software #retro

CodeCraft Academy: Как я создаю открытую платформу для обучения программированию

Привет, Хабр! Я yukk1ro , и сегодня хочу рассказать о своем проекте, который призван сделать обучение программированию более доступным и эффективным.

https://habr.com/ru/articles/895802/

#programming #education #opensourse #learning #codecraft #academy #git #github #js #webdevelopment

As usual with my writing ideas, some constructs got stuck in the machine and I finally found the flow to make them stick together:

https://www.sounding.com/2024/11/15/finding-flow/

#DevEx #SRE #intuition #improvisation #insight #flow #FlowState #creativity #stagecraft #codecraft #DIY #maker #programming

Had a developer moment updating a project: "Man, this is no good; I should do something about it."

That's the judgy part. The part that wants to throw everything away and start over using my current knowledge, patterns, and understanding.

This is the distracting part.

The site still works. The code is well crafted for my knowledge, patterns, and understanding at the time. Time to start making notes of how to get "there" from "here."

#CodeCraft
#PHP
#SoftwareDevelopment
#TechnicalCoach

I'm starting to think one of the blind spots of strong type system proponents is the power of names #design #codecraft

Possibly a crazy fever dream…but isn’t applying Single Responsibility Principle, and constraining function to a tightly coupled set of boundaries a similar concept to limiting work in progress? 🤔

#wip #srp #codecraft

@garyfleming If there was one, say, 'glasgow.tech', that might be a good.

I could see #CodeCraft Glasgow also joining it for example :)

I'm on #tech:glasgow.social and have not yet worked out if that is mastodon compatible or not.

No one thinks like you

Don’t make the mistake of thinking you’re the smartest person in the room. You might be the most knowledgeable about your specialist subject, but being a good boolean whisperer does not automatically make you an expert on public transportation, psychology, poverty, history, finance, or any other industry.

I’ve had the privilege of being disabused of that notion very early on in my career, surrounded by statisticians, linguists, psychologists, designers and vets. I do what I do, and let my curiosity take care of the rest.

But there’s a lot of arrogant arseholes in this industry who think they know best. Those who will talk instead of listening, who belittle, interrupt and condescend. They know their domain very well and are quick to criticise others who don’t understand.

But we all have our own models of how the world works, our own coordinates on the axes that describe the world as controlled by us vs controlled by others, whether money or relationships are more important, whether people matter more than animals, whether humanities can survive without science or science without humanities, visual thinkers or verbal thinkers or lingual thinker or kinetic thinkers. We don’t perceive or act in this world in a way quite like anyone else. We all bring unique experiences and perspectives to the table, and we all know something that others can learn from.

So sit and listen in silence. Take in what you can, and when you’re ready, ask questions. Listen to understand, not to respond, not merely to be polite, but because you are interested and you want to learn.

If we could see how others see us? They’re talking. All you need to do is listen.

The Constant Gardener : Knowing your team

One of the most interesting challenges in becoming a lead is understanding your team, and balancing project tasks between them. Whilst experience, both technical and domain, is a valuable indicator of how to assign tasks, there’s a few other things to take into account.

Having worked with a few people over the years, I can see 2 main types of developers. Managers may be asking which of the 16 Myers-Briggs personality types these represent, but I’m trying to give a persona sketch rather than a detailed breakdown.

Innovators are the ones I see most often – developers who want to work on the hot new thing, keep seeking out new ideas, and often like to throw things out and start again. They can pick up new projects quickly, by focussing on certain areas but are likely to get bored if they stay on one project for too long and may sometimes miss the bigger picture. That’s great for learning, and pushing forward the boundaries, but may not provide the stability that some projects need, and may need closer code reviews to ensure they maintain the house style for the project. If you’ve ever needed a white knight on your project, they’ll probably be an innovator.

Gardeners will take longer to get up to speed with a new project, because they prefer to dig in and find out how everything works, and build a detailed knowledge of the system before making changes. They will tend to evolve systems over extended periods. If you get someone like that on your project, you’ll want to keep them for several months, as their value to the project increases over time. Long lived projects with several maintenance releases benefit most from this type of individual. You may well find that they know the business domain better than the customer.

I think everyone I have worked with has qualities of both, but there are individuals who are clearly more innovators, and others that are clearly more gardeners. A good project should have both, with innovators pushing ideas and bringing new technologies to the tables, and the gardeners bringing the domain knowledge to make sure the right changes are made for the long-term health of the project. As a lead, your job should be to understand the way your team things, so that you can take the right ideas on board at the right time, and bring your team along with you. And, most importantly, know yourself. The most important thing the others on the team bring is knowledge of things you don’t know, or at least questions that force you to think about them. Embrace it. Inspire your innovators and nurture your gardeners.