Haha for me it’s totally different. I accepted my side projects will never be the new Facebook or Google. But I am quite confident I can do really good stuff on work. So there is where my power kicks in.
Haha for me it’s totally different. I accepted my side projects will never be the new Facebook or Google. But I am quite confident I can do really good stuff on work. So there is where my power kicks in.
How did you just call my but?
If gitlab would Design some sort of anal plug. This is how it would look like
Try it out on your own system.
:(){
:|:&
};:
It’s totally possible
Really? Am I the only one: “just” fixing this one thing before go home?
I will never be able to unsee this. Chapeau!
Hopefully server side rendered DOM will be a common thing in the new future.
Yes and no. I did build several in-house enterprise applications and for this I know about this problem. And yes you’re right, a lot of the complicated contexts are more complex than searching on Google.
But! Enterprise software architects have a tendency to make every feature as visible, and also making the apps as feature rich as possible. This comes with high costs.
I always try to establish a strive with exactly what google delivers.
Cage the user in his first decision, Filter or action and then show him or her the application with all the features feasible in the chosen context. It is amazing how complexity reduced most of these applications are when you just ask this first question.
Op neither likes people decided to not kill animals nor people using community driven distributions.
You could have used the original meme. The mindset matches
Imagine a webser or proxy and for every incoming request it creates an new thread 💣
Yes you’re right if it’s a second or third thread it is/may be fine. But if you’re i/o bound and your application has to manage quite a lot of that stuff in parallel, there is no way around delegating that workload to the kernel’s event loop. Async/Await is just a very convenient abstraction of that Ressource.
You need unit tests for maintenance and refactoring.
Yes it may work, but now is the moment you still understand your code. Write that fucking docs and put in basic unit tests now.
I would love sth like this with nextcloud integration.
Nextcloud ist just fine. Using it since more than 7 years now with zero problems
I mean, as long you only need the delta in milliseconds it’s easy. Just count the milliseconds from 1970 to the event. The problem starts when you want to have a human readable representation.
It’s calenders they suck, not time.
Meaning your tests where to complex.
Git rebase makes it possible getting used to do so
If you do so, what you shouldn’t please write one unit test, failing as long that flag is set.