Programming thread

The problem with this is that, while electron is bloated as shit, it's probably the best way to make an attractive desktop app.

Until someone comes up with something lighter weight, but approximately as powerful as the css box model / html5 model, electron's still gonna have a bunch of users.
If you need to make a cross-paltform app, and you replace "fastest" with "best", then I agree. But in absolutely zero manner is an Electron app better or more attractive than an app written for a system's native graphical layer.
 
  • Agree
Reactions: AnOminous
If you need to make a cross-paltform app, and you replace "fastest" with "best", then I agree. But in absolutely zero manner is an Electron app better or more attractive than an app written for a system's native graphical layer.
Designers have been all over web stuff like flies on shit for the past 15 years. A much, much smaller number of people have been working on native UIs during that period of time.

Some exceptions are mobile UIs (and even then, like on iOS, people are moving away from doing actual Obj C or Swift to using react native). OS X has always kinda the snobby graphical designer OS, so they've kinda held onto style for a bit. But overall, in general, the native desktop scene is a shitshow compared to the stuff people are doing on the web.

A big part of it is that they don't have to fuck around with compilers or (much) code to get stuff done.
 
Am I missing something?
Yes. You see, that package makes it possible to write fewer lines of code in your project, and writing fewer lines of code is always better even if you have to add yet another package of a few hundred sloc in order to do so.

But seriously, yes, I agree, that code is not at all more legible to what it replaces, especially for someone who would be just starting out on a project which had been using it. For this reason I'm not really a huge fan of custom or overloaded operators in programming languages (I assume that's what's happening here). Just write a function/method with a self-documenting name rather than forcing me to guess what "foo <% bar" means.
 
So last week, BuzzFeed, HuffPo and Gannett dropped the axe on some of their editorial staff. In response to the propensity for lefty journos to propose that laid-off coal-miners should "learn to code," some people on Twitter have been ribbing those who lost their jobs by suggesting they do the same. And some of those journos are not taking it well. Here's two separate pages on Twitchy listing such tweets back and forth.

I believe there is a special, dedicated section of Hell just for people with anime twitter avatars who tell laid-off journalists to “learn to code”

— Punished "Venom" Patrick George (@bypatrickgeorge) January 24, 2019

As someone who turned down an offer yesterday for a gig paying $15 an hour, I'd prefer to not have hundreds of new competitors driving rates down, so I hope these people can find new gigs in journalism or burger-flipping or… coal mining instead. Still, it's fun to see these people triggered by their own advice.
 
As someone who turned down an offer yesterday for a gig paying $15 an hour, I'd prefer to not have hundreds of new competitors driving rates down, so I hope these people can find new gigs in journalism or burger-flipping or… coal mining instead. Still, it's fun to see these people triggered by their own advice.
I'm fairly certain that none of the laid off journalists who are being told to "learn to code" will actually do so; they see that kind of work as beneath them. Just like every time this happens, the journalists who got fired will get scooped up by another unscrupulous """news""" outlet that will itself eventually collapse, starting the whole cycle over again.
 
As someone who turned down an offer yesterday for a gig paying $15 an hour, I'd prefer to not have hundreds of new competitors driving rates down, so I hope these people can find new gigs in journalism or burger-flipping or… coal mining instead. Still, it's fun to see these people triggered by their own advice.
They'll probably hire them to get you coffee and stuff.
 
  • Optimistic
Reactions: Splendid
Lol, what office still has assistants for the rank and file?
 
I'm learning some computery things right now because it will be helpful for my field. I picked up a little bit of R a few months ago and this (frankly overpriced) class I'm taking will teach UNIX, SQL and Python.
 
Lol, what office still has assistants for the rank and file?
Finance related companies.
I'm learning some computery things right now because it will be helpful for my field. I picked up a little bit of R a few months ago and this (frankly overpriced) class I'm taking will teach UNIX, SQL and Python.
That's cool. If you have any questions, this is obviously the thread. Though yeah, you might be overpaying for something that 99% of programmers just google.
 
  • Agree
Reactions: Kiwi Lime Pie
That's cool. If you have any questions, this is obviously the thread. Though yeah, you might be overpaying for something that 99% of programmers just google.
It's part of a Master's program I am taking.

You're right, most of the stuff I am learning could be learned for free (or cheap, because I still like paper books). But I work in biology which is unfortunately very credentialist. Actually, I should have started a Phd a decade ago because these days no one thinks you're a real scientist without one even if you have a decade of experience.

And unfortunately my current job is not providing any kind of tuition assistance because the company is run by penny pinching chinks.
 
  • Informative
Reactions: Marvin
Wait, is that why all Chinese software sucks? Do they just have random amateur coders doing it?
 
I won't have a reason to use R for a while but I'm just re-learning some stuff so I don't forget.

One of the challenges I have between what DataCamp teaches me versus what my classes require is that they're looking for different things. When I was still taking Stats I'd only learn as much R as needed for things I couldn't do in Excel (also, the class despite advertising being an intro to R did all its instruction in SAS or SPSS... annoying). DataCamp on the other hand teaches much more basic stuff (at first) that I felt was pointless, but isn't really.

