The 2 Types of Programmers

[@CodingWithLewis]

Where would you be on this sliding scale? 🤔

[@rusticmouse]

I'd definitly be more on the result side, because as a student you don't have much time to optimize your code. Once it's working it stays mostly untouched.

[@Equalisys]

@@rusticmouse defenitely: if it works, don't touch it.

[@miomip]

I'm on the craft-base side. I've used half a year on understanding something before I started working just to get the most optimal program, but I hate agile and think it's a waste of time, so many of the concepts associated with it is just not used.

[@siteantipas6837]

I am a Result-Based programmer. Just ship 🚢 it

[@0hhStormy]

I use Python but I use maybe one or two libraries at most in my projects so maybe a tad bit towards result.

[@cody_codes_youtube]

First 3-4 years I was craft, but then used those skills to be result for the rest of my career. The craft skills allow you dive deep when you need to

[@CodingWithLewis]

At the end of the day, we have to just say screw it and ship it

[@TGhost74]

> Be me > Be a result based programmer > Complete stage 1 @2:12 in a week > Complete stage 2 in 5 months > Begin stage 3 > Site gets DOS'ed on the first day, didnt spend enough time on security. All has failed > Start again. JavaScript programming in a nutshell

[@pierreollivier1]

as a Zig enjoyer, I would agree with Zig's zen : Communicate intent precisely. Edge cases matter. Favor reading code over writing code. Only one obvious way to do things. Runtime crashes are better than bugs. Compile errors are better than runtime crashes. Incremental improvements. Avoid local maximums. Reduce the amount one must remember. Focus on code rather than style. Resource allocation may fail; resource deallocation must succeed. Memory is a resource. Together we serve the users. So definitely more Craft based, but also user focus. Users are what matters at the end of the day.

[@SteveEngebretsen]

I had not heard of Zig before. Interesting.

[@k.Kayzen]

python is my fav lang because its simple but (kinda) powerful, and i also agree with its zen Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity. Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one-and preferably only one-obvious way to do it. Although that way may not be obvious at first unless you're Dutch. Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea. Namespaces are one honking great idea-let's do more of those!

[@pierreollivier1]

@ I really like python too, but I think that it doesn’t really obeys its own Zen. I still love python, ans use it all the time for prototyping, and experimenting which I love to do. But Zig really follows its own Zen adamantly. They’ve the benefit of not being 1.0 yet, so they have more leeway too unlike python, Zig’s core team, breaks the language and build system, add and remove features in order to avoid local maximum. Python is great but since it’s a dynamic language it’s harder to truly follow its own guidelines. Tools help but yeah, I wish python had some better tooling especially the build system. I really love when a language has a built system that’s well made, and really like it even more when the build system is in the same language like Zig.

[@frogery]

i wish i was more results based, but i get so caught up in doing things "right" and overanalyzing that i never complete my projects.

[@alexcarlseen1301]

You gotta complete your projects! You can always go back and re-factor things you wish you did differently. I think it’s a natural part of the process to discover that some part of a function should be split off so it can be used elsewhere. Or that your early architecture decision might not be your ideal approach for this particular problem. Honestly, recognizing shortcomings after the fact and then reworking some of my code provides great educational insights that I get to file away for the next project.

[@05degrees]

Maybe it’s not being a craft-oriented type but, say, having ADHD. I think there are plenty of people who focus on craft and do well with completion-it should be, if I’m getting psychology right, an almost orthogonal dimension.

[@MusicEngineeer]

Yes - same here!

[@destinyx1636]

This is me too

[@neos_hackerspace]

In my opinion, craft programmers win :) Craft driven programmers can also be a result driven programmer, but not the other way around, because most craft driven programmers have much more skills and knowledge than the result based programmers and as a craft programmer you can always just switch to result based and use existing tools to build a product quickly. If you know how to implement your own database or programming language, you can always use an existing one and even better so, as you have more understanding of the inner mechanics. If you only glued packages together for years, as result driven programmer, you simply do not have the skills to really build something from the ground up. Sure it might not be a problem for a specific job or project, but we talk about a general comparison here. The downside of craft driven programmers is, that you need more time - building your own things and learning takes much longer than learning how to use existing tools.

[@alexkotusenko]

Great analysis

[@kiyasuihito]

