Mr SuperAwesome posted:

actually its the difference between god, nature, and satan - evolution
(god's computers: the apple macintosh, ourselves, computers squared - complictated or evil computers - think android linux, or windows XP or 8)

fun fact lets put this in other numbers - 2^4 = 16 (carbon, u, the shitposter), 42 = H20 = water (sea, earth) 1+(9-2) = 7 = nitrogen (air, fire)

stick them all together and u get N20 - laughing gas - and N20(9) (H20)2 C (420) = the weed number

look at it backwards, and you get funny stuff (laughing (N20) at (2) things (C))

if the things are computers theyre 64 bits = 2^9 * 2 = 18/2 = 9

so the funny computer number is for reelz the 219

the pos is the union of 420 and 219, the true chill place to hang out with ur bros

for more on this exciting new videogame blend of progamming math and weed, keep an eye on ur local app store. itll be here in hovr form

Stringent posted:

the only way to contribute to an open source project is to use it and fix poo poo as you need it, unfortunately

MeruFM posted:

slow down there wutang

Notorious b.s.d. posted:

talking to users is like 99% of the useful part of your work. if you can't talk to an end user about what you are about to do to the product, you are a great target for outsourcing to alabama/india

coffeetable posted:

superawesome is a crank

Stringent posted:

the only way to contribute to an open source project is to use it and fix poo poo as you need it, unfortunately

Notorious b.s.d. posted:

this is the attitude i am trying to combat

sales people are good at sales. this usually implies that they are very friendly. it almost never implies strong "soft skills"

fixing bugs only matters in proportion to how much it affects users

working on an awesome n**2 to n*log(n) transition matters exactly not at all unless users are complaining or it enables users to do something new with the product

talking to users is like 99% of the useful part of your work. if you can't talk to an end user about what you are about to do to the product, you are a great target for outsourcing to alabama/india

Notorious b.s.d. posted:

fixing bugs only matters in proportion to how much it affects users

working on an awesome n**2 to n*log(n) transition matters exactly not at all unless users are complaining or it enables users to do something new with the product

talking to users is like 99% of the useful part of your work. if you can't talk to an end user about what you are about to do to the product, you are a great target for outsourcing to alabama/india

Kevin Mitnick P.E. posted:

currently i have 0 ability to talk to end users as my role is working on the core services that app backends rely on. that said, it's typically not hard to quantify the impact of a change on end users & I'm very dubious of doing work that doesn't have a quantifiable impact. the rest of what you said i'm going to call self-management and agree that devs who act as a consumer of tasks & producer of commits are not making a good case for why they boss should employ them over anyone else

Stringent posted:

the only way to contribute to an open source project is to use it and fix poo poo as you need it, unfortunately

Notorious b.s.d. posted:

yeah.

your users are the service consumers, so it's in your best interest to work closely with those consumers and be more useful/responsive than an off-shore team

write good docs

dont let a legion of BAs get in the way

go to fuckin meetings and really participate, let users actually see you playing the "active listening" game.

nrook posted:

while this is true, I think you're being mistaken in comparing unit tests to, like, pointless algorithm refactoring or whatever

the point of unit tests is to make it not scary to modify code you haven't seen before, and thus make it faster to write new code (even with the unit tests). ime I've found code with good unit tests is easier and faster to write (correct) code for, so I think the theory here is accurate.

double sulk posted:

i have a terrible programmer e/n. i've been feeling kinda lovely the last week or so for a number of reasons i'd like to do some oss stuff but it feels like any of the stuff i'd like to work on i'm too behind in terms of understanding. taking elixir for example, it's a neat language and there are a couple cool projects, but the few things there are really heavy on the http/server poo poo (new frameworks being built, see: phoenix) or stuff like database querying (see: ecto). i get by decently enough with the rails stuff i do now but it's ultimately totally different from building non-insignificant programs/libraries is still over my head, and by the time i could contribute anything of value it'll either have already been implemented or something. a lot of what i'm used to essentially abstracts what's going on in the background, which is great until you need to understand it.

basically i look at projects like those and still think "where the gently caress do you start" and it's the one thing that ever makes me regret not having a traditional cs education (to an extent). at the same time, as long as i'm working and getting paid i guess i could continue to take the who gives a gently caress approach with regards to doing oss poo poo, but i feel like it puts me behind. it's a pseudo-imposter syndrome that bothers the gently caress out of me and i'm not sure what to do. maybe i really just need to sit and read books or code bases for a few hours on end but i don't know if i have the mental patience, or maybe i just need to do something that isn't a loving web app.

in a way i really hate what i do now which is be part of a place that does consulting (even if the senior guys are doing more the initial estimate poo poo) because i end up working on a bunch of vastly different applications, and the differences between 3-4 year old libraries is mixing my brain up and i can never 100% commit anything to memory. we have a bunch of rails 2 apps that still have to be moved to rails 3, and i only really know so many of the rails 2-isms, or we have old loving versions of capybara that i can't remember what the differences are from the newer ones and it slows me down so often. basically it's a massive level of inconsistency because i don't get to pick what we work on nor the stack in some cases and i think it's hindering my growth, but at the same time it wears down my personal drive to do anything else.

that was longer than i wanted it to be but i feel pretty lovely and don't particularly have anyone to talk to about it. i'm supposed to have an onsite interview this week for a scala/ruby job and the context of what i'd be doing sounds really cool in theory, but i honestly have no idea what's going to happen or if i'd end up really wanting the job if i was fortunate enough to be offered it.

Morkai posted:

it's not imposter syndrome when you really are an imposter.

you should pick a project that has a language or feature you're interested in for whatever reason. start working on it in earnest, and then pray to god that someone else DOES implement the feature you wanted so you can see someone else's take on the same problem. use it as a learning experience and don't be a whiny babby because you can't contribute in a meaningful way to something built by people years ahead of you.

get used to inconsistency. you will see it everywhere, especially in a mature code base that's only under maintenance. get used to not being able to memorize things. learn language features not frameworks. learn how to FIND the answer not know all the answers.

grow up.

Cybernetic Vermin posted:

ada seems p. sweet really, but the fact that you are writing ada 83 probably immediately implies that you are working on some gigantic legacy system in a situation where you have very limited ability to make any larger changes without a long bureaucratic process

otoh programming in itself is p. boring all around anyway, spend the money they pay you on fine whisky and try to forget

power botton posted:

stop using ORMs

power botton posted:

stop using ORMs

power botton posted:

stop using ORMs

Awia posted:

the code is thankfully well maintained, documented, formatted and commented, even the stuff from the 90s
we were talking about upgrading to ada 95 but thatll probably take years

i work support so i just fix the bugs that dev somehow sneaks in
i drink to forget the millions of unit tests

Morkai posted:

they also pretty sweet when your architect can't make up her drat mind about poo poo and reworking something takes an hour rather than a day.

Stringent posted:

nice mensrights post, rear end in a top hat

Kevin Mitnick P.E. posted:

Luigi Thirty posted:

dear yospos how do i programming job when i live in florida and make $9 an hour and can't afford to move to the west coast where all the jobs are? tia

Werthog 95 posted:

hey what's the easiest way to make a dumb little gui for a python script