Live data from Hacker News

You’re not writing code, you’re solving problems

lanraccoon.com

91–100 of 143 posts

Re: You’re not writing code, you’re solving problems

#91

NOTE: This is tongue-in-cheek (for the most part). However, I cannot help but feel that articles like this are a subtle form of social manipulation; especially for younger, less experienced programmers. From the article: * The software is not the purpose Translation: your craft, how you do it, and why are not important. Going meta for your profession is not valued and if people see you doing it, you're in trouble. Le…

> I cannot help but feel that articles like this are a subtle form of social manipulation; especially for younger, less experienced programmers.

Indeed, I'd go as far as saying this is straight up managerial tautological BS like I've heard many times.

"If the software doesn’t do what you need it to do, it’s useless.", said Captain Obvious. Well, of course it must solve the problem, but that's not enough, far from it.

And then the article promotes things like wordpress and webflow... well, I for sure know what code base I won't have to deal with when a bad plugin will break the "best code is no code" mantra.

Re: You’re not writing code, you’re solving problems

#92
post #87

Depends on the language. I find that in C++, I spend a lot of time working on figuring out the language, while in python I spend far more time solving the actual problem.

Hoh! I spend most of my time figuring out pipenv (not my design choice!) .

Don't use pipenv, you don't need it. Seriously.

Edit: you don't need poetry either.

Re: You’re not writing code, you’re solving problems

#93
post #87

Depends on the language. I find that in C++, I spend a lot of time working on figuring out the language, while in python I spend far more time solving the actual problem.

Hoh! I spend most of my time figuring out pipenv (not my design choice!) .

Python packaging is now a solved problem.

Use Poetry. Resolves all your dependencies and manages your virtual environments.

Also lets you build and publish your own projects with a few commands.

https://python-poetry.org/

Re: You’re not writing code, you’re solving problems

#94

Depends on the language. I find that in C++, I spend a lot of time working on figuring out the language, while in python I spend far more time solving the actual problem.

Yeah same in Clojure, you spend most of your time messing with/writing interop and trying to get it correct.

Re: You’re not writing code, you’re solving problems

#96
post #92
post #87

Earlier quoted context omitted.

Hoh! I spend most of my time figuring out pipenv (not my design choice!) .

Don't use pipenv, you don't need it. Seriously. Edit: you don't need poetry either.

Yes I do, sadly, I need it for my job. I don't like it, and I want it replaced, but until then I have to commit to the decision my team has made.

Re: You’re not writing code, you’re solving problems

#97
As a literal example, I've occasionally been asked to put some process that was previously done physically "on the computer". That is, perhaps a paper log of some important activity that they'd now like to have a program for, or a physical token system for tracking a critical resource.

Often computerizing is useful, but sometimes it turns out that any conceivable software version would actually be significantly worse than what they're already doing.

In a case like that, you truly can solve their problem by not writing any code.

(Obviously, this only works if they ultimately agree.)

Re: You’re not writing code, you’re solving problems

#98
post #96
post #92

Earlier quoted context omitted.

Don't use pipenv, you don't need it. Seriously. Edit: you don't need poetry either.

Yes I do, sadly, I need it for my job. I don't like it, and I want it replaced, but until then I have to commit to the decision my team has made.

Well, I can only sympathize then...

Personaly I just stick with manual venv and pip. It's not hard to use, it works, it's standard. But of course I'm lucky enough to be the one making the decisions.

Re: You’re not writing code, you’re solving problems

#99
post #92
post #87

Earlier quoted context omitted.

Hoh! I spend most of my time figuring out pipenv (not my design choice!) .

Don't use pipenv, you don't need it. Seriously. Edit: you don't need poetry either.

Is there a better way to get a lock/freeze file that includes checksums?

Re: You’re not writing code, you’re solving problems

#100
post #41

"You're not cooking meals, you're solving problems"

You're missing the point. The goal of cooking meals is to have a meal at the end. Because people need to eat. The food is the solution to the problem you have. People don't consume software, slurping up lines of code like ramen. Having a steaming bowl of software is not the end goal. The end goal is to solve some _other_ problem which may or may not, once you dig into it, require writing software, and if it does then…

I am afraid, as jackcviers3 already said, you are missing the point.

The goal of making applications is to have a piece of software at the end. That piece of software is the solution to the problem you have.

Actually, in that very sentence of yours you explicitly repeated what I already wrote

Post reply on HN