Agreed. Not to mention that software has to be architected well to support any long term product that a business want to expand on. Takes a lot longer to ship to market when you're trying to make spaghetti code fit new requirements. 😅

[@thomas.thomas]

not every company nor project need some sophisticated tailored solution if you are just selling sparkling water it is best to have some result driven team. being result driven doesn't mean sphagetti code. It can mean using standard libraries to build a website, maybe using php instead of some complicated javascrip

[@Faizan29353]

@@thomas.thomas as he stated, craft based programmer can use tools If say he uses chatGPT, he can analyze/improve it to his liking.

[@SteveEngebretsen]

"rust is craft focused while python is production focused" Now I know why I don' t like python. 30 years of embedded C and C++ including OO. On the other hand I learned early on there is no such thing as 'beautiful code', just code that generates the correct behavior. Professional software engineers focus on readability and maintainability because you come back to the code months, or weeks, later and say, "Who wrote that? Oh. I did. What does it do?" ... TO LEWIS, these are wonderful videos. Lots of wisdom. Thanks!

[@daemon_zero]

No wonder you know well code isn't always pretty, Sir, considering you did C and C++. I'm working in a very low level part of a personal project (low level as in bit twiddling) and I look at that code and find it some of the most offputting lines of character I have ever seen.

[@SteveEngebretsen]

@@daemon_zero Yep. Using bitwise operators or bitfields. I did it in Pascal a very long time ago. OMG. Learned C later. ;') The scary part is when you find yourself thinking in it. I had a friend who dreamed the coded solution to a problem.

[@thomas.thomas]

@@daemon_zero what defines well code? in a production environment it can be more important on how fast you can change the logic or the parts of code, or how fast you can train new employees to do that

[@AZisk]

wow. nice production

[@gtleshow]

The email reliability debate had me nodding so hard because... relatable. It's great to see both approaches appreciated for their strengths rather than pitted against each other. Awesome content, Lewis!

[@logvoid]

As an student, i consider myself somewhat of an hobbyist so i'm only focused on the quality of the code. I'm on the extreme far end of the craft side. Just thinking about the overhead of Python code or JS frameworks gives me a feeling of repulsion and disgust regardless of how rational that feeling actually is.

[@thomas.thomas]

why not code everything in Assembly then? Gotta hate the overhead that is called Rust or C

[@G36_maid]

why not build a circuit for them? Gonna hate the overhead of assembly instructions

[@jwm109]

@@thomas.thomas because compilers are now better then handwritten assembly code, but C is still way faster then python plus they didn't say which language they are using

[@logvoid]

@@thomas.thomas If i did write something in assembly, it wouldn't be much or even at all more efficient than if i wrote it in Rust or C - The compiler will write better assembly and faster. The cases where handwritten assembly would perform significantly better are very rare and the code would be way harder to maintain.

[@jwm109]

@@G36_maid costs

[@kylegrossman6260]

Personally, I'm an accountant, and I love Python for handling tedious tasks. I understand that something like rust or cpp could be 10x faster, but we're talking a project being completed in 1/100th of a second versus 1/10th of a second in Python. When the task is converting an excel spreadsheet into a new format, and it was going to take an hour to do by hand anyway, it's a diminishing marginal return to learn a more difficult syntax. Of course, if I had a million spreadsheets... I think it comes down to the volume of information the task requires to complete, and whether or not a performance boost creates a noticeable difference.

[@studiohonzik]

i love this videos, keep going!

[@CodingWithLewis]

Glad you like it!

[@umikaliprivate]

I personally like to finish the project fast, and then optimize. I enjoy both the result, but optimization is really cool.

[@CodingWithLewis]

I 100% feel ya. That's why it's always so hard to saw which one you are.

[@DanielTorres-gd2uf]

Love this video, I work at a start up and definitely am learning both sides of things, but results seems to be taking the cake!

[@ged9925]

I'd prefer to be craft-based, but deadlines and job requirements force me to be result-based.

[@MusicEngineeer]

That resonates strongly with me. Thanks for making me aware of this dichotomy. It now all makes sense. I think, I fall squarely on the crafter side. That's why I have a massive amount of loose ends in my codebase (low level number crunching and signal processing algorithms that do cool stuff) but never get to shipping anything.

[@tdrg_]

I start with the result-based, then I go crafter, and in the end my project never ships anyway because I either realise I’m wasting my time on a useless product or I just lose interest

[@JStudios6118]

