The ETA just for setting up the development environment in $newJob is no less than 2 weeks, but it's no problem if it's two months. I know many of you are used to this kind of scale in dev work places, but I'm kind of terrified (that, plus the ~300 person IT workforce all in the same place, the git repo with more than 100 repos -and this is, apparently, just the tip of the iceberg-), the commits in 1000+ LOC files made in the past century... This will be fun, fortunately. And sadly. :P
@array When I started as a contractor for Boeing, it took 5 weeks before I was set up to do work. Two of the people who got hired along with me were laid off before they even got up and running.
@tulpa I just hope I won't be laid off in a few weeks, then... But if so happens, well, that's life. XD
The good part is that I'm not just setting up stuff, I've got liberty to come to other coworkers' places and see what they are up to, they explain what they do and I can even make suggestions. It's been just two days, but I'm really enjoying this, so if tomorrow they lay me off, I still get two days of enjoyment. :)
And it seems I'll be doing full stack, but #Java mostly. I know, I know, but indulge me: I just love Java, so I feel lucky. And more important, I've found a very cozy workplace, the team seems to get along fine, they meet every Friday after workday for beers and chat, and they have been very helpful and welcoming. This is what I signed for when I began Programming, and quite different from what have been my early experiences. I hope this ends up as well as it is promising now. :D
@fedops As I said, I know, I know... Just take into account that my experience so far includes not only Java, but PHP and JavaScript (full stack JS!), so it's either learning to love the underdog, or live a life of pure misery. XD
Now seriously, Java is way better than some people give it credit for. You can say whatever about it, but compared to "[new, hip and shiny]", it's really battle tested, had years to improve, and the community, docs, ecosystem etc are just huge, so that may count. ;)
@tulpa@fedops There's code in prod ranging from Java 6 to 17, and it all does the job. It happened to me that upgrading a Node project's dependencies just a few weeks old broke said project; just saying. ;)
@array@tulpa oh yeah, no comparison to JS and other languages from hell.
Java basically survived due to Moore's Law. When it came out in the 1990s it was so comically slow we referred to Java/Corba/XML as the Tranquilizer Trio. These days it can be really fast even on a phone.
@fedops@tulpa Indeed, I've read some performance comparisons and Java usually does quite well. Anyway, I believe it could happen to me what I've seen many times, people very often hate what they use at work, as there's no silver bullet and the more you use something, the more problems you can find, so I may change my mind. I'll just enjoy my Java honeymoon while it lasts. XD
@array@fedops@tulpa after 20 years of #java coding, having worked with others ( C, C++, PHP, js, Rust, python), well I think Java is most of the time the Silver Bullet for any serious, long lasting, industry grade projects, and recent versions get it closer :-)
@motofix@fedops@tulpa My company's Big Brains seem to agree with you! ;) Yeah, I'm almost crushed by the raw quantity and the complexity of the code base I'm just beginning to get a peek of, meanwhile Java has managed to work as expected for decades here, no sweat. :D
Add comment