Question, how much do you pay for Netflix? Or Amazon Prime?

Disclaimer, I have never paid for an Apple developer license and probably never will.

Happy Birthday! But shouldn't age just be a getter or computed value from your date of birth? Just sayin'...

Instead of looking for a "project" look for a problem or pain point you have in your current development workflow. Look for solutions to that problem. If one already exists, implement it into your workflow. If you have a use case that's slightly different than the ones provided, submit PRs. If no one in the history of ever has had your same issue, you have some crazy use use case, or you've just encountered a rare thing.

That being said, don't be afraid of reinventing the wheel for learning purposes. You may encounter use cases along the way that the original authors missed or forgot about, or perhaps they knew about it but there was something you hadn't considered yet.

Just don't go solo cowboy. There's a lot to learn from the past and your peers.

Anecdotal experience: every tech job I've worked in, 99% of the developers used mac, usually only one or two used Linux. No windows... but I've never worked for a .net shop

Indenting from the right... I knew someone who did this to troll... he's a music major now

Unit tests pass!

✅

@Jasey Infoind this to be true in my university program. The successful students knew better while the sheeple just took what was taught as gospel.

Poor chaps...

I think the goal is it web scrape a bunch of data from a paginated list. It might be more useful and end result to parse the HTML and extrapolate the data you need and put it into a csv or database directly.

Programming exams should be TDD. Maybe a longer if you really want to enforce a certain style.

Yes, I did regular fire drills to make sure the backups could restore. I have heard of arq backups failing, though

Oh gross... that's like... dead skin, earwax, whatever was in his saliva, poop particles (using phone in the bathroom)...

Run far far away

I remember the good 'of days when you could just write a .js file, and then write a script tag to include it on a page.

Then people wanted "applications". Which spawned build processes, minifiers, module bundlers, transpilers, and some more overengineering.

It's all pretty cool, but it's kind of overkill when your boilerplate starts out at 300kb and still doesn't do anything.

I haven't used time machine in years... screwed me over one too many times. Been using ARQ with S3, and it's been great and cheap.

Don't bother trying to learn the API. The maintainers make major breaking changes every few months or so.

@SHA-256 For sure, I just don't like the distribution model because it allows those other distributors to not update the OS. I think Android is a great OS, and if I were to ever get an android phone, it would be a Google made one.

I had a temporary project manager like this. At first he would say that he couldn't understand why we like programming, then he said that he literally gets mad mad at developers because they're doing something he'll never understand, and that we made so much money doing it.

He was a terrible project manager and a jerk to us

Then the fire nation attacked!

^ referencing my comment above:

I know not all Java apps end up that resource heavy, but in my admittedly limited perspective of the Java world, all of the Java web projects I've seen have ended up that heavy

I don't mind Java. The Java apps I've seen in production though tend to be hard/expensive to scale requiring tons of memory and processing power.

At work we have Java apps and Node apps. The apps are pretty different so the comparisons aren't super valid, but here's a list of differences of the production environments:

- For the Java apps, they have to have a new app instance per customer.
- Each running instance for the Java apps requires at least 8GB of RAM and 4 fairly decent CPU cores.
- 90% of our operational costs are eaten up by the costs of running those servers alone, and adding more customers increases that cost in a way that doesn't scale well.

- On the node side, we have a scalable cluster that runs between 2-4 instances that handle every customer.
- The servers are single core and use less than 1GB of RAM
- The cost the of running our apps is about the cost of some of the licenses required by whatever IDE that the Java Developers are using.

Biggest lie that an executive or product owner will tell you: "Lets implement the quick solution for now and we'll pencil in some time to do the real fix"

If they don't prioritize the real fix now, they'll care even less about it later, that is until everything goes to crap because they didn't listen to you about the problems with the quick solution, and everything is your fault again for not implementing it correctly the first time.

This is why I've stopped suggesting quick solutions, because they're usually half-baked anyway.

JavaScript

const arr = [ a, b, c ]
const newArr = arr.map((val) => [ val ])

In most shells, * is used to select all files/ folders in a given path, but you need a special flag to view the hidden ones :)

That is a solid rant. Have a ++

Maybe it's a job for an OCR company

Just to be sure... results could have gotten stale, you never know ;)

Could be filepaths to images that the CSS references

I did a similar migration once, from a static website to a CMS (some 8000+ web pages) it has some decent SEO and although we knew the tags were pretty useless as far as SEO goes, we went ahead migrating them anyway. The site ended up getting a boost from google.

We did the same thing for a smaller site that got about the same amount of traffic, but the developer working on that one forgot to migrate the tags (got everything else, including pretty much the same markup). The site tanked after that because even though the tags didn't give any direct SEO value, it was a way that the page was "fingerprinted", so when they were removed, Google and others thought they were new pages and decided to knock them down a bit because the content had changed too much.

Black Magic, all of it

It's probably taking a while to build your code. Are you using webpack? Babel?

I think in theory, you can't get more elegant. In practice, I find it hard to read. The functional programs I have written have been fairly bug free, but when I compose a bunch of functions together to accomplish some business rule, I have to pick it apart every time I read it because it's so hard to follow.

I think it's great for coding challenges though.

@FlyPigFly the right companies will see it for what it is, recruiters might see the buzzwords like angular and react