371–380 of 383 posts
Earlier quoted context omitted.
Why would anyone want to live in SF with that kind of prices is beyond me.
The prices are because so many people want to live in SF.
Earlier quoted context omitted.
The prices are because so many people want to live in SF.
But why would they want to live there? It's one of the most depressing place I've been to, it's like those dystopian movies...
Because they value different things than you do; whether that's the food, the theaters, the museums, the climate, or the social culture, or something else. Different ones of those for different people.
> It's one of the most depressing place I've been to, it's like those dystopian movies...
Other than in the generic ways that most urban environments are "like those dystopian movies" to someone whose lived most of their life in a suburban environment, I don't really see it.
I don't know why she has never mentioned someone she worked with at all. I commented about this about her 70 days ago. --- So let's see her repository ( https://github.com/jendewalt/jennifer_dewalt ). This girl not only became a competent front end developer in 100 days, but looking at the Gemfile, she knows how to use capistrano, redis, capistrano, paperclip, omniauth and devise? She knows the best practices for Rai…
We don't call male coders "boy", let's not call female ones "girl" unless they're a fourteen year old or something.
Earlier quoted context omitted.
We don't call male coders "boy", let's not call female ones "girl" unless they're a fourteen year old or something.
"girl" is used in place of "guy" because "guy" has a masculine connotation. I'd be happy to see "gal" but it's a little anachronistic.
Earlier quoted context omitted.
No it isn't.
There are a lot of things to do that have value that aren't web. There are a lot of things to do that you can be paid for that aren't web. There is some overlap. If it's hard to justify working on any of these things, the parent is going to have to explain why.
I suppose programming Microcontrollers for appliances, but I have never seen job postings for that (although they must exist). Might be because I didn't look at C jobs, though.
What I meant is also that most apps these days can be coded as web apps, and it is difficult to justify not doing so.
Earlier quoted context omitted.
There are a lot of things to do that have value that aren't web. There are a lot of things to do that you can be paid for that aren't web. There is some overlap. If it's hard to justify working on any of these things, the parent is going to have to explain why.
Mention some of those things, then. I suppose programming Microcontrollers for appliances, but I have never seen job postings for that (although they must exist). Might be because I didn't look at C jobs, though. What I meant is also that most apps these days can be coded as web apps, and it is difficult to justify not doing so.
Web browser tech itself quite obviously can't all be built as a web app.
A lot of things could be built as a web app but it's plain silly to - I don't want to lose access to my text editor when I lose networking (I could run a server on my local machine, but that's several layers of abstraction that clearly aren't necessary and I'm not confident they're helpful).
To be sure, there are lots of things where a web app is quite appropriate - but a view that that's all there is seems myopic.
Earlier quoted context omitted.
I don't get your point. Sure, some people have issues with those things. Let me give you an example. I used to help out a lot of people while at school, and most of them couldn't wrap their head around what a variable was. I was the one helping them since the first class, and I wasn't one class in front of them either. I simply understood it quickly. I could "grok" faster than them, for some unknown reason. I am by n…
I was by no means arguing one couldn't learn all of these things on one's own. I, too, am a self-taught programmer, and in fact, it makes it even harder for me to make an assessment of the claim without comparing to myself. All of the information is on the web, you're right. But just from a practical standpoint, it takes time to even learn about what you need to search for. One great piece of wisdom is that as you be…
'When I set out on this project, I knew I wanted to learn to code dynamic interactive websites, but I also knew next to nothing about coding. Rather than try to tackle the enormous task of building a complex, fully functional social network, I took a small first step. I pieced together a few bits of html and CSS to make the website for day 1, the homepage for the project.'
So if you look at the first sentence--she clearly knew something--some terminology, some idea of the technology and what it could do. IMO, most programming (heck, most tech stuff) is just _knowing_ that something's possible. After that, you just need to look up how to do it. There are kids out there who pick up this stuff easy as breathing. I think she did the same thing, just on a slower trajectory.
Earlier quoted context omitted.
Thanks for the background. I understand that there is more to "coding"/"coder" than I implied, it's just seems that the words have become so appropriated that I now instantly associate them with the whole "brogrammer" thing.
Well, I'm gonna try to hang on to it; it's what my parents used when I was growing up.