441–450 of 480 posts
I'm a Financial Analyst, CPA, CIA, CTA, Statistician, Expert System Developer, Using Clojure, R, core.logic, PostgreSQL, etc. All professional knowledge is self-learning. The founder of The Pure Function Pipeline Data Flow. [The Pure Function Pipeline Data Flow]( https://github.com/linpengcheng/PurefunctionPipelineDataflow )
No CS degree is fine when you’re doing trivial programming work that doesn’t really matter, such as application frontends. But could you imagine riding in a plane or using critical infrastructure services programmed by people with absolutely no computer science degree to their name? Not a chance. Like getting surgery from a butcher.
In at least Sweden's machine industry programming is just something you learn in your engineering role by osmosis and revulations from God, and typically one to three 7 week courses at university.
Volvo Cars, Volvo Trucks, Scania, SAAB etc.
There's clearly strong feelings in this thread. Whether or not a degree is necessary, I think we can say there's two groups: - People who went to university, going through significant effort for their degree, and want to defend that choice - People who _didnt_ go to school, perhaps suffering from a touch of imposter syndrome, who want to hide their insecurity I'm a 20yr old "self-taught" dev. I'm considering going ba…
> There's clearly strong feelings in this thread. It's always like this when it comes up, which is fairly often here, and I think you're right to point this out. It's an emotionally loaded topic, which means it's a hard one to actually get useful data from. I think there's a couple of things going on here: The path someone takes to get where they are is a huge part of their identity. So when they look back on their o…
Not going to school gives you more freedom to explore your interests and choose a unique, idiosyncratic path. If you are driven and focused, you can get farther down a road than most others will because you have the freedom to focus on areas where you are passionate.
This is me, but I know this is not for everyone. I would advise going to school to make it easier in the long run. Passion for your work and the focus to pursue it is very important to get somewhere.
If school worked like it does today, 20 years ago, then maybe I could've finished it.
Earlier quoted context omitted.
I'm not sure he never was at university, I just assume not [1]. > why are you drawn to Haskell? I just want my programs to work. I've seen too many null pointer exceptions and other runtime errors. Runtime errors = bad. Compile errors = good. [1]: https://news.ycombinator.com/item?id=20112065
"I just want my programs to work" Me too ... And I think imperative languages are way more easy and clear to read and write. I allways imagined that you have to be a math nerd to prefer Haskell, but apparently this guy is not a math guy, but loves Haskell .. so ok, good counterpoint.
Because it's what you've had exposure to. Perhaps, they're even objectively easier to read and write, I don't know. It's also completely besides my point.
My point was that I want my programs to work as desired. That's orthogonal to how easy it is to read and write. I don't want runtime exceptions where I could've gotten a compile-time error.
No CS degree is fine when you’re doing trivial programming work that doesn’t really matter, such as application frontends. But could you imagine riding in a plane or using critical infrastructure services programmed by people with absolutely no computer science degree to their name? Not a chance. Like getting surgery from a butcher.
Earlier quoted context omitted.
That doesn't matter. If there's one thing my years in this career has taught me, it's that the client(s) don't GAF what language or framework or system you used to solve their problem(s). What they care about is if you have given them a solution that solves their problem(s). They don't care how you got there. They don't care what technology you used. Just as long as you solved the problem(s) they were having, and tha…
You said a lot of words and assumed a hell of a lot of things that were not contained in my question. I simply asked a simple question out of curiosity, JFC. Does curiosity matter? For the record, all code is ephemeral so since you're going to end up throwing it away anyway one day, it doesn't fucking matter what language you start with. Pretty much any language can back-end an API until a certain (large) number of u…
Earlier quoted context omitted.
I had a similar experience with C64 and its User and Reference manuals at that age. I was thinking about that a couple of months back, and found that they're still out there as PDFs of the originals: https://www.commodore.ca/commodore-manuals/
Ive been wanting to do something similar with Python. Time has been the issue.
Earlier quoted context omitted.
So, in reality, you have no idea if your idea is truly better and it looks like you just ran some specific test cases and assumed it applied. Still paper worthy, but far from thinking that you made anything better than published literature. And the goal isn't to "personally benefit" it's to know that your ideas survive scrutiny and contribute something meaningful to the world.
You're making a lot of assumptions there about which your mistaken. I don't need to defend myself here. If that's what you want to believe, that's fine.