navd

Not necessarily a food, but nicotine can create insane dreams. People who are in the process of quitting cigarettes can have really disturbing dreams if they fall asleep with the patch.

The line seems blurred. I've found the end result is much more desirable designing and iterating on existing code as you implement.

Not to me. I think the distinction between these titles are silly. Part of programming is architecting applications. There really isn't a way out of it unless you've just been maintaining and patching up existing code your entire life.

I agree that may be part of it.

I think coding interviews are fine as long as they aren't insane like what you see a lot these days. We just need a good metric on how to know if the person I'm interviewing can solve general problems, my problems, and has the appetite to grow more.

That's really hard.

I think like anything else, there are tiers to this profession. It's fair for someone in this position to call themselves a programmer but I think the OP is doing themselves an injustice by not taking the time to actually learn how to write code. Writings like this are fine, but a point should be made that progressing ones skillset is just as important as getting into the profession.

Otherwise, we support the notion that you don't need to learn how to solve problems to be a "Programmer". Which at its essence, is what a "Programmer" is.

We do the same right now, it kinda works but we might have info for tools we've built spread across repos.

I think this is where custom error types become useful. They can provide you more context about what went wrong so that you can handle that issue properly

Assuming you know other programming languages it might be best to build something. I usually pick a small project I can get done in an afternoon or two that I could easily do in my language of choice and build that.

Is there way to develop and test this locally? It seems like you constantly need to deploy to now to test new changes?

Probably not what you want to hear but, the next step is that you continue iterating to test to see if you can get traction.

If you can’t convince people to use the product it might mean that it is not something people want. Try treating your product like a science experiment. Your idea and execution is a hypothesis for what you think people want.

If you’re an engineer then the above doesn’t cost any money and hence doesn’t require investors. If not you have to get good at convincing people to work with you.

It looks interesting! There are two issues for me.

1) There is a bit too much copy and it took a while for me to see what you’re actually selling. I think you’re selling too much without letting the content do the talking.

2) I couldn’t find any example videos that show how you teach. This is important. I want to know if I’ll enjoy your course.

Otherwise, thanks for investing the time in this. Good luck!

Dude congrats! Super hyped for you.

There's no harm in being honest, and I believe previous offenders have already gone through YC

I'm fine with an external device if it is my phone...

I think you're looking at this the wrong way. There's a place for programming languages like Go. A tool does not have to "full featured" or "hard" to be good. And using "simple" tools does not make someone more dumb.

If you need a swiss army knife, then by all means use one. If you need a drill, Go ;-) with that.

There is beauty in simplicity as well.

Looks like a competitor to next.js, and from their docs built on koa.

It’s nice to see more libs in this space, but it seems a little over complicated to me with the “plugin” style arch.

Exactly, it’s a lot clearer to your future self, and any other maintainers how the application works when you aren’t adhering to a “frameworks” way of doing something. Especially for a simple cli.

Abstractions can be good, but I feel as though something like commander is really just an unneccessary abstraction.

I’ll take simplicity first anyday.

This article goes through discussing using tjs commander library for building node cli’s. I’m not a big fan of the library.

A recent approach I’ve been taking is just parsing args with something like minimist or zeit/arg and then handling the commands passed in.

It leads to a lot simpler code especially for small tasks like what is described in the parent article.

Another tip, you could also use pkg to create binaries for your new cli application so people don’t need node installed on their machine to run them.

Any opinions on Phabricator vs Gerrit? I'm currently working on a project using the latter.

Is this something that others are interested in as well?

Btw what kind of info would you like to see in a write up about this?

Ardan Labs | Mid - Senior Software Engineer | Miami, FL | Full Time | REMOTE | ONSITE | https://www.ardanlabs.com/

Ardan Labs is a high performance software development firm that builds and delivers reliable solutions and applications. We're looking for several Mid-level and Senior Backend Engineers to help us develop solutions for our clients.

This is a great opportunity to be part of a culture of caring, cooperation, reliability and growth. We are based in Miami, Florida, but our team is spread across North America. Some roles may be location dependent, but we welcome remote work.

Ideally you are a responsible, self-motivated individual that is looking to work with the latest technology and create uncompromising user experiences.