The thumbnail is frighteningly accurate 🙃

[@Android-17]

Awesome content as always🚀

[@gregsar1321]

I would definetely be craft oriented, when i first started using python i was very frustrated by how i didnt understand how things worked under the hood. Result based is more usefull when you have deadlines and stuff. But learning the computer magic in every finest detail is what gets me hooked up on a project that challenges to learn new stuff and problem solve my way into finishing it.

[@josephp1263]

Great content!

[@realgoatzy]

I am definitely result based, because i'm willing to make my code absolute dogpoop just to get the result I want 😂

[@CodingWithLewis]

Me too

[@tsunami870]

Just a crappy programmer

[@realgoatzy]

@@tsunami870 ??

[@TheCommunistRabbit]

@@tsunami870 every programmer is a crappy programmer

[@RanCham727]

​@@tsunami870 you probably can't even code a hello world app in html

[@cody_codes_youtube]

Immediately saw prime on the result end and I would have put him as a craft!

[@CodingWithLewis]

content creators have to go on one end!

[@thomas.thomas]

are you sure about that? he is focused a lot on getting things done

[@cody_codes_youtube]

@@thomas.thomas personal opinion, I think yeah. What I watch he seems to go deep on a lot of the craft of languages and can speak in great detail about the tech. I don’t hear much about “this will be good enough for the user, it’s fine”

[@slappy_chimp]

Him and Teej are on the craft side, Theo definitely is on the result side

[@jameslay6505]

Yeah I think prime is leaning in the craft direction. There's tons of content creators who are strictly craft, like Jonathan blow, or Casey muratori or low level learning... they're just not as popular. People like results.

[@joeldick6871]

I've always been primarily a craft-based programmer, and it always slowed me down. Recently I wanted to pick up web programming to build a web app, and I wanted to add user authorization functionality. I immediately went to a third party SSO service that just works, and since then, I've learned the benefit of being a results-based programmer. Now I like to put together web apps in an hour or two, and it feels so freeing.

[@johnmoff9324]

Don't think the choice of language to use implicitly place you in either side. There are python devs who really care about the craft in their code.

[@autistadolinux5336]

for the last point you made, there's a talk from Brian Kernighan talking about succesful language designs. The problem is not the language, it's the tool you took to solve the problem. AWK is awesome to process text but you might not want to use it to make a game. You might want to write your http server in C, but generally it doesn't matter because your program will be IO-Bound anyway and there won't be any amount of requests to process for you to even think about implementing the thing in low-level languages, and if you reach the point you are required to write things in low level, if you started at high-level you now just need to "detail the thing a little more", you already have the thing done.

[@2000krzysztof]

I would put myself somewhere near the middle leaning to results side of the scale. Im not too interested in low level programming but i don't like when a framework does too much for you either. When i code i like to know whats going on and i like to have my code organised and clean.

[@juanandresnunez658]

More than anything your thumbnail reminded me that I'm the kind of dude that daily drives Arch Linux, is learning C/C++, wants to avoid webdev, and uses Nvim, but has never been employed.

[@fabricehategekimana5350]

Interesting video ! I think I am more in the craft side tbh. I LOVE tooling. I especially love tool's philosophy, and terminal tools. My most interesting project is building a programming language

[@marloelefant7500]

I am a craft based programmer by heart, but I often force myself to care more about the result, because I noticed that if I'm too strict with myself, I won't get anything done. A bad solution is often better than no solution.

[@aryajpegasus]

started as a result based, shifting more and more to craft based as days go by

[@Karurosagu]

7:22 With python and other languages that live in that same gray area you can be either tilt to Result or Craft depending on what do you do with it: Machine Learning or backend with Django of Flask, etc... is straight up Craft, desktop GUIs may be in the middle, and scripting where the language, its practices and the necessary tooling for it aren't the protagonist is very close to Result driven

[@AndrewI-n5l]

I'm in between: I want the solution quick, I'm experimental, and I want it to be good and efficient.

[@allancorp_official]

Sometimes both just it according to the project i am working on

[@markjohnmalanteno4655]

