English lad currently a C#/Java/VueJs/JavaScript/TypeScript engineer.
Extra dribbling can be found at https://codeheir.com
Portfolio found at https://lukegarrigan.com
Watching someone/working in Production Databases. There's so many easy ways to accidentally bring the system down in a fiery mess. Especially when watching someone that doesn't give off a strong sense that they know what they're doing.
Just as anxious-inducing for me is copying a production database to your local development box. If there's private customer data, ugh. (One consulting gig insisted I copy the production database over for local development or connect to it directly and it was a small business so the owners and employees and contractors can lose their livelihoods with one messed up SQL query or ORM command).
Senior Software Engineer started programming over 20 years ago.
C C++ python
flask QT django
AWS GCP Airflow
k8s terraform
JS CloudDB's
rust vue TS
API backend dev
#Intp #mathematics #nerd
Anything to do with Android. My first attempt at making an app was about a year or two after Android launched (2009?) I tried again later on and didn't get very far.
And in the last 2 years I've tried to work on an existing app and that went okay except it was 99% React Native/TypeScript (which I already have experience with so I'm not anxious about it, I'm only anxious when people write JavaScript/TypeScript as if it were Java!).
Now I'm trying to give it another go, this time by using Kotlin to cut down on boiler plate.
But it still makes me anxious knowing that the official docs and some books won't have the help I need, it'll be some obscure question on StackOverflow or a random blog that has the answers to my questions about Android.
Apple/iOS is even worse with their complicated Xcode and "iTunes Connect" tooling (which you have to use even when you're creating a mobile app with Cordova). Android tooling is much, much simpler. And with Google you pay USD 25, one time, while Apple makes you pay USD 100 per year (!) for the "privilege" to enrich their App Store with your apps.
I have a similar fear when using Firebase. The web interface is okay but logging/debugging is really poor. For example, we pay by the number of reads/writes we do to the database.
One day I was setting up a side project and I was getting like 1,000 reads every time I opened up my app. It was freaking hard to debug where those reads were coming from as they don't provide a way to see stats by documents in the database.
I'm always afraid I'm going to do something stupid and end up having a huge bill.
AWS pricing is notoriously complicated and opaque.
I did a price calculation recently, comparing what it would cost to host something on AWS versus Linode, and I was pretty shocked to find that data transfer out was approximately 9 times more expensive per Gigabyte compared to Linode (I'm not affiliated to Linode in any way, although I've been a happy user for a couple of years).
But this is nothing new, I believe that billing being notoriously complex and nontransparent (and expensive compared to competitors) is a known thing with AWS.
Oldest comments (87)
Vanilla JS. I had a dream about
[object Object]once.Was it the
[object Object]of your desire?Uncaught TypeError: desire is not a functionFor me "Eloquent JavaScript" and "YDKJS" were huge breakthrough on making up with JS.
JAVASCRIPT
RxJava π€·ββ
$ ssh production.vmDocker, every time I touch it I feel like I waste so much time. I get it working, but I feel like I could of done better.
Keep going, once you master it, you'll reap the rewards my friend!
Thing is that most of us just deal with docker when we absolutely have to. So you mostly have to relearn it every time '
Could you give me some examples of some of the things you have to do? Would be interesting to see it from another's perspective
Same, the docker developer CLI and I don't particularly jive. Luckily docker is pretty much 'set it and forget it' once you set up a Dockerfile.
I've just lost three days of work because of that thing. Looks like a fourth in the making.
Right, I try not to use it unless it's absolutely necessary.
GWT
JS
Watching someone/working in Production Databases. There's so many easy ways to accidentally bring the system down in a fiery mess. Especially when watching someone that doesn't give off a strong sense that they know what they're doing.
Just as anxious-inducing for me is copying a production database to your local development box. If there's private customer data, ugh. (One consulting gig insisted I copy the production database over for local development or connect to it directly and it was a small business so the owners and employees and contractors can lose their livelihoods with one messed up SQL query or ORM command).
Same with me. Well that is a scary situation playing with the production database.
Anything to do with Android. My first attempt at making an app was about a year or two after Android launched (2009?) I tried again later on and didn't get very far.
And in the last 2 years I've tried to work on an existing app and that went okay except it was 99% React Native/TypeScript (which I already have experience with so I'm not anxious about it, I'm only anxious when people write JavaScript/TypeScript as if it were Java!).
Now I'm trying to give it another go, this time by using Kotlin to cut down on boiler plate.
But it still makes me anxious knowing that the official docs and some books won't have the help I need, it'll be some obscure question on StackOverflow or a random blog that has the answers to my questions about Android.
In general, mobile development. It seems soooo cumbersome to setup, tools are like too heavy, too many downloads, so tedious to test(sometimes).
Apple/iOS is even worse with their complicated Xcode and "iTunes Connect" tooling (which you have to use even when you're creating a mobile app with Cordova). Android tooling is much, much simpler. And with Google you pay USD 25, one time, while Apple makes you pay USD 100 per year (!) for the "privilege" to enrich their App Store with your apps.
AWS. The web interface is really complicated and I always worry I'm going to some how rack up a huge bill by doing something wrong.
I have a similar fear when using Firebase. The web interface is okay but logging/debugging is really poor. For example, we pay by the number of reads/writes we do to the database.
One day I was setting up a side project and I was getting like 1,000 reads every time I opened up my app. It was freaking hard to debug where those reads were coming from as they don't provide a way to see stats by documents in the database.
I'm always afraid I'm going to do something stupid and end up having a huge bill.
The way firebase works is that all the debugging should be done on your app's side, unless the problem was with cloud functions.
AWS pricing is notoriously complicated and opaque.
I did a price calculation recently, comparing what it would cost to host something on AWS versus Linode, and I was pretty shocked to find that data transfer out was approximately 9 times more expensive per Gigabyte compared to Linode (I'm not affiliated to Linode in any way, although I've been a happy user for a couple of years).
But this is nothing new, I believe that billing being notoriously complex and nontransparent (and expensive compared to competitors) is a known thing with AWS.
That is the number one reason I decided to go with Google Cloud, as it's easier to use.