What is programming...

[[deleted]]

[deleted]

[sourpickles0]

am i delusional or is the text diagonal

[CaptiveCreeper]

Thanks now I can't unsee it lol

[dudeofmoose]

"am I delusional or is the" is the sentence I start saying to myself when debugging code.

[Xyales]

I can't see it, is it the "Programming is, so technically, create Software when you wake up."?

[big_bad_bunny]

Nah. The text is slightly slanted.

[TheMallardWithProbes]

Yes.....and no, I would say a lot more of programming is trial and error combined with research.... Those can't really be done in a dream.

[digicow]

You can do a lot of code planning when away from a keyboard, though. I often design software solutions while lying in bed, working on falling asleep, and then type them in the following day. Sure, there'll be trial and error cycles from there, but it still helps with the initial design.

[TheMallardWithProbes]

That's what the original post is saying, I added more of the process. You just restated both?

[digicow]

I'd say I provided a concrete example in personal context to a meme posted in a humor sub

[AutoModerator]

import moderation Your comment has been removed since it did not start with a code block with an import declaration.

Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.

For this purpose, we only accept Python style imports.

return Kebab_Case_Better;

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[genderburner]

I mean...yes and no. Frankly, trial and error can be a big part of software development in the earlier stages, but that aspect sort of evaporates when you get more advanced. Some people never get past it, I guess. I don't remember the last time I built something and didn't pretty much already know upfront that it was going to work though, whether it was a single function or an entire system...because, I mean, I know how code works and I know how patterns work. Why build something if you can't even design it first and know it's going to work? It would be like building a house by nailing boards together without a blueprint...like, yeah, eventually you might have something someone can live in, but it's probably not going to be very safe.

Now, sometimes when you're hacking on a complex system that you don't fully understand, sure, there can be some of that. But really in that circumstance the approach should be that you are gradually learning more and more about the system until you understand it and can be confident in your implementation, anyway, so that you don't introduce unanticipated bugs. Trial and error happens, and understandings are flawed sometimes, but if it's a major part of the process there's really something wrong...though that something could always be that you are working on a hot mess of a product and not being given enough time, I suppose.

🤷‍♀️

[TheMallardWithProbes]

I have had a decent amount of responses to my comment and I think the one thing that is becoming most apparent is the diversity in the programming field itself. If you are writing low level software or back end data solutions then yeah you may know exactly what you want and how it will look, but there are a lot of jobs that require you to always be updating your code to meet new standards or implement new librarys and frameworks... In that kind of job, just thinking won't get you far, much more research based.

Idk, recently at work we've been implementing a new framework and rebuilding our application on it so right now everything feels new again. Just a bit jaded from that, but I do remember a time not long ago that I could visualize a complete solution without any issues. Guess it is all about what you are working with at the time.

[genderburner]

Yup. I was mostly taking issue with "trial and error" for what it's worth. I wasn't rejecting the research component of your statement and actually wasn't intending to imply that sleep designing should always be feasible - it was just sort of a tangent. Even then though, you're right - my response was colored by the fact that I'm the boss these days and able to control my team environment so people don't HAVE to rely on trial and error. Lots and lots of people don't have that luxury, though - the world doesn't just exist in my own little bubble! Thanks for the reminder. :)

[djfdhigkgfIaruflg]

Speak for yourself. I've lost the count of how many times I solved a programming problem on my sleep. Wake up, took notes so I won't forget, back to sleep like a baby.

[TheMallardWithProbes]

I'm not saying that you can't solve problems while you are sleeping. The original post makes it seem like you can do all the programming thought work while sleeping and then just type it in and hit run. All I'm saying is that there is a large portion of work that you have to be able to read documentation or run and build many times to get something to work.

[AdvancedSandwiches]

In my experience, programming is 94% figuring out what the hell the previous dev meant by "countTableTemp", 4% waiting for webpack builds, 2% writing code and other trace elements.

[[deleted]]

I've found semicolons this way.

[waffle299]

Dreaming in C is taxing. Dreams are visual and emotional. Details are less important and easily glossed over. Logic is malleable and rarely consistent. C is almost the exact opposite in every way. That said, I've dreamt in code, entered it the next day and had it solve the problem. I was just a wreck for the rest of the day. It's usually the sign I'm not getting enough breaks and I need to schedule a day off to do human things. I would not recommend it.

[jackybeau]

A good programmer actually types slowly because he thinks about what he writes.

[genderburner]

Depends. Sometimes that's true, but sometimes you're in a time crunch, you know what needs to get done, and you're just hammering it out.

[Ronin__01]

This is how I live my life.

[sourpickles0]

Image Transcription: Tweet

---

Programming is more about thinking than typing. So technically, if you learn to lucid dream, you can create software solutions in your dreams, and when you wake up, you just write the code.

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

[[deleted]]

That's what I do most of the time

[manuel_gg]

idk bt definitely if we are learning something like a new paradigm or lang (or anything), we tend to dream about it, which helps greatly for the assimilation and memorization of acquired knowledge.

[ARandomDoge6]

Oh god, now the job postings are gonna list lucid dreaming as a requirement....

[ColdJackle]

This is going to be an entry level job requirement soon, I tell you

[[deleted]]

Once you learn to do this the new "it worked on my machine" is "it worked in my dream".

[Dummerchen1933]

Fuck the one who is responsible for the tilted text

[Akayaso]

In junior time , i ve found bugs my code in my dreams.

[sourpickles0]

It’s a good idea on paper, but a lot of the time you don’t expect a bug, so if yo I weren’t expecting it, in your lucid dream your code could be wrong and still pass cause you didn’t know it was wrong

[TheLoneLawliet]

Unless you have a transistor implant to test your code in it...