Responsibilities:

Design and build REST/gRPC APIs with speed and reliability in mind. Design and use SQL and NoSQL databases to support both relational and nonrelational performance and storage requirements. Write tests. Document web services for public consumption. Implement proper instrumentation and logging. Leverage Kubernetes/Docker to deploy and manage a scalable infrastructure across multiple geographical regions. Respond to system level issues as necessary to provide the best overall customer experience.

Qualifications:

Minimum 2+ years of professional experience developing REST based web services. Experience developing in more than one backend language preferrably Go, C/C++, Java, Ruby, Python, Node.js, etc. Experience with the Linux operating system and the Bash shell. Ability to communicate and articulate architecture decisions and the reasons behind them.

Nice to Haves:

Experience with Go, Postgres, Message Queuing, Websockets/Server Sent Events highly desired. Experience working on a highly scalable platform. Familiarity with Asynchronous communication protocols. Experience using Docker for development and deployment to production environments Experience supporting/developing mobile platforms.

We have a straightforward interview process. So no surprises there!

If you're interested, feel free to email us with your resume at careers @ ardanlabs.com or apply on our website: https://www.ardanlabs.com/careers

Awesome, I didn't know they had podcast links! Thanks

These posts are becoming redundant. Although I do understand where the author is coming from. I think the issue is that frontend development is hard! Especially modern frontend dev. It requires an entirely different thought process than backend development and this is why I think so many people get scared and reach for the most familiar lib out there.

However, getting used to the React ecosystem really does have huge benefits (code clarity, minimization of bugs, ease of creating complex interactions) and I do recommend that those interested really just dive in and build something simple to see for themselves.

If you're new, ignore [babel, redux, (insert buzz lib here)] and just build something. Checkout https://medium.com/@clmyles/react-without-npm-babel-or-webpa... on how to create something with just React.

All the extra libs and tools are helpful and make your job easier in most cases. But they can be phased in as you get a deeper understanding of the ecosystem.

The ecosystem is standardizing now. And I don't see webpack or React going away anytime soon.

Like anything else it depends. JWTs are still great. Just don’t treat it like a classical session and dump important information in it.

You could also use session like you always have if the SPA is being served by the same server.

I don't think he's implying that. A good way to think about it is mapping reducers -> features.

Reducers are composable, so you can actually end up with pretty clean code in large codebases

Realizing how much money and time can be saved cooking rice and beans.

Good tip make “sofrito” ahead of time (puree peppers, onions, cilantro, garlic) and freeze it in an ice tray so it is already portioned and ready for when you cook.

Rice and beans takes about 20 min to make without much effort, and is pretty nutritious. Not to mention you can eat for dollars a day.

Edit: My grandmother used to feed the whole family for less than $20. And most of that cost is in meat.

The only way is really to educate them. I’ve dealt with this quite a bit with my family, and telling them what to be wary of has helped a bunch.

Hey all! Author here! This is a course on building a CI pipeline on top of git hooks using Nodejs. Leave a comment if you've got any questions!

It could be argued that YC wouldn't be as popular as it is today without HN. Also it seems to be a great recruiting source for YC companies. It doesn't have to literally bring in money to be considered profitable when the profits could be in the form of more intangible things.

To be honest I like most of your work and you remind me a bit of myself. The only difference seems to be I have a large focus on development. (frontend or backend, whatever code is code just the process is different)

My first job ~7 years ago I kind of fell into with a bit of luck and networking. However that experience helped me really propel my career.

I'm about the same age as you (24) have the following advice:

Don't put your age anywhere. Ageism exists. It'll benefit you a lot more to have a stunning resume / track record that gets you in the door and have a face to face talk with people who will hire you.

Get your programming chops up and try to pursue an engineering position. There are more jobs in engineering vs a design position. Plus you obviously know a bit about design and this'll translate nicely into aspects of engineering.

Good luck! And like others have said take a day off, have a couple beers, and continue when you feel a bit more optimistic.

A raspberry pi is also not a CDN. Why even manage servers when all you need is a static site? Deploy to a CDN and if properly configured, everything just works.

Especially with the site being considered in 'maintenance mode', I doubt they want to manage a server aside from the other things they need to do.