My type of programmer depend what role I am doing: In backend, I am more on Result Based programmer, why? the reason is that BE is more inclined on the result such as security and stability. In frontend, I am more Craft Based programmer. The reason is that FE are more inclined on the User Experience, it will directly affect the user which need to be easily customizable on the programmer. But overall I am more result based programmer, because I am more on the side of BE development. I am doing modular code on FE if I have time such as Pagination Scrolling, Modal and many more. If craft-based is 0 and 100 is result-based, I am in the 70... On my opinion: Result Based Framework BE: Laravel (Which I used) FE: Vue Craft Based Programmer: BE: Node JS or any Vanilla FE: React JS (Which I used) or any Vanilla

[@Tayoky]

me : create game so i create my own game engine in c only unsing the clib and opengl defenitely craft

[@ratstam5428]

12 seconds 0 views, bro fell off

[@CodingWithLewis]

Deleting my channel

[@akuoko_konadu]

@@CodingWithLewis😂

[@zapz]

Don't do it, i will watch 4000 more time

[@ratstam5428]

@@CodingWithLewis nahh I'm watching every vid, really loving the effort and hoping you reach more people than ever

[@Rick40867]

​@@CodingWithLewis😢

[@SWEbigbox]

i think im in the middle, i want my code to be good anf at the same time just want the result.

[@zoomstrikegaming]

i like to see myself closer to the craft end of programming. Any programmer should be able to do both, but I prefer to optimize things, as a lot of inconveniences in everyday apps I use are always caused by result based programming. Im not in industry yet and I know industry will require me to be results based, but in my side hobbies, ill make sure every line of code follows a standard, and make sure to remove restrictions that may result in issues further down the line

[@TheDarthVi]

I think there might also be another axis for types of programmers when you also take into account testing: on one end you have Black Box Unit Testing and on the other end you have White Box Code Testing (with Cyclomatic Complexity analysis) along with programmers that structure the code as a mathematical proof (probably the realm of functional programming and rule rewrite systems)

[@VaidikKhurana]

yea, i was on the second side. but i think i'm going to the 1st one now

[@mxpf26]

An experienced developer knows both sides, knows when to use which tool and aims for lowest complexity + fastest output. Thanks for the analysis!

[@hedwig7s]

Not exactly sure what I am but I have a habit of spewing shit then iterating over and over until I get something good

[@gungun974]

I’m maybe in the philosophy of your results developer but I more see the world through the simplicity and necessity. For example, I’m creating an audio player for all platforms and before I was embedding mpv but mpv was hard to perfectly tune. So I scrap it for c++ and directly use libav/ffmpeg for decoding my files in the most efficient way but it’s was not the goal to be perfectly optimized but more the necessity that mpv couldn’t fulfilled me. Every thing is trade off

[@Чумак-щ8и]

Hello Lewis!

[@CodingWithLewis]

👋👋👋

[@Чумак-щ8и]

@@CodingWithLewis Your videos are amazing!

[@yalnisinfo]

I would just fall out of one side of the edge 😂

[@mienislav]

I work for a large fintech company, where I mostly operate on Java. I do many personal projects in Python and learn Rust. To be honest: I'm rather a craft programmer despite coding mostly in "result-based" languages. My priority was always writing easy to maintain code, readable and optimised (where I see a potential). Sometimes I even have some tendency to premature optimization stuff or to write too complex architectures (easy to extend, hovewer too complex for solving a simple problem), however I try to change my habits and follow more of result-based principles but still keeping some of craft ones.

[@ArielAlejandro-j5o]

As always, if there is two sides of for a good reason. Both have their case-scenario to be the best choice. For example, If I have the time and the interest I'm gonna dive in. Learning the hard way. If it's not the case, then I will prefer dedicate my efforts in doing things that will pay my bills now.

[@Admeen3581]

Definition of craft based programmer is the devs who made roller coaster tycoon

[@mr_minepiesek]

For me it depends, for example if I'm working on my own apps I first write a prototype of the feature I want to add and then rewrite and optimize it, and if I doing an exercise at school I do it as fast as possible, but since my classmates just have started programming, I have a lot of free time, so while waiting for them to finish I optimize my code.

[@RA-xx4mz]

The “best” programmer is the one you need to be to take it to your skills to the next level. If you’re learning and starving, prioritize making something, anything, that works. If you’re employed and secure-ish, prioritize developing craftsmanship.

[@filip0112]

I’m really on both sides, sometimes to the craft sometimes to the result

[@bananaclub69]

I love these opinion-piece interactive video type essays

[@xb_salami]

