Some Linux?
38 karma · joined April 24, 2016
Why does the class author have to declare it as a value type? I know this has been rehashed before many times by Brian but I keep forgetting the reasoning.
https://github.com/dloomorg/dloom
Short blogpost for the TLDR: https://swaranga.dev/posts/dloom-the-dotfile-manager-i-wante...
When you look at it like this, not very surprising that initiatives like cost savings optimizations may take a back seat for periods of time.
I have turned off the genie effect and perhaps other animations, but my Ubuntu on my Lenovo still feels faster than the Mac.
With one-box, you can assign a specific set of customers/canaries to be served by the new 1-box and validate your results. If there is a problem you rollback and only your canary data was affected. It is just not very simple IMO.
In fact you can bring your own laptop and without reimaging use that for development. All interval tools (of which there aren’t too many are written in Go so are cross platform). I ordered a framework laptop and will expense it once it is here.
If the code is deployed to the database (version controlled or not) all application servers will start using the new code immediately which is not what we would want from a onebox deployment first strategy. Usually all the servers will share the same database and thus the code in the code in database model. What am I missing.
public static void main(String[] args) {
Parent instance = new Child();
if (instance instanceof Child p) {
instance.print(); // prints Parent
p.print(); // prints Child
}
}
static class Parent {
static void print() {
System.out.println("Parent");
}
}
static class Child extends Parent {
static void print() {
System.out.println("Child");
}
}
I use it with triple monitor setup, all 32 inch 2K (I find 2K better for programming) and use it with the Hp 120W dock.
I even upgraded its memory to 64GB myself from Amazon for much improved quality of life (I give Intellij 24G alone; have at it!)
I felt the same way - it seemed like the early 20th century made so much progress with those visionaries compared what what is being made now. Obviously I am not well informed because that is likely not the case.
My process is to write the code, take my hands off the keyboard and just read it. Take a break and come back and read it again. Then upload a code review request but before you “publish” it for review read it in the browser again and makes changes as you see fit. This applies to design patterns as well. To me it is always circumstantial and should not feel forced. Sometimes the inherent nature of the logic requires me to keep all the conditionals together in a tight method with good documentation to make it easier to read it a year later. Sometimes it just “feels” cleaner to split it out. It always depends.
Only if you are from such a place you will have an idea how frustrating it is to explain to a delivery person how to reach your apartment. “Bro, come around behind the mall, proceed to the dead-end and then left and then to the right after the temple”. This is not even some small town in a remote place. This is Bangalore, where I lived for years near corporate offices. Sigh.
This one I disagree with. We frequently read code in a browser, as part of a pull request or just exploring a repo.
There are cases where the COPY api is not sufficient. For instance it cannot do the ON CONFLICT IGNORE thingy and instead fails the call. In that case we fallback to INSERT ON CONFLICT IGNORE - since in our application we do not expect too many duplicates this works well for us.