moonarchia
The Scientific Shitlord
- 29,098
- 56,399
IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
Noodleface
A Mod Real Quick
- 39,375
- 17,818
My old boss would throw away resumes if java was the first language a candidate listed
- 1
- 17,614
- 8,642
Part of my job requires working with the entirety of the Android repo. Google has been moving more of their code to Kotlin, which if understand correctly is Java with aids.
Our product will invoke multiple jvms to build Android and then invoke many more jvms to run our own Java-based analysis of their Java code. It's gayer than it sounds.
Our product will invoke multiple jvms to build Android and then invoke many more jvms to run our own Java-based analysis of their Java code. It's gayer than it sounds.
Noodleface
A Mod Real Quick
- 39,375
- 17,818
- 3,052
- 4,966
- 3,052
- 4,966
The whole Android ecosystem is "we're running Linux", but not really, only the Kernel with loads of Java on top. The even got into a fistfight with Oracle for that reason.
At least Apple had the foresight to make the underlying language for their iPhone ecosystem Objective-C and "Objective-C, but a bit more modern" (aka Swift).
TJT
Mr. Poopybutthole
- 46,371
- 126,589
I have my one coworker on PIP right now. We recently integrated a data governance solution and despite its issues God damn if it isn't absolutely amazing at finding tech debt and janky bullshit made over the years. 90% of jank bullshit was made by this one guy lol. At least stuff that isn't fossilized and is actually being used.
Luckily its all recorded well. It shows a constant pattern. Time after time misunderstanding basic design principles or not even knowing what they are. Every time find the shortcut to the desired output and implement it.
This is largely ancient databases where source control isn't much of a thing. Just things that exist around the edges of our primary stack, which is all source controlled. Like as an example, this source doesn't have the data type I want, make a table that does and load it with some trigger bullshit then use that rather than identifying the right layer to transform it and do that. Or the one I got him cold on the other week.
Can't figure out how to solve a basic data type problem so he hardcodes 100+ things. I tell him how to do it in a programmatic way and get him half way there. Gets frustrated and goes back to hardcoding it.
Sigh.
Luckily its all recorded well. It shows a constant pattern. Time after time misunderstanding basic design principles or not even knowing what they are. Every time find the shortcut to the desired output and implement it.
This is largely ancient databases where source control isn't much of a thing. Just things that exist around the edges of our primary stack, which is all source controlled. Like as an example, this source doesn't have the data type I want, make a table that does and load it with some trigger bullshit then use that rather than identifying the right layer to transform it and do that. Or the one I got him cold on the other week.
Can't figure out how to solve a basic data type problem so he hardcodes 100+ things. I tell him how to do it in a programmatic way and get him half way there. Gets frustrated and goes back to hardcoding it.
Sigh.
- 1