I feel like it depends on the situation and what your trying to achieve. Me personally, if I'm committed to learn how something works and make my own implementation, then I will take the role of being a craft programmer. I can then be a result programmer by just using the tool I made to get things done. If else, I'll just use a library someone else made.

[@ducodarling]

A perspective from someone (all the way) on the left side of the scale: There is no difference between me and my software. It's like a katana in the hands of a samurai. I don't need docs because it's faster to read the code, if I even have to. I can refactor my code while sleeping, or just for fun. I dream up new features in full detail... To read my code is to understand me. To write it is to know me.

[@saturnYTper]

I am definitely on the craft side of programming. I don't really care for the frontend that much when I write code and I mostly focus on the functionality.

[@nihnjastar]

I feel like everyone benefits from having a somewhat result based focus. By better understanding your use case and what you are trying to deliver, you have a more clear picture of what kinds of optimizations will have the biggest impact on your project and your company. You get to get the most value out of your time instead of adding unnecessary complexity for little payoff.

[@nihnjastar]

However I disagree that people who are careless with code quality are truly results based. Piling on tech debt will only slow you down in the long run.

[@Android-17]

7:21 So you declared war against Rust Community🦀

[@GordonRoland]

My experience has been a little different. The two types of programmers are: Those who "wouldn't have done it that way" and; Those who actually get things done. Solid "like," BTW.

[@kevin.malone]

Sorta depends on what I'm working on. I'm probably middle right of the scale, but I lean further left when working at my job. When I'm working on personal projects I feel the freedom to move further into the right. But the longer I'm in the industry, the more I move left. It's just a pain to be lazy and cause yourself immense trouble down the road.

[@michael_ibeh]

I am in between; I like to ship fast, and i care about the code quality, but i dont like overengineering, but sometimes, i prefer to build my own custom solutions.

[@CppDemon]

Im more in the craft based but deadline be hittin hard sometimes.

[@cocoasulphur]

What about craft vs result-based video editors...? 🤔

[@CodingWithLewis]

wrong channel broski

[@cocoasulphur]

@@CodingWithLewis 💀

[@iexist_nt]

personally im result, but it's also more of "do things correctly so you don't screw yourself over a few months later"

[@Argletrough]

A lot of the time, I go off the end of the scale in the craft direction and end up producing nothing 💀

[@AnonymousAnonymous-l2i]

I'd love to know which tech is used for these nice comfy animations :)

[@darkdudironaji]

To put it simply, the results based programmer is the person that takes the products created by craft based programmers and duct tapes them together into a working product.

[@thomas.thomas]

thats just what you think to make yourself feel better writing a program in Java instead of Assembly is result based . and the code can still be of good quality

[@AnonymousAnonymous-l2i]

Spot on and the more up in the duct taping hierarchy they are the more fancy the names they give themselves - it's like compensation from insecurity knowing that they don't do shit - big boy titles like dev ops architect or cloud solution engineer where real hackers just lay low and take pride by seeing their work done up and going.

[@mage3690]

I think the world should endeavor to let everyone be an artist. For some of us, art is found in in cglm and SIMD; for others, in pretty colors and graphics on a webpage. I can definitely appreciate both, but I prefer SIMD and _speed._ There's nothing more satisfying to me than when I ask my computer to do something, and it happens in nanoseconds. One frame is entirely too long. Seconds are an eternity. God forbid it takes _minutes._

[@noisetide]

5:54 Ah yeah... I should definitely optimize my social "ife"

[@ThisIsMMI]

I will definitely fall under result based programmer. I really respect the craft based programmers though, without them programming would be insanely difficult.

[@nonesubham]

"Wait a minute, which category do I belong to if I'm neither a craft-based programmer nor someone who gets results in result-based programming?"

[@zejwier5442]

I don't think that should be a debate about programming languages but rather about how much care you are willing to give to the thing that you are writing. You can implement db engine in both Python and Rust and it will be as hard in both languages to come up with ideas, it's more like do you care to implement this and if you even should, just like always it's about tradeoffs.

[@kcalmwinds]

Missed opportunity to use the "turtle"cursor

[@ltecheroffical]

Here is where I fit on this scale in normalized [0, 1], 0 being craft based and 1 being result based, i'd fit at 0.35.

[@ahmadhassan90590]

I think it depend on project on which you are working that which type of programmer you become for that project.

[@rogersmith258]

