Announcements & News
The latest announcements and Flight Rising news.
TOPIC | Dev Update: 2022 Goals
1 2 ... 11 12 13 14 15 ... 26 27
Which pages are still missing from the new code base?nonly the ones mentioned in the edit, or is it more?
Which pages are still missing from the new code base?nonly the ones mentioned in the edit, or is it more?
iSeAVDm.gif6mlt6oK.pngSNH9aOp.gif





B9L.pnglvf-7.pnglvf-9.pnglvf-1.pnglvf-6.pnglvf-5.pnglvf-3.pnglvf-2.pnglvf-4.pnglvf-10.pnglvf-8.pngB10R.png
fOHFzrA.png
Thank you devs for keeping us updated! I can't wait to see what FR has in store this year!
Thank you devs for keeping us updated! I can't wait to see what FR has in store this year!
Fishes | she/her | +3 FR time
your local nintendo nerd
DragCave | Obe-Loaf Art!| Wishlist!
NlmYDAS.pngLRdLP2V.pngv2PJF9u.png
Oooh fancy. I hope plague Nests keep their soup
Oooh fancy. I hope plague Nests keep their soup
Caravan of the Infected Voyagers
68475654.png
She/Her | FR+3
Makes sense. Would you (or members of the engineering team) be able to share which aspects of refactoring have been most difficult, or what the largest hurdles are?

It’d be cool to follow the progress of minor updates, similar to the thread of gene errors, where we have information pertaining to what the technical issues and fixes are (such as a layering issue in one single case vs having to redo a lot of stuff manually). Wouldn’t mind being able to predict any potential hiccups ahead of time, too, if it involves a major mechanic.
Makes sense. Would you (or members of the engineering team) be able to share which aspects of refactoring have been most difficult, or what the largest hurdles are?

It’d be cool to follow the progress of minor updates, similar to the thread of gene errors, where we have information pertaining to what the technical issues and fixes are (such as a layering issue in one single case vs having to redo a lot of stuff manually). Wouldn’t mind being able to predict any potential hiccups ahead of time, too, if it involves a major mechanic.
z9qhfn0.pngROlI7FX.pngZxxgt4q.png
[emoji=banescale happy size=1]
bJs5ioz.gif
Made by Dovalore
[quote name="sirspiderider" date="2022-01-10 15:14:20" ] Makes sense. Would you (or members of the engineering team) be able to share which aspects of refactoring have been most difficult, or what the largest hurdles are? It’d be cool to follow the progress of minor updates, similar to the thread of gene errors, where we have information pertaining to what the technical issues and fixes are (such as a layering issue in one single case vs having to redo a lot of stuff manually). Wouldn’t mind being able to predict any potential hiccups ahead of time, too, if it involves a major mechanic. [/quote] ^ I second this.
sirspiderider wrote on 2022-01-10 15:14:20:
Makes sense. Would you (or members of the engineering team) be able to share which aspects of refactoring have been most difficult, or what the largest hurdles are?

It’d be cool to follow the progress of minor updates, similar to the thread of gene errors, where we have information pertaining to what the technical issues and fixes are (such as a layering issue in one single case vs having to redo a lot of stuff manually). Wouldn’t mind being able to predict any potential hiccups ahead of time, too, if it involves a major mechanic.
^ I second this.
bJs5ioz.gif
Made by Dovalore
actually I’m curious, why is the site divided into two (sub?)domains? Is it to keep the dragon heavy parts separate from other features, so in the case that one part were to go down, there’s a backup?

Otherwise, thanks so much for the hard work and update guys!
actually I’m curious, why is the site divided into two (sub?)domains? Is it to keep the dragon heavy parts separate from other features, so in the case that one part were to go down, there’s a backup?

