81–90 of 226 posts
This is an awesome article! I like the idea of being more forthcoming with what we don't know. > Containers. I have no idea about how to use Docker or Kubernetes. (Are those related?) I have a vague idea that they let me spin up a separate VM in a predictable way. Sounds cool but I haven’t tried it. > Deployment and devops. I can manage to send some files over FTP or kill some processes but that’s the limit of my dev…
Earlier quoted context omitted.
Meh. I wrote C# for 13 years of my career, starting with .NET 1.0. I worked at Microsoft, writing C# services, I worked for consultancies writing C# servers, clients, and web apps. I’ve been doing full time JS with some Ruby for the past 5 years. I doubt I could write anything more than “Hello world” in C# without a lot of Googling.
"I understand the concept of types and can read annotations but I’ve never written it. The few times I tried, I ran into difficulties." I know it's part of the "typescript" section. But it honestly sounds like it is quite general. I looked his github, and his only C# experience seems to be a tictactoe made in 2014.
Earlier quoted context omitted.
Meh. I wrote C# for 13 years of my career, starting with .NET 1.0. I worked at Microsoft, writing C# services, I worked for consultancies writing C# servers, clients, and web apps. I’ve been doing full time JS with some Ruby for the past 5 years. I doubt I could write anything more than “Hello world” in C# without a lot of Googling.
"I understand the concept of types and can read annotations but I’ve never written it. The few times I tried, I ran into difficulties." I know it's part of the "typescript" section. But it honestly sounds like it is quite general. I looked his github, and his only C# experience seems to be a tictactoe made in 2014.
I’ve worked on C# codebases professionally for about four years. They’re not open source because half of that time I worked on enterprise software (ASP .NET MVC, Entity Framework, NHibernate) and another half was a closed source product (Xamarin aka MonoTouch, Rx). Prior to that I worked a little on an open source static analysis tool (Gendarme) using Mono Cecil.
Prior to that I was moderating the .NET section on one of the largest Russian programming forums and translated documents like LINQ Overview when they came out. I also have a silver C# badge on StackOverflow. (https://stackoverflow.com/help/badges/39/c-sharp?userid=4581...)
I know how types work. My remark was that I haven’t worked with C# for about four years. I’m not aware of changes between versions 5 and 9, and might have forgotten some of the C# syntax for things like lambdas, having worked a lot with JS since then.
Earlier quoted context omitted.
Shared hosting includes automatic capacity scaling and on-demand pricing?
For most use cases, the required capacity ranges from zero to still small enough to fit on a single host. Any half-decent shared host ought to be able to scale you at least as far as a single database server on commodity hardware will suffice.
This is a very good article. What stumps me though is how the 10x engineers/architects make such sound technical choices without knowing a lot of things. I perennially feel ignorant of Computer Science concepts that many others seem to possess. This article helps me to understand it's not only me. But I would still like to make the best tech choices most of the times...But the problem is..WHAT TO LEARN NEXT? THERE'S…
What I miss from this article is what he does know. Not to boats, but to contrast. I know some of the things he does not know, and I'm sure he knows things I don't know. But without knowing what his expertise is, it's easy to think you know more than him.
This. Never heard of Dan before today. Now he is "a guy on the Internet who writes about programming but doesn't know much about it".
After reading this, I feel like I've imposter syndrome as well. I know about 80% of those topics pretty well, but I don't think I could ever get a job as a junior dev. Maybe I focus too much on learning things that interest me, and not enough on things that land you that software engineer title.
So the main thing you are missing is the actual coding?
What do you consider "actual coding"?