I'm procrastination based, I neither get results nor engage in depth with the craft.

[@qy9MC]

I am craft based: I code in C I use linux

[@SteveEngebretsen]

Ouch. I see myself in thy mirror. 🥸

[@purpasmart_4831]

Same here

[@technogodCEO]

I think i'm a amalgamation of both

[@paca3107]

I love learning CS so I am a craft programmer, but if I had to make a real project for money I would pick up the easiest and the fastest way. Imo Good programmers are on the middle of scale

[@Jeremyak]

I enjoy my handcrafted artisanal small batch software engineers.

[@CarlosGonzalez-mp9re]

I don't think that "craft-based care about programming and result-based care about software" is the correct dichotomy here. I think "craft-based" developers think about software as a tool, and as such it must solve a real problem in the most efficient and consistent manner, while "result-based" developers think about software as a product, and as such it must be produced ASAP, and it must be attractive to be sold and/or used. I'm more of a craft guy, but it makes sense that if your goal is to sell, you go for the second mindset. Technical debt doesn't matter that much when your product might not even be sold and you have to abandon it for other project.

[@ofofononoumoren]

Absolutely a results based programmer.

[@Meow_YT]

lol, I see myself in both types, depends on how I wake up... makes it hard to get things done tbh.

[@2penry2]

Indie hackers "mOvE fASt aNd BrEAk tHinGs, cUsTomEr's dON't cArE aBoUt code qUaliTy" also indie hackers, "why are these critical third parties of my app breaking things, my customers will be upset at their lack of quality control"

[@Mr.BinarySniper]

Congratulation. another debate has just started.

[@dimiterpanchew8415]

I'm more of the worst of both worlds, i write everything from scratch in c++ but i make it so messed up and confusing that it's not scalable or fast.

[@greendsnow]

Definitely "result based". I'm not an engineer but a dev, a wrapper dev. I wrap. I don't contribute to open source either, I am not capable of reading and understanding somebody's 100mb thoughts. I listen to books. I use AI, extensively. But I totally respect and love the library maintainer type of programmers. I'm like a forgetful fish 🐠 🐟 🐟 next to them.

[@rcookman]

Not heard that one before but I was thinking something similar recently. So yeah.

[@zaneflow]

the ones that went to university and the ones that didn't

[@Αλέξανδρος56]

Not carrying about maintenability isn't really a 'type' of programmer but moke like a flaw in my sense...

[@LarryRobinsonintothefog]

I was more of a Craft programmer (or leaned that way), but guess it takes a mixture of both.

[@VOgaming51official]

I'd probably fit somewhere in the middle

[@T1Oracle]

Okay, but I love the craft of programming and I love using the latest cutting edge technology so long as it improves the craft of programming. For example, when Rust came along, I felt like I had been waiting for that language for 8 years. I even had my own "language manifesto" describing something very much like Rust. Oftentimes I look at "tried and true" tech and I hate it, because I know that it has issues that I don't feel it should have. Like C++ having smart pointers but still not enforcing their use. Or Java having tons of libraries with "method not implemented" exceptions. Then why are those methods there? Or languages that let you pass a string when you need an int? Just because it's old doesn't mean it's good.

[@RishitSrivastava007]

i am a little bit and little bit there.

[@Meleeman011]

i think i know why i'm not popular on youtube, i'm more craft based than results oriented.

[@samgould8567]

It’s a yin and yang situation

[@teenriot-de]

One end are scientists - the other end are engineers. I think we need more scientists at the moment since programming is still unstable, it still searches for fundamental laws and cant even answer if such laws exists. Programming is like alchemy before there was chemistry. Engineers slow down this process. Thats why a trillion dollar industry uses Javascript, HTML, SQL. They are are using unstable prototypes because of the engineers.

[@kiyasuihito]

I'm both. Craft is the only way to drive results. Can't sustain a software business without solid architecture! It reduces business risks such as delayed time to ship to market due to unplanned work spent on fixing the technical debt the "results" guys left us and customer dissatisfaction from partially implemented features or bugs. 😅 no hate but you know it's true.

[@trstensvold]

Think I lean Craft, but see speed useful in prototyping and such.

[@Jukebox300Minecraft]

I haven't done any coding professionally yet, but shouldn't I be given specifications for how reliable, efficient, and readable a program should be? All I care is that these specifications are met given that they're appropriately defined.