117 karma · joined February 7, 2019
While we're paying high taxes here in Denmark (about 38-50% income tax depending on your bracket), we don't spend a lot of money on things like health insurance like you do in US.
If I know I have to be there anyways, I might as well goof off a little.
If no-one cared about the hours but I just had hard deliverables every day/week/month, I'd work much faster so I can go home earlier.
Depends on the project, too. Some I'm more interested in than others.
There's a bunch of grammatical errors on the site (space after exclamation mark, missing words), which prevents me from trusting it.
The design is also very... strange. It looks like a mess. (Sorry!)
There's that first logo "BA net" which looks pretty bad, like someone took someone elses app icon and used Paint to draw a rectangle and some text above it.
Everything around the header is positioned weirdly. My eyes don't know where to focus. There's no visual hierarchy. (Also, what's with that weird "party" icon at the right? At least make it the same size as the BA net logo, and align it to the top right.)
Above the header there's a sort of feature list, I thought it was a menu at first. Why use a period to separate items? Maybe move it down to the features list along with some context ("Here's what you can use it for...")
The big button looks ok, but it's encased in a grey border. Why is there a border around it?
Same with the feature list. The border just makes it look ugly. There's no padding to the left of the "Features" header, and the first item randomly doesn't have a border. Why?
Is anyone actually using those audio and text chat iframes? First of all, they're way to small to serve a practical purpose, and they also have a border again.
The operating system icons don't look nice against the grey background. Are they even needed?
Finally there's some mess in the bottom menu link items. Just a bunch of random stuff, I guess? Maybe just remove it, and use some proper CSS instead of periods and no-breaking space characters.
You're using a lot of boxes that don't align, sometimes there's a border, there's all sorts of different font sizes. It's kind of sloppy, which reflects poorly on the underlying product.
– Be up front about pricing and terms (depends on target business size though)
– Easy to understand but detailed feature lists, tier comparisons, screenshots, videos
– Public, well organized documentation that goes in depth and is easy to search/navigate, also acts as good SEO
– Plenty of samples in documentation so you can paste and go
– Quick support that can get technical enough
– Offer yearly and monthly subscriptions
Developers usually spend a few minutes scanning each solution they're comparing, so within very short time and clicks, they should be able to decide why you should be a pick and not the next one. There's usually a hard criteria. They need to solve a problem. Investigate what kinds of features your users picked you for.
Also, trials: If you don't offer trials, you'll get higher quality customers. (But still offer refunds just in case.) They'll be the type who can spend the first monthly fee to check out your site, and have realistic expectations.
LastPass UI is a nightmare last I tried it a couple years ago.
Even simple things are faltering, like when logging in, macOS stops registering keypresses in the middle of entering my password. Switching screens around when docking my MacBook Pro. Important features like Time Machine silently corrupting your files.
It's such a shame that macOS just keeps getting more buggy. I've read from multiple (ex) employees that there's no real incentive to fix bugs, since employees seem only to be rewarded when they're working on prestige projects.
What good is investing so much R&D into new hardware like Mac Pro when the operating system is the limiting factor?
> optimizing for a single server is a waste of resources
No, I think you should spend your time wisely and actually building your product. I don't think you should spend a huge amount of time to "optimize for a single server" (whatever that means), just that a single server can be enough for a large amount of traffic.
Many startups go all-in on complex architecture, microservices and Kubernetes from the get-go (or start splitting their monolith or whatever before it's necessary) and lose a huge amount of time setting all this up (when only Netflix-sized companies really need it) at a time where they should've focused on building their product.
The point here is that you can easily scale most apps in small steps without having to indebt yourself with complex architecture from the get go, which requires having to spend huge sums of cash on sysadmins and AWS bills that don't benefit your users.
It'll certainly take less time to manage than Kubernetes, that's fore sure.
Computer geeks that hated this didn't realize how good it was because they were familiar with the previous generations and don't like change.
The Word/Office 2007 UX design is probably some of Microsoft's best design work ever.
Noone is perfect. Greta eschewed the plane for a yacht, and guess what, people like you are still complaining. This is why people are blocking it out and are angry at her. How the can anyone win with this logic?
We can't just shame ourselves into fixing the climate. Broad regulation is the only way this will get solved. It can't be up to each individual person to save the climate.
If that's your solution, we're even more fucked than we currently are. Even if everybody stopped flying or eating ribeyes or whatever, there's still a huge amount of carbon that needs to be sucked out of the atmosphere, and plenty of extremely large sources of carbon and methane that are still there. The world is going to shit and you want me to eschew the tiny bit of enjoyment I have left in the hopes that everybody else does the same thing? Not gonna happen.
But that's not how anyone is doing Keto. It's not that easy to eat the massive amounts of fat this would require, which is why most people on Keto lose weight easily.
Also, why do we need mice to tell us this? Consuming large amounts of calories in general can trigger diabetes, right? In addition, Keto is extremely popular, so why not test on humans?
Programmers should not have the responsibility to decide these things on their own; it should come from the companys risk assessments and help with the goal of the company, not the goal of the programmers (which is to put neat things on their CV.)
This is spoken as a programmer, by the way.
But where does the .com part come in to the picture?
Does corp.net or corp.ninja have the same type of issue?