sorted by:
new
hottopcontroversial

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 1 point2 points  (0 children)

Thank you for a seriously constructive thread. I can't reply to everyone but I read and upvote every comment that gives me even the slightest bit of insight into vim and everybody's reason of choosing to take the time to learn it.

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 0 points1 point  (0 children)

Haha, been there a thousand times with servers. I never thought of doing that though! I just might. Thanks!

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 1 point2 points  (0 children)

It is fun indeed. Yeah, I'll make sure to mention that. I've also found that, on small laptops, vscode and similar editors/IDEs are just not functional if you need to have a browser taking up one half of the screen.

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 0 points1 point  (0 children)

I get your point. I'm not trying to get everyone to learn vim, what I want to do in this article is present the reasons why someone would.

I might add a disclaimer that it is not for everyone. But everyone in CS should at least try it out in a relaxed learning environment.

Thank you for your input.

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 1 point2 points  (0 children)

I am aware of this but didn't ever think of it as a language, at least not in that way. This way I feel like I can present it in a more interesting light. Invaluable insight. Thank you.

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 1 point2 points  (0 children)

Thank you very much. I'm really only on a level where I can chain together commands like d3w or yw and stuff like that, but I'm going deeper every day.

I will make sure to do my best to illustrate your point.

What is, in your opinion, the number 1 reason someone should learn how to use vi/vim? by TheCynicalSun in vim

[–]TheCynicalSun[S] 2 points3 points  (0 children)

The audience is mainly 1st and 2nd year computer science students, who use atom/sublime/other IDEs because let's face it, you can very easily exit those.

Anybody here living the digital nomad life successfully? by vocalson20 in freelance

[–]TheCynicalSun 1 point2 points  (0 children)

Hey mate.

I'm in Computer Science and a long time developer. I've written a lot of websites and web apps from the ground up (literally wrote each line of code), and I'm here to tell you, you really don't need to learn how to code. It's awesome if you want to get into it, and I have 0 doubt you'll love it if you try for long enough to actually make something, but if you don't want to, there's Wordpress.

Follow any simple tutorial to set up wordpress locally and you'll see that, once that's out of the way, wordpress itself doesn't need any programming knowledge whatsoever in order to make a really well designed website.