I realized how bad terrible my skill gap was by totally fucking up basic practice exercises despite PASSING the introductory class. The thing I was having most trouble with was selecting elements of a matrix and the factor() and levels() command. So I did a bit of offline practice

Code:
> Week <- c("Tuesday", "Sunday", "Friday", "Saturday", "Wednesday", "Thursday,
+ "Monday")
Error: unexpected symbol in:
"Week <- c("Tuesday", "Sunday", "Friday", "Saturday", "Wednesday", "Thursday,
"Monday"
> Week <- c("Tuesday", "Sunday", "Friday", "Saturday", "Wednesday", "Thursday"
+ , "Monday")
> factors(Week)
Error in factors(Week) : could not find function "factors"
> factor(Week)
[1] Tuesday   Sunday    Friday    Saturday  Wednesday Thursday  Monday  
Levels: Friday Monday Saturday Sunday Thursday Tuesday Wednesday
> levels(Week) <- c("Monday", "Tuesday", "Wednesday", "Thursday", "Friday",
+ "Saturday", "Sunday")
> factor(Week)
[1] Tuesday   Sunday    Friday    Saturday  Wednesday Thursday  Monday  
Levels: Friday Monday Saturday Sunday Thursday Tuesday Wednesday
> levels(Week)
[1] "Monday"    "Tuesday"   "Wednesday" "Thursday"  "Friday"    "Saturday"
[7] "Sunday"
 
  • Informative
Reactions: Marvin
better-coders.png


:story:
 
When I took statistics, I mainly used imported .csv files to stand in for data frames in R.

I did a little practice just now to manually create data frames and then add columns to said data frames.
Code:
> names <- c("Peter", "Paul", "Mary")
> sex <- c("Male", "Male", "Female")
> age <- c(80, 81, 72) #current age or age at death
> stuatus <- c("Living", "Living", "Deceased") #Had a brain fart and forgot to add "c" to make a vector. By the time I got it right, I misspelled status
> PeterPaulMary <- data.frame(names,
+ sex,
+ age,
+ stuatus)
> PeterPaulMary
  names    sex age  stuatus
1 Peter   Male  80   Living
2  Paul   Male  81   Living
3  Mary Female  72 Deceased
> PeterPaulMary$sex
[1] Male   Male   Female
Levels: Female Male
> PeterPaulMary$penis <- c(T, T, F)
> PeterPaulMary
  names    sex age  stuatus penis
1 Peter   Male  80   Living  TRUE
2  Paul   Male  81   Living  TRUE
3  Mary Female  72 Deceased FALSE

And yes, I did assume their genders because I'm not a PC cuck.

References:
https://en.wikipedia.org/wiki/Peter,_Paul_and_Mary
 
When I took statistics, I mainly used imported .csv files to stand in for data frames in R.

I did a little practice just now to manually create data frames and then add columns to said data frames.
Code:
> names <- c("Peter", "Paul", "Mary")
> sex <- c("Male", "Male", "Female")
> age <- c(80, 81, 72) #current age or age at death
> stuatus <- c("Living", "Living", "Deceased") #Had a brain fart and forgot to add "c" to make a vector. By the time I got it right, I misspelled status
> PeterPaulMary <- data.frame(names,
+ sex,
+ age,
+ stuatus)
> PeterPaulMary
  names    sex age  stuatus
1 Peter   Male  80   Living
2  Paul   Male  81   Living
3  Mary Female  72 Deceased
> PeterPaulMary$sex
[1] Male   Male   Female
Levels: Female Male
> PeterPaulMary$penis <- c(T, T, F)
> PeterPaulMary
  names    sex age  stuatus penis
1 Peter   Male  80   Living  TRUE
2  Paul   Male  81   Living  TRUE
3  Mary Female  72 Deceased FALSE

And yes, I did assume their genders because I'm not a PC cuck.

References:
https://en.wikipedia.org/wiki/Peter,_Paul_and_Mary
Julia has some really great libraries for working with .csv files, turning them into dataframes, and then doing calculations on them.
 
  • Like
Reactions: Strange Looking Dog
I'm thinking ahead a little about all this stuff I'm learning and what I want to do with it.

Currently I'm doing an MS in Biotechnology but the field is plagued with a Ph.D. oversupply AND a glass ceiling. For every post and permadoc that whines about never being able to get a tenure-track position, there are probably 10 BS and MS level employees that will never be considered for a entry level scientist position, no matter how many years of experience they have. The ones that do did so before the Ph.D. bubble reached critical mass and stayed at their particular company for a decade or more.

I wanted to get into Bioinformatics because of the shift in the industry towards personalized medicine, but alas the computer side of things is also stung with the "You have to have a Ph.D. and seven million years of experience in a completely niche field" miasma. Also, thinking about myself personally, I'm fast approaching the middle of my thirties and I can't help but think, "Why would anyone hire you when they could hire someone a decade younger with more experience or a Pajeet?"
 
Back