I’m clicking my mouse as fast as I can but nothing is happening.
How many clicks until my awesome app is finished?
There lies your problem, ditch mouse use vim(neovim if want to impress the ladies).
vims that thing were you type emoticons everywhere right? :q :w :e
It’s 2024 we only use emojis now 😎
:u :w :u
deleted by creator
Careful with that, occasionally you can develop some pretty nasty emacs hand
Removed by mod
Emacs for coding. Fight me.
I agree Emacs is agreat OS, but sadly it doesn’t have any good text editor.
It does(evil)
The mistake is clicking it, and not speaking to it. Try “hello computer”.
Have you tried clicking on rhythm? Have you tried different rhythms?
As a developer I object to your assumption that I need a mouse to do my job. The only thing I need a mouse for is outlook and I’d definitely be more productive without it.
This is my imposter syndrome.
I’m a senior engineer now and I’m a big mouse user. It’s more intuitive for me. My productivity is certainly not bottlenecking on how fast my hands move on the keyboard. .
My productivity is bottlenecked by the number of meetings I have to attend, random slack messages that need to be responded to, and distractions IRL.
I’m not going to shame anyone about using a mouse unless you also always right click to copy/paste.
Only because I have figured out how to copy from vim to other apps without the mouse yet.
If you ever find out a way, please DM me
I’ll probably get back to you in a few years, still mastering the motions and actions.
Haha, same lol
Hey, if you’re still wondering, I found this on SE: https://vi.stackexchange.com/questions/84/how-can-i-copy-text-to-the-system-clipboard-from-vim
Thank you for this, now I know I have 26+ registers to store stuff in as well as the system clipboard! Honestly been so busy I haven’t touched my computer in over a week.
Nah fuck the haters, the keyboard-only workflow may be technically more productive, just like a Dvorak is better than a QWERTY, but what matters is your output and your quality.
People will spend hours learning things that save them seconds.
One of the best programmers I worked with was a hunt and peck typist.
His code was meticulous. I frequently learned things reading his PRs.
Pair programming with him otoh…
I choose to eschew my mouse when I can because it’s easier. I don’t have to move my arms around as much, and I can work quicker. It’s more comfortable. All of this is a preference thing, why should anyone do something my way if it’s not how they prefer?
Great perspective. If we are codeving or screen sharing, I’m fast and fluid. I just move differently.
Skiing vs snowboarding
Disclaimer: I have never used this but I did a Google for you. It looks reasonably maintained.
It’s for navigating web documentation when arrow keys are too fine but page up/down keys are too coarse.
I guess you could hit tab 9000 times to get to the right hyperlink. I’ve done that when setting up Hyperland on an Nvidia GPU and my cursor was there but invisible.
“If you wish to be a writer, write.”
Epictetus delivered this burn over 1900 years ago.
Is that actually a burn? It depends on the context.
It’s the same thing whenever I hear somebody say “I wish I could draw like that.” You probably can, but it would take hundreds of hours of practice. Of course, people wish that there was some shortcut, so that they could get the skill without all the work.
Yeah but I feel like there’s a million books been written since that time which point out how vapid this quote is. To write one must know what you want to say and how to convey it, do you really think it’s better to just dive into a task unprepared and muddle through rather than learn first the structure and ideals behind such work?
I would say both. You need to learn by trying things out, making your own mistakes and finding a style. Then you get input from the outside world on why some peculiar structure make sense or just giving helpful tips. Then you try out more, apply those tips and see what works for you. But you can read as much helpful input as you want, it won’t be any good without you trying to apply it and practice.
At the end of the day, both are required. You need to study to be effective at what you’re doing, but at the end of the day the only way words get on paper is writing. You’ll also get more out of learning these structures and ideals trying to apply them after you have a bit of time just floundering, getting a feel for the actual task.
Yeah, came here to compare. Both are wrong. If you wish to be a writer, write. If you wish to be a good writer, learn something. Same with programming, except programming requires something to function so it’s even worse in that regard.
Fuck me right in my ADHD. But it is true
Pick a language. Keep it simple. Make something.
Bonus points if it’s something very simple that you’ll use.
Tic tac toe. Fizzbuzz. A score pad for a game. Something that can theoretically be done in an hour (if you were an expert).
Don’t forget to RTFM
Someone documented enough of a thing to call it a manual?
Manual? You mean the half-finished wiki someone put together that is the only source of information while also missing the information I need?
If anyone genuinely feels this way and wants to get started in coding, I highly recommend doing one of the mooc.fi courses. Codecademy is fine as a taster/refresh but don’t waste money on the premium when something like mooc is available for free.
For many, like me, coding just isn’t how our brain works. Even if we are interested in it it’s basically impossible to get a grip on it. I can figure out code that’s already written and do basic editing of it but anything more than that just doesn’t click no matter how much time I spend trying to learn.
It takes 3-6 months for the concepts to click, speaking from experience.
The funniest thing for me is that the definition of object oriented programming is a source of confusion as a beginner yet the most succinct definition as an intermediate/ expert.
It’s just telling the computer in a very detailed way. Are you monolingual? I think the concept of learning how to code is easier if you speak more than one language.
I want to preface this with the mention that understanding other people’s code and being able to modify it in a way that gets it to do what you want is a big part of real world coding and not a small feat.
The rest of my comment may come across as “you’re learning wrong”. It is meant to. I don’t know how you’ve been learning and I have no proof that doing it differently will help, but I’m optimistic that it can. The main takeaway is this: be patient with yourself. Solving problems and building things is hard. It’s ok to progress slowly. Don’t try to skip ahead, especially early on.
(also this comment isn’t directed at you specifically, but at anyone who shares your frustration)I was gonna write an entire rant opposing the meme, but thought better of it as it seems most people here agree with me.
BUT I think that once you’ve got some basics down, there really is no better way to improve than to do. The key is to start at the appropriate level of complexity for your level of experience.
Obviously I don’t know what that is for you specifically, but I think in general it’s a good idea to start simple. Don’t try to engineer an entire application as your first programming activity.Find an easy (and simple! as in - a single function with well defined inputs and outputs and no side effects) problem; either think of something yourself, or pick an easy problem from an online platform like leetcode or codechef. And try to solve the problem yourself. There’s no need to get stuck for ages, but give it an honest try.
I think a decent heuristic for determining if you have a useful problem is whether you feel like you’ve made significant progress towards a solution after an hour or two. If not, readjust and pick a different problem. There’s no point in spending days on a problem that’s not clicking for you.If you weren’t able to solve the problem, look at solutions. Pick one that seems most straight forward to you and try to understand it. When you think you do, give the original problem a little twist and try to solve that. While referencing the solution to the original if you need to.
If you’re struggling with this kind of constrained problem, keep doing them. Seriously. Perhaps dial down the difficulty of the problems themselves until you can follow and understand the solutions. But keep struggling with trying to solve little problems from scratch. Because that’s the essence of programming: you want the computer to do something and you need to figure out how to achieve that.
It’s not automatic, intuitive, inspired creation. It’s not magic. It’s a difficult and uncertain process of exploration. I’m fairly confident that for most people, coding just isn’t how their brain works, initially. And I’m also sure that for some it “clicks” much easier than for others. But fundamentally, the skill to code is like a muscle: it must be trained to be useful. You can listen to a hundred talks on the mechanics of bike riding, and be an expert on the physics. If you don’t put in the hours on the pedals, you’ll never be biking from A to B.
I think this period at the beginning is the most challenging and frustrating, because you’re working so hard and seemingly progress so slowly. But the two are connected. You’re not breezing through because it is hard. You’re learning a new way of thinking. Everything else builds on this.Once you’re more comfortable with solving isolated problems like that, consider making a simple application. For example: read an input text file, replace all occurrences of one string with another string, write the resulting text to a new text file. Don’t focus on perfection or best practices at first. Simply solve the problem the way you know how. Perhaps start with hard-coded values for the replacement, then make them configurable (e.g. by passing them as arguments to your application).
When you have a few small applications under your belt you can start to dream big. As in, start solving “real” problems. Like some automation that would help you or someone you know. Or tasks at work for a software company. Or that cool app you’ve always wanted to build. Working on real applications will give you more confidence and open the door to more learning. You’ll run into lots of problems and learn how not to do things. So many ways not to do things.
TLDR: If it’s not clicking, you need to, as a general rule, do less learning (in the conventional sense of absorbing and integrating information) and more doing. A lot of doing.
Underrated comment.
Terrific advice. Baby steps.
I definitely feel this. I had to take a programing course in university and I was easily able to follow along up until the lesson on pointers, whereupon I completely lost the thread and never recovered.
I’ve known a good number of computer scientists over the years, and the general consensus I got from them is that my story is neither unique nor uncommon.
Yeah, some folks have trouble with pointers, and computer-engineering curricula are designed to discourage folks from taking third-year courses if pointers don’t make sense. It’s a stereotype for a reason. I’d love to know if there’s an underlying psychological explanation, or if pointers are just…hard.
I am but one man whose only education in programming was a first year university course in C from almost two decades ago (and thus I am liable to completely botch any explanation of CS concepts and/or may just have faulty memories), but I can offer my own opinion.
Most basic programming concepts I was taught had easily understood use cases and produced observable effects. There were a lot of analogous concepts to algebra, and functions like
printfdid things that were concrete and could be immediately evaluated visually.Pointers, on the other hand, felt designed purely of and for programming. Instead of directly defining a variable by some real-world concept I was already familiar with, it was a variable defined by a property of another variable, and it took some thinking to even comprehend what that meant. Even reading the Wikipedia page today I’m not sure if I completely understand.
Pointers also didn’t appear to have an immediate use case. We had been primarily concerned with using the value of a variable to perform basic tasks, but none of those tasks ever required the location of a variable to complete the calculations. We were never offered any functions that used pointers for anything, either before or after, so including them felt like busywork.
It also didn’t help that my professor basically refused to offer any explanation beyond a basic definition. We were just told to arbitrarily include pointers in our work even though they didn’t seem to contribute to anything, and I really resented that fact. We were assured that we would eventually understand if we continued to take programming courses, but that wasn’t much comfort to first year students who just wanted to pass the introductory class they were already in.
And if what you said is true, that later courses are built on the assumption that one understands the function and usefulness of pointers despite the poor explanations, then its no wonder so many people bounce off of computer science at such a low level.
Thanks for offering your perspective! It’s important that we keep in mind that not everybody who studies computer science becomes a professional programmer, and you’ve offered us good food for thought.
For what it’s worth, pointers are fundamental for Von Neumann machines, which are very common in the computing world; your current machine and the machine serving this page are both Von Neumann. In such machines, memory doesn’t just store data, but also instructions; the machine has an instruction pointer, which is a pointer referencing the currently-executing instruction in memory. So, if one wants to understand how a computer jumps from one instruction to another, then one must somewhat understand pointers.
You are welcome.
Pointers do make more sense to me now than two decades ago, mostly owing to me being married to a computer scientist. But I always go back the fact that for the purposes of my first year programming course, pointers were (probably) unnecessary and thus confusing. I have a hard time understanding things if not given an immediate and tangible use case, and pointers didn’t really help me when most of my programs used a bare few functions and some globally defined variables to solve simple physics problems.
EDIT: I’ll also say that pointers alone weren’t what sunk my interested in programming, they’re just an easily identifiable concept that sticks out as “not making sense.” At around the same time we had the lesson on pointers, our programs were also starting to reach a critical mass of complexity, and the amount of mental work I had to do to follow along became more than I was willing to put into it - it wasn’t “fun” anymore. I only did well on my final project because a friend patiently sat in my dorm room for a few hours and talked me through each step of the program, and then fed me enough vocabulary to convince the TA that I knew what I was doing.
Aren’t pointers just an ID given to a verible that currosponds to its “true” position in the array of bytes thay make up a program’s memory? I feel like I’m missing something
I doubt that you’re missing anything about pointers themselves. I may not have done a good job articulating why non-programmers have a hard time understanding them.
I would attribute this to the difference between programming/coding, and software design or engineering. They’re related but different concepts. Just like a builder and an architect do different things and complement each other to get a building built, these are also two distinct steps. I do think it’s easier and more common for one person to (be able to) do both tasks than in my analogy though, but it’s also done separately often enough (in industry).
My point being: don’t beat yourself up that you don’t know programming, you probably do, it’s the software design that you’re not familiar with yet. But now that you know what is missing, you can look into it and work on it, and gain a valuable skill to complement your existing skill.
Start small, make silly things. Html is probably the easiest thing to pick up and see what your changes are doing almost immediately. Play with formatting and styling, add pictures, learn how to create buttons and radials.
After that I’d start learning how to make stuff happen with JavaScript maybe create a pop-up when you hit a button, figure out how to change the color of elements with input boxes or sliders, etc.
When you feel comfortable enough with the language make what you want even if it already exists. Tic tac toe, a rudimentary blog, Conways game of life. Don’t be afraid to take a break if it gets frustrating and don’t be too hard on yourself if it’s not amazing.
Just remember it takes time, I hear most developers say it takes at least a year of carving a few ours a week just making stuff to really start grasping a language. So just make stuff and don’t be afraid to look it up. The more pointed your questions the easier it gets to find answers.
I jumped head first into c++ my apps are incredibly buggy and run slower than most web apps. They’re only terminal apps but I’m improving and so can you.
deleted by creator
This is my experience. I can understand the fundamentals without trouble but don’t have the ability to plan out the structure of something and write code to make that work.
I’ve done online courses, tried boot camps. It just doesn’t work for me.
if you can use a dictionary, play a card game like Uno, poker, gofish, cheat etc, use an index in an encyclopedia, Google, Wikipedia, and you can do high school algebra you can grasp the basics of coding.
Object Orientated Programming / classes / objects / inheritance is kinda like a card game
All Hearts are a type of card, all Kings are a type of card, a straight is a way of arranging cards, four of a kind is a way of arranging cards. That’s about as complicated as OOP needs to get for a beginner.
Understanding and producing are very different things.
Hold on, no one said I had to learn to know how to code.
I started a CS club in college and it was crazy how many members would tell me this. They would ask me questions like I hadn’t picked up programming the year before and taught myself via the internet. If you want it, it’s out there.
Pfft imagine using a mouse to code.
I’m sure it works fine when held like a pen…
Classic result of a business man in charge of a software company.
LPT: work for a company where the decision maker comes from an engineering background, not a business background.
You’re welcome.
I mean there must be a reason why someone would want to be a dev. I would go from there
What if I wanna learn to code because I want to make more money than what I’m making now but lack creativity to make something like a game or an app that’s supposed to be good practice?
Learn finance and bookkeeping; work for a bank. Software development is not lucrative; the high-paying jobs are fundamentally tough and cause burnout. Median employment at big software companies is maybe 2-3yrs and it will ruin your ability to relate to other humans.
Or work for a software development related to finance and bookkeeping so you get the downsides of both.
You don’t need to make something unique, if your goal is to learn.
The best thing you can do is to build something that solves a problem for you, or to build something that already exists that you know well.
As for money, given that companies seem to love layoffs lately, I would say that higher salaries only matter if you are employed. It’s an employers market right now, and a lot of people are really struggling to find work again, even from large companies like Amazon and Google.
I try to keep an eye out for repetitive tasks that might make good projects. I just started a python script that’s going to download all my google photos so i can free up my cloud storage.
Think of it more like problem solving. Plenty of jobs use software engineers just to code bespoke tools suited to exactly what they need. Someone else will tell you what it should do, you just have to translate that into code. The hard part is more figuring out what they really need/want because what they tell you isn’t always what they want.
Be aware that learning to code is not a safe bet for making money in this market. Of course it’s better to have coding skills on your resume than nothing. Coding also complements other white collar skills well (eg. program Macros in Excel or use Jupyter for bespoke data analysis). But code alone is unlikely to get you cash, in my opinion.
Sometimes motivation can make your better in forced way
Your case same like mine actually. in the end i forced to learn programming because it’s digital era & everything will be digital at some point, at first i admit i suck at everything but as time goes on i can made something better and betterI still remembered the first time i forced my way i learned about programming world especially web dev 14 years ago. I learned WordPress, why i learned it ? because it can make website really really fast, it’s high demand in my country (even today), you can make easy peasy money with it since my client doesn’t care about what tools you used as long as the website is launch and meet their requirements, & it suits for client that have very tight budget
Well nowadays i still learning how to make website & apps in proper way (like true programmer does). I admit it’s hard since i always use the easy way to cheat it, but i will made it through
Maybe next time I’ll learn how to make games since nowadays games popularity has rised so much compared way back then
Where is the guitar?
How do you expect people to become rockstar https://codewithrockstar.com/ devs without a guitar?!
