|
RE: plugins i stopped using eclipse when i learned how it works with maven sane people would run maven in another process, maybe with some messaging hooks so you don't have to parse std-out like an animal well, that's not how m2e (maven plugin for eclipse) does it. m2e takes all the maven configuration data and slurps everything up into the JVM running eclipse, including whatever maven plugins you have specified. this is why every maven plugin has to have a eclipse specific configuration or eclipse gets all whiny; m2e was causing too many OOMs and resource leaks because plugin devs didn't cleanup or anticipate their code running more than one per call to maven.
|
#
?
Jan 29, 2015 05:10
|
|
|
|
| # ? May 23, 2024 08:20 |
|
|
slurping maven into your app was part of maven's intentional design. Specify project info once, have it parse able by the same code base in any context Idk whether to blame your problems on eclipse or plugin authors
|
|
#
?
Jan 29, 2015 05:15
|
|
|
well, the problem with that is the implicit context of the plugins. most of them are going to get tested with little interaction with other plugins and in a context where the host JVM is destroyed at most minutes after usage and the same code is never executed twice regardless of the maven design, the ecosystem of the plugins makes it seriously questionable to inject them into some running process that isn't disposable
|
|
#
?
Jan 29, 2015 05:39
|
|
|
Brain Candy posted:well, the problem with that is the implicit context of the plugins. most of them are going to get tested with little interaction with other plugins and in a context where the host JVM is destroyed at most minutes after usage and the same code is never executed twice yeah i'm not sure whether this is a mistake by eclipse, or by plugin authors if you are loading maven in your same jvm just for the sake of its side effects, that seems like a mistake by eclipse. loading up maven data should be done for project data if you are loading maven in your jvm for project info, and this somehow requires you to load plugins that exist to manage side effects, that seems like a mistake by plugin authors
|
|
#
?
Jan 29, 2015 06:16
|
|
|
so apparently they went from "we'd love to hire you RIGHT NOW" to total hiring freeze in 3 weeks and didn't bother telling me for a month. and the other company I was supposed to have an interview with just laid off 4,000 people. welp. at least the guy says he has a lead on a position as a PHP developer (lol)
|
|
#
?
Jan 29, 2015 23:12
|
|
|
Luigi Thirty posted:so apparently they went from "we'd love to hire you RIGHT NOW" to total hiring freeze in 3 weeks this is one of the dangers of looking for a job near the end of the year.
|
|
#
?
Jan 29, 2015 23:13
|
|
|
Luigi Thirty posted:at least the guy says he has a lead on a position as a PHP developer (lol) as much as we make fun of it php dev is better than retail barely, because it at least gives you software dev experience
|
|
#
?
Jan 29, 2015 23:27
|
|
|
Dear terrible programmers, across the land: Proofread your goddamn resumes. Love, CPColin
|
|
#
?
Jan 29, 2015 23:44
|
|
|
Arcsech posted:as much as we make fun of it php dev is better than retail in the way that working at a garage that only fixes 1974 Triumph motorcycles technically gives you mechanic experience yet is still preferable to starving
|
|
#
?
Jan 29, 2015 23:44
|
|
|
Luigi Thirty posted:in the way that working at a garage that only fixes 1974 Triumph motorcycles technically gives you mechanic experience yet is still preferable to starving php experience is actually pretty handy to have, because there's always gonna be some ancient POS laying around that needs to be updated and it's always in PHP, so it's not as bad as yospos makes it sound.
|
|
#
?
Jan 29, 2015 23:55
|
|
|
a friendly reminder of why this thread exists sarehu posted:You have to be emotionally retarded to interpret that retroactive abortion comment as vitriolic.* When I read comments like that I think, yes, I have felt that way and written like that, and I know how he feels, and it doesn't turn me off at all. So I think if other people are turned off then they are wrong to be so and their reasons or mere feelings are invalid. Also you are overlooking all the benefits of the tone he has. You'll see that sort of thing at other check-your-ego-at-the-door type environments.
|
|
#
?
Jan 30, 2015 00:00
|
|
|
php is pretty good for learning compared to things like ruby on rails where things like http headers and sql injections are dark mysteries of an ancient and bygone era. like i used curl to make an api auth request the other day. and then there was a cookie just sitting there and i was like 'oh wait, that's how sessions work??' what i'm saying is, php is close to the metal
|
|
#
?
Jan 30, 2015 00:06
|
|
|
otoh cgi's are less stateful than big lumbering web servers and if you're not learning how to deal with layers upon layers upon layers of state then you're not learning anything useful
|
|
#
?
Jan 30, 2015 00:11
|
|
|
mostly I'm afraid of PHP on a resume being like the university of phoenix on a resume and actively harming your chances of doing non-PHP things because you don't know anything that happened after 2000
|
|
#
?
Jan 30, 2015 00:16
|
|
|
Luigi Thirty posted:mostly I'm afraid of PHP on a resume being like the university of phoenix on a resume and actively harming your chances of doing non-PHP things because you don't know anything that happened after 2000 any software experience is better than no software experience if your only option is php, then do the php and write some junk in your spare time in something you like, chuck it up on github, and link to that on your resume when you go to look for a not-php job
|
|
#
?
Jan 30, 2015 00:23
|
|
|
Arcsech posted:any software experience is better than no software experience counter point: i know fortran and wrote a gaussian integrator or something in it for a coursework. that fact is not going anywhere near my cv whatsoever
|
|
#
?
Jan 30, 2015 00:28
|
|
|
rotor posted:php experience is actually pretty handy to have, because there's always gonna be some ancient POS laying around that needs to be updated and it's always in PHP, so it's not as bad as yospos makes it sound. no one doubts that there is always demand just working in php chafes the brain
|
|
#
?
Jan 30, 2015 00:30
|
|
|
rotor posted:php experience is actually pretty handy to have, because there's always gonna be some ancient POS laying around that needs to be updated and it's always in PHP, so it's not as bad as yospos makes it sound. we don't have any php stuff
|
|
#
?
Jan 30, 2015 00:32
|
|
|
Notorious b.s.d. posted:just working in php chafes the brain rotor posted:it's not as bad as yospos makes it sound.
|
|
#
?
Jan 30, 2015 00:32
|
|
|
Shaggar posted:we don't have any php stuff hey thats great *pats u on the head*
|
|
#
?
Jan 30, 2015 00:32
|
|
|
we have classic asp and jsp which are almost as bad.
|
|
#
?
Jan 30, 2015 00:34
|
|
|
as someone who writes php, these are both true
|
|
#
?
Jan 30, 2015 00:49
|
|
|
specifically it was "PHP developers with .net experience" he said the company was looking for which makes me very afraid for what they're actually doing
|
|
#
?
Jan 30, 2015 01:02
|
|
|
Luigi Thirty posted:so apparently they went from "we'd love to hire you RIGHT NOW" to total hiring freeze in 3 weeks and didn't bother telling me for a month. and the other company I was supposed to have an interview with just laid off 4,000 people. welp. i had this thing happen to me before. woulda been a 50% salary increase, but at least i already had a job
|
|
#
?
Jan 30, 2015 01:07
|
|
|
the important thing is not to work with the best technology all the time, but to know why it's bad, pick your battles, and deal sensibly with the cards you're given typecasting php programmers is a thing that happens, but if you can get to an interview people will appreciate your story on how you dealt with broken legacy system X i'd rather hear "so we decided to stick with php but move everything to a supported version asap and try to develop new features as services when it makes sense" than "so we decided to rewrite everything in node.js/go/haskell"
|
|
#
?
Jan 30, 2015 01:29
|
|
|
Luigi Thirty posted:specifically it was "PHP developers with .net experience" he said the company was looking for which makes me very afraid for what they're actually doing you should ask them
|
|
#
?
Jan 30, 2015 01:30
|
|
|
suffix posted:you should ask them I did which I assumed was implied
|
|
#
?
Jan 30, 2015 01:38
|
|
|
suffix posted:typecasting php programmers is a thing that happens heh, i'm pretty sure that's one problem php programmers don't have
|
|
#
?
Jan 30, 2015 01:44
|
|
|
the best eclipse plugin I've ever used is IvyDE. does pretty much exactly what it says on the box. m2e is somehow even more obtuse and lovely than maven itself.
|
|
#
?
Jan 30, 2015 01:46
|
|
|
MALE SHOEGAZE posted:heh, i'm pretty sure that's one problem php programmers don't have heh
|
|
#
?
Jan 30, 2015 02:01
|
|
|
MALE SHOEGAZE posted:heh, i'm pretty sure that's one problem php programmers don't have 
|
|
#
?
Jan 30, 2015 02:19
|
|
|
MALE SHOEGAZE posted:heh, i'm pretty sure that's one problem php programmers don't have
|
|
#
?
Jan 30, 2015 02:22
|
|
|
rrrrrrrrrrrt posted:the best eclipse plugin I've ever used is IvyDE. does pretty much exactly what it says on the box. lol
|
|
#
?
Jan 30, 2015 02:22
|
|
|
I've turned into the build engineer at work.
|
|
#
?
Jan 30, 2015 03:17
|
|
|
Space Whale posted:I've turned into the build engineer at work. 
|
|
#
?
Jan 30, 2015 03:31
|
|
|
On the one hand I've actually learned git pretty well. I made my architect with WAY more experience just drop his jaw fixing poo poo merges. OTOH I need to learn how to be an rear end in a top hat and make people follow the swim lanes. Also, TeamCity.
|
|
#
?
Jan 30, 2015 03:35
|
|
|
Space Whale posted:I've turned into the build engineer at work. talk about owned
|
|
#
?
Jan 30, 2015 03:36
|
|
|
Space Whale posted:On the one hand I've actually learned git pretty well. I made my architect with WAY more experience just drop his jaw fixing poo poo merges. so I was a build engineer for a while and here is my advice: 1) Have no tolerance for broken builds. if someone breaks a build, let everyone know who did it. Ideally, you should set things up so a broken build is impossible. 2) Have no tolerance for "just one more thing" commits when the build train is about to leave. Especially have no tolerance for people above the food chain fighting you to cram in one last feature. You know its wrong, and deep in their hearts they know it's wrong too. 3) Write your build logic in some scripting language. python seems like a decent choice. 4) Nightly builds are Just Fine. Full builds per commit are nice if you can do it, but don't kill yourself over it. 5) Absolutely do not be afraid to call people out on lovely behaviour like missing/sassy commit messages, constant flip-flopping trying to solve bugs by trial and error, committing straight to trunk instead of branch & merge, that sort of thing. 6) When a release goes extra smooth, spread some love around in the form of expensive scotch.
|
|
#
?
Jan 30, 2015 03:44
|
|
|
Space Whale posted:On the one hand I've actually learned git pretty well. I made my architect with WAY more experience just drop his jaw fixing poo poo merges. congratulations on your new role as the build janitor and the merge janitor  Space Whale posted:OTOH I need to learn how to be an rear end in a top hat and make people follow the swim lanes. 
|
|
#
?
Jan 30, 2015 03:48
|
|
|
|
| # ? May 23, 2024 08:20 |
|
|
that loving pixel
|
|
#
?
Jan 30, 2015 03:49
|
|