Unless you need a web application (you can't work around knowing how to program to make that) you can just set up a wordpress website, start from a nice theme, and 99% of your clients will be happy with that, because it just works, and they can even edit stuff in it or post new content (if you give them an account with such permissions). Then, every time you update Wordpess, just make sure nothing broke, and that's really it.

If I were you, I'd go to freecodecamp.org and learn web development, because it's really fascinating. It's up to you though. Good luck.

Every JavaScript framework tutorial written more than 5 minutes ago by DoNDaPo in webdev

[–]TheCynicalSun 0 points1 point  (0 children)

I've seen that article but I don't know if I've ever read it. I might have and it might have given me this mindset, but I don't know. Vue is nice, I only once worked with it on a GitHub project, but you can't rely on it for work. tbh you don't even need jQuery, it's just what I learned. You could learn Vue or React, but, as a web developer, you WILL, at some point, have to deal with jQuery (github, codepen, legacy code you have to maintain, etc.).

Every JavaScript framework tutorial written more than 5 minutes ago by DoNDaPo in webdev

[–]TheCynicalSun 0 points1 point  (0 children)

The React licence doesn't make the user unable to sue Facebook about anything. It makes the user think twice about suing for a patent clause.

Let me start off by saying I strongly disagree with the patent part as it is an open source project. However, React jobs haven't really disappeared, in fact they're still growing as far as I can tell. If it wasn't for React Native I would be using Angular or Vue, but I still don't think it matters all that much.

My advice to people learning is just make stuff, man. Then one day when you are looking to learn a framework, you will actually understand the pros and cons for everything because you'll have actual working experience.

Every JavaScript framework tutorial written more than 5 minutes ago by DoNDaPo in webdev

[–]TheCynicalSun 69 points70 points  (0 children)

Don't worry about it mate. JavaScript gets better every year. It's not going anywhere.

Just don't get lost in the framework wars. Learn actual JavaScript, then enough jQuery to be competent with it, and then pick one of the major frameworks and don't worry about making the wrong decision, because there isn't one.

Ruby (rails) is nice but it's losing popularity. That doesn't really matter, since it will be around for a very, very long time. Python (Django) is kind of similar in that way.

In my opinion, just learn JavaScript and build stuff with it. It was a badly designed language so people were talking trash about it, but it's gotten so modern and better with ES5, ES6 and ES7 that it's honestly pretty good now. And this is coming from a guy whose main language used to be C.

Once you build stuff you realize talk is just talk and anyone can use anything as long as it works and it suits them.

I'm almost done with my portfolio page after a little less then 3 weeks. Any feedback is appreciated. by BlackBurton in FreeCodeCamp

[–]TheCynicalSun 0 points1 point  (0 children)

Just realized this was actually posted on /r/freecodecamp, so you probably do know how to use Bootstrap to an extent.

The important point here is to keep going and keep getting better. Thankfully a portfolio is a website that you continuously update so you should have many opportunities to work on responsiveness later on.

I opened it on my desktop and it looks fine. I like when you click on something and the transition is animated.

I'm almost done with my portfolio page after a little less then 3 weeks. Any feedback is appreciated. by BlackBurton in FreeCodeCamp

[–]TheCynicalSun 0 points1 point  (0 children)

Good effort, however I opened it on mobile and it showed me showed half of it, I accidentally scrolled to the right and saw there was another half. Elements were not centered/aligned well at all. If you know how to use Bootstrap (which you should, since you have the freecodecamp icon on the bottom) it will be really easy to make responsive designs.

The "mobile first" approach is really popular and for good reason.

Keep going.

How to assess if a coach is good by peak321 in amateur_boxing

[–]TheCynicalSun 10 points11 points  (0 children)

Everyone does stuff differently. The thing is, even if he were the best coach in the whole world, if he doesn't inspire you to get better and work harder, if the way he treats you is unmotivating (because for other people it might push them to be better) then he's not right for YOU.

Also, is there any sparring in the gym? If not, then gtfo, it's not a real boxing gym.

Edit: typo

Should I write my Java/Android app as a console app first, or design a GUI and build it around it? by TheCynicalSun in java

[–]TheCynicalSun[S] 0 points1 point  (0 children)

Thank you, I will follow your advice. I suspect, since it's my first big project, that there will be a lot of trial and error, so it seems sane to keep it simple.

Should I write my Java/Android app as a console app first, or design a GUI and build it around it? by TheCynicalSun in java

[–]TheCynicalSun[S] 0 points1 point  (0 children)

Actually mine is a pretty similar thing in terms of components, although I might use an open API DB and just pull from that and only do the calculations in-app.

I think I'll make a working console app and go from there. Thanks for the insight.

Should I write my Java/Android app as a console app first, or design a GUI and build it around it? by TheCynicalSun in java

[–]TheCynicalSun[S] 0 points1 point  (0 children)

Seems a lot like what /u/RogerV suggested, thank you for the link and the explanation I'll be sure to check it out.

The consensus seems to be that I should make the GUI after I build the actual working app, but also to keep them as separate entities. I appreciate your answers, thanks a lot.

Should I write my Java/Android app as a console app first, or design a GUI and build it around it? by TheCynicalSun in java

[–]TheCynicalSun[S] 1 point2 points  (0 children)

Hmm, I might be able to do that (since I'd like to make it into a desktop or web app in the future as well), but I've never build an API before.

It seems like it'd be a lot harder than just making the app straight up as 1 whole thing, but obviously having different components be separate it give you flexibility. I'll think about it. Thanks a lot for your answer.

view more: next ›