Otherwise, thanks so much for the hard work and update guys!
vettel.gif shebudollagainsmalllll.png
[quote name="Vrachos" date="2022-01-10 13:50:40" ] [img]https://cdn.discordapp.com/attachments/731626887360806985/930216506233585684/unknown.png[/img] context: [spoiler]a friend joked that it was "year of the revamp" so i made this edit really fast. Also I support the devs' decision to do this; as a software developer myself, a lift-and-shift seems much easier to deliver than a total rewrite[/spoiler] [/quote] Well, refactor, not revamp. We're doing 1:1 conversions of the code that don't change anything or add any bells and whistles. Revamps are revamps and include quality of life and often interface improvements. Something to make the feature different and upgraded. We still plan on doing revamps, but if we get everything on the same codebase before we do rather than trying to convert and improve simultaneously, it'll make things go a lot smoother since the engineers won't have to be looking two places every time they make a change!
Vrachos wrote on 2022-01-10 13:50:40:
unknown.png



context: a friend joked that it was "year of the revamp" so i made this edit really fast. Also I support the devs' decision to do this; as a software developer myself, a lift-and-shift seems much easier to deliver than a total rewrite

Well, refactor, not revamp. We're doing 1:1 conversions of the code that don't change anything or add any bells and whistles. Revamps are revamps and include quality of life and often interface improvements. Something to make the feature different and upgraded.

We still plan on doing revamps, but if we get everything on the same codebase before we do rather than trying to convert and improve simultaneously, it'll make things go a lot smoother since the engineers won't have to be looking two places every time they make a change!


youtube.png tumblr.png reddit.png twitter.png facebook.png da.png
[quote name="Xhaztol" date="2022-01-10 13:00:10" ] [i]snipped[/i] here are a few of the things that we're hoping to refactor this year, if we can fit them all in alongside new content and new features: [LIST] [*]The Dominance standings page [*]Gathering & Gathering Results [*]Clan Profile [*]Nesting Grounds [/LIST] [/quote] Thank ya'll for being so transparent and updating us with everything! Am I right in understanding there are basically three categories? [LIST] [*] New features - New things not currently incorporated into the site in any form such as new items, events, etc. Development to continue as normal for 2022. [*] Revamp - Updating existing features, such as adding the ability to select pairs with a visual menu vs. drop-down on the nesting page. Development to be mostly paused for 2022. [*] Refactor - Rewriting/converting code for existing features to make all future development much easier/less time consuming. One of the main focuses for 2022. [/LIST]
Xhaztol wrote on 2022-01-10 13:00:10:

snipped

here are a few of the things that we're hoping to refactor this year, if we can fit them all in alongside new content and new features:
  • The Dominance standings page
  • Gathering & Gathering Results
  • Clan Profile
  • Nesting Grounds

Thank ya'll for being so transparent and updating us with everything!

Am I right in understanding there are basically three categories?
  • New features - New things not currently incorporated into the site in any form such as new items, events, etc. Development to continue as normal for 2022.
  • Revamp - Updating existing features, such as adding the ability to select pairs with a visual menu vs. drop-down on the nesting page. Development to be mostly paused for 2022.
  • Refactor - Rewriting/converting code for existing features to make all future development much easier/less time consuming. One of the main focuses for 2022.
dT9HQge.png
p3Lr8aR.png
5hF3FGk.png
tumblr_inline_nz2de7oArI1tgh8q0_250.png
So, if I understand this right: This means you're deciding to focus on making the code more efficient, so things run smoother in the long run? (easier bug fixes, less strain on the code, easier to go back and change things in the future?) Un-spaghetti the code? Is that what this means? If so, I'm glad y'all are deciding to focus on that first and foremost! Cleaner codes mean cleaner features and much less stress in the long run [emoji=spiral tongue size=1]
So, if I understand this right: This means you're deciding to focus on making the code more efficient, so things run smoother in the long run? (easier bug fixes, less strain on the code, easier to go back and change things in the future?) Un-spaghetti the code? Is that what this means?
If so, I'm glad y'all are deciding to focus on that first and foremost! Cleaner codes mean cleaner features and much less stress in the long run
bYt72YT.pngrcLDXY6.pngMUYNhfy.png
yZFrBUC.pngyvMj9jM.pnggYW0j5f.png

tumblr_inline_nz2d9xtCMB1tgh8q0_250.png
1 2 ... 11 12 13 14 15 ... 26 27