Details
-
AboutAndroid Developer. Questions why anyone would use dynamic languages on a large scale.
-
Skillsjava, kotlin, android-studio, typescript, python
-
LocationCologne
-
Github
Joined devRant on 11/2/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I thought echo was PHPs debugger 😂
-
I heard that the fasting time backfires and most people actually gain weight during that time. Is that true? ^^
-
I'm very super famous...
-
Or use async.js to flatten them out
-
You have a bright future my friend. There's a metric megaton of developers which hate their jobs because the have to fix bugs in absolutely unmaintainable codebases
-
"with the right computer algorithms I can hack you back in time" Hackerman
-
1. Switch to AppCode
2. Code your Interfaces
3. ?
4. Profit -
Have you tried AppCode?
-
@JTBringe no, actually moving on from C to other languages was pretty straight forward
-
Waaaaa... wo hast du den her?
-
MonoDevelop still exists?
-
@Linux "Suddenly broken things?" One word: Bootloader
-
@Linux it really depends on the hardware you're running on. If the parts build into it a common, it'll likely just work fine but dare you if you have some exotic parts in your laptop...
-
@vortexman100 it's all about balance of efforts - is it feasible to just scale the machine up? Then do that. Or if not, then start optimizing...
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%. A good programmer will not be lulled into complacency by such reasoning, he will be wise to look carefully at the critical code; but only after that code has been identified" — Donald Knuth -
When you're alone in the project... otherwise: learn how to rebase!
-
To quote Guido Van Rossum: "not execution speed is too slow, development is too slow!". While performance has its point, in 90% of the software projects I came across, it wasn't the cruital part
-
@zfor yeah I think the problem really lies more in the overly complex nature of an Android App build, I mean there're like up to 5 processing steps, tha hell man...
-
Gradle is a resource hungry monster - they'll really have to work on this
-
Math.pow(x, 2)
-
And here I am having to run Android Studio + Emulator on an old laptop with an i5 and 8 GB RAM...
-
No, simple mathematics...
-
😁
-
Don't worry, you will curse yourself later when you have to internationalize your app
-
Visual Studio - the Dart Vader of the IDEs
-
elementaryOS 👌
-
@RamirezTuJest it is because it inherently relies on the the Dom is structured - making it unmaintainable
-
At least you don't use "." as commit message. I have seen this...
-
I like to quote Guido Van Rossum: "Not execution time is too slow, development is too slow!" Start in whatever technology you can iterate the fastest. Then afterwards if performance REALLY becomes a problem, you can start to optimize - change technologies
-
That's a low blow 😂
-
Must be a Cologne Ehrenfeld based developer ;-)